On Wed, Feb 9, 2011 at 7:25 PM, Raghuveer Murthy <[email protected]> wrote: > Adding DVI support to OMAP4 PandaBoard. > > PandaBoard uses TFP410 DVI Framer chip > http://focus.ti.com/lit/ds/symlink/tfp410.pdf > > The TFP410 gets its power enable and display data over GPIO lines muxed > in from OMAP4430. PandaBoard supports other LCD displays through expansion > connectors, following board rework. This will disable the DVI interface. > However, the existing mux settings remain the same > > PandaBoard additionally supports display over HDMI interface. It is > mutually exclusive to display over DVI. Hence the mux settings need to be > configured seperately, as and when HDMI is enabled > > Also, I2C3 bus used for reading EDID data from DVI Monitors is > registered here. Since the design is similar to BeagleBoard, the code > for the same is taken from the kernel.org commit e3333f48dd5cb21 > (omap: Adding beagle i2c eeprom driver to read EDID) > > Reviewed-by: Manjunath G Kondaiah <[email protected]> > Reviewed-by: Anand Gadiyar <[email protected]>
I've also tested it on the Panda, and gone through this and most of the other patches in the series. So if you like, you could consider this an: Acked-by: Anand Gadiyar <[email protected]> > Reviewed-by: Nishanth Menon <[email protected]> > Reviewed-by: Sumit Semwal <[email protected]> > Signed-off-by: Raghuveer Murthy <[email protected]> > --- > > Base > ==== > url = > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > branch "master" > commit 100b33c8bd8a3235fd0b7948338d6cbb3db3c63d > tag 2.6.38-rc4 > To make it easier for someone to test, I've extracted this and the 6 dependent series from patchwork, and hosted them in a branch on my devel tree. They are available against v2.6.38-rc4 here: git://dev.omapzoom.org/pub/scm/anand/linux-omap-usb.git in the display-patches-for-v2.6.38-rc4 branch if someone wants to take a look. - Anand -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
