Am Donnerstag, den 16.02.2017, 15:43 +0100 schrieb gianluca:
> 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.
The node isn't called just "hdmi", that is just the handle, which may
not even be present in the final DTB if nothing uses it. The nodes name
is "hdmi@0120000".
See "arch/arm/boot/dts/imx6qdl.dtsi".
Regards,
Lucas
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
