On Thu, Dec 16, 2010 at 9:47 AM, Timur Tabi <ti...@freescale.com> wrote: > On Fri, Jul 23, 2010 at 9:00 AM, Anatolij Gustschin <ag...@denx.de> 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 <ag...@denx.de> >> Acked-by: Timur Tabi <ti...@freescale.com> >> Cc: devicetree-disc...@lists.ozlabs.org > > 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. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
