mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: gianluca <gianlucarenzi@eurekelettronica.it>
Cc: barebox@lists.infradead.org
Subject: Re: Using LVDS in a iMX6Q/D from Barebox
Date: Wed, 15 Feb 2017 12:51:04 +0100	[thread overview]
Message-ID: <20170215115104.qez5tgbsvwt3zxzz@pengutronix.de> (raw)
In-Reply-To: <e2e3ab47-9cbd-0437-d889-a98704459d1b@eurekelettronica.it>

On Tue, Feb 14, 2017 at 11:32:44AM +0100, 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
> 
> So barebox is trying to bring-up the imx-ldb but fails.
> 
> So I suppose something is wrong in my device tree structure.

Nope, there's everything right.

I can reproduce this here on a GuF Santaro board. LVDS works fine on
current barebox as long as I leave hdmi disabled in the device tree.
When I enable hdmi I also get a "failed to get modes".

Normally when different outputs are available then one would expect
that each one of them is routed to some framebuffer, maybe with some
sane default and configurable during runtime. The current code falls
short here.
What happens is each framebuffer looks around for outputs, all finding
hdmi and lvds. Now the hdmi output may not have a monitor connected
and returns no valid mode. In this case the lvds is not even asked for
modes.
Also in the current code it can happen that the lvds is asked for modes
which are then applied to hdmi.
Where we currently are is that it should work when exactly one output
is enabled. Does lvds work properly when hdmi is disabled? In this
case I would suggest that you manipulate your devicetree so that exactly
one output is enabled.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2017-02-15 11:51 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
2017-02-15 10:07       ` gianluca
2017-02-15 11:51     ` Sascha Hauer [this message]
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=20170215115104.qez5tgbsvwt3zxzz@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=gianlucarenzi@eurekelettronica.it \
    /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