On Thu, Dec 16, 2010 at 9:47 AM, Timur Tabi <[email protected]> wrote: > On Fri, Jul 23, 2010 at 9:00 AM, Anatolij Gustschin <[email protected]> wrote: >> Adds support for encoding display mode information >> in the device tree using verbatim EDID block. >> >> If the EDID entry in the DIU node is present, the >> driver will build mode database using EDID data >> and allow setting the display modes from this database. >> Otherwise display mode will be set using mode >> entries from driver's internal database as usual. >> >> This patch also updates device tree bindings. >> >> Signed-off-by: Anatolij Gustschin <[email protected]> >> Acked-by: Timur Tabi <[email protected]> >> Cc: [email protected] > > Anatolij, > > I know this patch is old, but I'm now getting back to working on the > DIU driver. One question I have: why are you reading the EDID data > from the device tree? Why not just read it directly from the device > using I2C? Who is supposed to put the EDID data into the device tree > in the first place?
This is for devices which don't have an i2c edid channel. g. _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
