mail archive of the barebox mailing list
 help / color / mirror / Atom feed
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: Thu, 16 Feb 2017 10:07:49 +0100	[thread overview]
Message-ID: <3fbfb5fd-6334-9866-edf7-16dabc124a46@eurekelettronica.it> (raw)
In-Reply-To: <20170216072801.sh3byseyh3f6osgg@pengutronix.de>

On 02/16/2017 08:28 AM, Sascha Hauer wrote:
> On Wed, Feb 15, 2017 at 03:34:55PM +0100, gianluca wrote:
>> First of all hdmi and ldb node are "disabled" by default.
>>
>> Then I am looking for any eeprom in the lvds connector I have.
>> If it is found, check the phandle "native-mode" of the display-timings node
>> to match the value found in eeprom. If not matches the native-mode, it
>>
>> If no eeprom is found activate the status of the hdmi node from "disabled"
>> to "okay". So with the same algorithm as above,
>>
>> Those operations will be done in the coredevice_initcall() level. Is this
>> correct?
>
> Sounds like a plan. I'm not sure though if you find your EEPROM at
> coredevice_initcall time.
>

Now I will check. In the worst case I will do a first-gpio-based (no 
device-tree based) i2c bus access, then when the i2c driver will get 
probed, I will do any other operation.

I will keep you informed.

Regards,
-- 
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-16  9:08 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
2017-02-15 14:34       ` gianluca
2017-02-16  7:28         ` Sascha Hauer
2017-02-16  9:07           ` gianluca [this message]
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=3fbfb5fd-6334-9866-edf7-16dabc124a46@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