I2C3 & TFP410 I2C

My plan is to implement a WinCE driver that dynamically sets up optimal DVI-D output based on display device.

So I am looking at reworking a B7 board to connect TFP410 I2C slave port to I2C3 port. Short of a voltage translator and some resistor changes, any reason not to do this?

Perhaps more curious why this wasn't implemented by default.

Joel

The display is not controlled by the TFP410. It is just a framer. It is controlled via SW in the LCD controller of the OMAP3530. You have the ability to read the EDID information via the I2C pins on the connector and then you set it inside the OMAP3530.

Gerald

Gerald....Go to bed!

-Keith

Gerald Coley wrote:

Can’t sleep! Too many Beagle questions!

Gerald

I see. So anything the OMAP can throw at the TFP410 in current
configuration will work, as long as the display supports it?

Thanks,
Joel

Gerald Coley wrote:

Looking at the TFP410 manual brings up a couple thoughts:
1. Data skew is linear over supported frequency range of OMAP output?
Or is this solely there to support hardware design variances?
2. Detect connection to monitor other than polling? Looks like the
MSEN pin is intended to be used as an hot plug interrupt source.
3. Without I2C - DE generator is a non-feature, which eliminates
potential feature of non-scaling display output.

Joel

Joel Winarske wrote:

I've been playing with ddccontrol (http://
johnkennedyflm.dealerconnection.com/?lang=en) on my beagle but could
not get it to work.
Apparently the EDID data is read but the video driver did not support
ddc or something like that. Not sure any more about details.
Still one of the many things on my TODO list ....

Frans

Correct. We do not support these features on the TFP410 and use it in a set mode. It is there strictly to do the DVI-D coversion of the LCD interface. The LCD interface is accessible on Rev C2 which would allow you to do other things if you like.

Gerald

I see. Thanks for the info.

Joel

Gerald Coley wrote: