----- guillaume gardet <guillaume.gardet@free.fr> a écrit :
----- Tomi Valkeinen <tomi.valkeinen@ti.com> a écrit :
On 2013-03-28 10:55, Guillaume Gardet wrote:
I think I identified the problem.
The TFP410 (dvi chip) is kept in power down state (PD_n pin). I verified it on hardware, the pin is in reset state (0 V) with recent kernels, whereas it is in normal state (3.3 V) with older kernels. I need to dig a bit further to know where is the problem in the code.
Btw, I earlier said the patches I mentioned fixed the DVI output for my beagleboard. But it can be fixed without any patches, by setting CONFIG_DRM_OMAP_NUM_CRTCS=2.
With a 3.7.10 kernel, we need to create file "/etc/modprobe.d/50-omapdrm.conf" with: softdep omapdrm pre: panel-tfp410
To ensure panel-tfp410 is loaded before omapdrm.
Modprobe config seems to help but sometime it still does not work. When it does not work, I get lots of "omap_i2c omap_i2c.3: timeout waiting for bus ready" in dmesg. i2c3 is used to communicate with monitor to determine configuration settings. i2c problem seems known according to this thread: http://www.spinics.net/lists/linux-omap/msg79920.html Any idea how to fix the i2c problem? Maybe will fix as well omapdrm. Please note that omapfb is working fine. Guillaume
With 3.8.6, I get the screen up but it stays black. But I got kernel traces about problems with clock. Maybe related.
3.9 does not boot ATM but it should be something wrong on my side.
Guillaume
Tomi
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org