mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: gianluca <gianlucarenzi@eurekelettronica.it>
To: barebox@lists.infradead.org
Subject: Using LVDS in a iMX6Q/D from Barebox
Date: Thu, 9 Feb 2017 15:37:41 +0100	[thread overview]
Message-ID: <3a707429-03a7-db6b-a1b1-1e70ec0b929e@eurekelettronica.it> (raw)

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.

In my iMX28 based board, I was used the:

> 	add_generic_device("stmfb", 0, NULL, IMX_FB_BASE, 0x2000,
> 			   IORESOURCE_MEM, &board_fb_pdata);

system call to activate a specific videomode defined in the board_fb_data.

Which is the correct way to enable LVDS stuff? Maybe in the device tree 
stuff?

Best regards for any example or any help, hint or clue you will give me
-- 
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

             reply	other threads:[~2017-02-09 14:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 14:37 gianluca [this message]
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
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=3a707429-03a7-db6b-a1b1-1e70ec0b929e@eurekelettronica.it \
    --to=gianlucarenzi@eurekelettronica.it \
    --cc=barebox@lists.infradead.org \
    /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