From: gianluca <gianlucarenzi@eurekelettronica.it>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Using LVDS in a iMX6Q/D from Barebox
Date: Tue, 14 Feb 2017 11:59:53 +0100 [thread overview]
Message-ID: <814412dc-f364-70cb-43a9-f9e971a0b3c1@eurekelettronica.it> (raw)
In-Reply-To: <e2e3ab47-9cbd-0437-d889-a98704459d1b@eurekelettronica.it>
On 02/14/2017 11:32 AM, gianluca wrote:
> On 02/10/2017 08:35 AM, Sascha Hauer wrote:
>> Hi Gianluca,
>>
>> On Thu, Feb 09, 2017 at 03:37:41PM +0100, gianluca wrote:
>>> Hello,
>>> I would like to know if there is a clear way on using the lvds pins
>>> to drive
>>> a LVDS display in a custom made board, based on iMX6Q (in the near
>>> future
>>> the iMX6Dual).
>>
>> I think what you are looking for is of_device_enable_and_register() or
>> of_device_enable_and_register_by_name(). You can call it on either the
>> lvds device node or the hdmi device node, depending on whether you found
>> an EEPROM or not.
>>
>
> I think this is not necessary as during boot I can see clearly:
>
>> imx-ipuv3 2400000.ipu: IPUv3H probed
>> imx-ipuv3 2800000.ipu: IPUv3H probed
>> imx-ldb ldb.10: probe failed: Invalid argument
>> imx-hdmi 120000.hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
>
I had a wrong configuration:
>
>> &ldb {
>> status = "okay";
>>
>> lvds0: lvds-channel@0 {
>> fsl,data-mapping = "spwg";
>> fsl,data-width = <16>;
>> status = "okay";
>>
fsl,data-width = must be <18> or <24>
Now boots without error, but the framebuffer device is not registered.
Why? I need something more??
--
Eurek s.r.l. |
Electronic Engineering | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377 | Fax: +39-(0)542-609212
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-02-14 11:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 14:37 gianluca
2017-02-10 7:35 ` Sascha Hauer
2017-02-14 10:32 ` gianluca
2017-02-14 10:59 ` gianluca [this message]
2017-02-15 10:07 ` gianluca
2017-02-15 11:51 ` Sascha Hauer
2017-02-15 14:34 ` gianluca
2017-02-16 7:28 ` Sascha Hauer
2017-02-16 9:07 ` gianluca
2017-02-16 14:43 ` gianluca
2017-02-16 15:50 ` Lucas Stach
2017-02-17 15:38 ` gianluca
2017-02-22 8:00 ` Sascha Hauer
2017-02-22 8:26 ` gianluca
2017-02-22 9:05 ` gianluca
2017-02-22 9:40 ` Sascha Hauer
2017-02-23 12:10 ` gianluca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=814412dc-f364-70cb-43a9-f9e971a0b3c1@eurekelettronica.it \
--to=gianlucarenzi@eurekelettronica.it \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox