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: Fri, 10 Feb 2017 08:35:41 +0100 [thread overview]
Message-ID: <20170210073541.73bsfjhk3fu7nnwm@pengutronix.de> (raw)
In-Reply-To: <3a707429-03a7-db6b-a1b1-1e70ec0b929e@eurekelettronica.it>
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).
>
> Actually it boots using Barebox 2017.01 and if there is a HDMI display it
> uses without hassle.
>
> My init scripts are loading a splash screen, then boot into linux:
>
> > echo "Load splash.png from filesystem..."
> > splash -f /dev/fb0 -b 0 $bootconfig_path/splash.png
> > fb0.enable=1
>
> But now, we are looking for a clear way to activate the LVDS signals in the
> LCD Controller when an eeprom chip is found in the I2C bus (more or less
> like EDID stuff) during bootup.
>
> In my bootup script (or specific board initcall code [board.c]) if no EEPROM
> is found, then it will boot naturally with the HDMI port LCD Display (if
> any) or completely BLIND board if no lcd is present.
>
> If it easy to activate the i2c bus and check for some chip addresses, I do
> not know on how to activate the lvds within code.
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.
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
next prev parent reply other threads:[~2017-02-10 7:36 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 [this message]
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
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=20170210073541.73bsfjhk3fu7nnwm@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