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 15:43:52 +0100 [thread overview]
Message-ID: <067eac64-0c28-4012-23bb-813e462d74c2@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:
>> On 02/15/2017 12:51 PM, Sascha Hauer wrote:
>>> On Tue, Feb 14, 2017 at 11:32:44AM +0100, gianluca wrote:
>>>> On 02/10/2017 08:35 AM, Sascha Hauer wrote:
>> 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.
>
Nope. Accessing device drivers (enabled in the device-tree) is possible
in the section: device_initcall() and *NOT* in the coredevice_initcall()
time.
Anyway I was wondering if looking for a node in the device-tree, it will
be possible to change the status of that node.
in DTS I have
&hdmi {
status="disabled";
}
but I need to set the status to "okay" later on the device_initcall() time.
Iterating in the device tree using for_each_node_by_name_from() does not
show any node like hdmi, but using the same function to look for any
"display-timing" section it works.
Why? Where I have to look on to change the status of the device driver
node &hdmi and &ldb?
I see a lot of __fixup() functions but I do not understand it correctly.
Like to change the phandle of the native-mode too..
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
next prev parent reply other threads:[~2017-02-16 14:44 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
2017-02-16 14:43 ` gianluca [this message]
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=067eac64-0c28-4012-23bb-813e462d74c2@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