On 02/09/14 12:51, Dr. H. Nikolaus Schaller wrote:
Config:
http://git.goldelico.com/?p=gta04-kernel.git;a=blob;f=arch/arm/configs/gta04...
You seem to have a mix built-in and modules for the display drivers. I'd recommend just using one, either build all as modules, or all as built-in. Makes life easier.
In your case, I think the main problem is that you have omapfb as built-in, but display devices as modules. omapfb doesn't support "hotplugging" new displays. So when you at some point load the display modules related to HDMI, omapfb has already decided that there are no displays.
So either build everything into kernel, or build them as modules, and load omapfb last.
Device Tree:
http://git.goldelico.com/?p=gta04-kernel.git;a=blob;f=arch/arm/boot/dts/omap...
- there is no HDMI i2c to inspect by i2cdetect -r 5
The HDMI i2c is not exposed as normal i2c bus. It's only used inside the HDMI driver.
Ah, I see.
I remember it was a nice debugging feature of the older 3.8 kernel. And it would allow some hacking for external devices (a 5V compatible I2C on external standard connector...).
So can it easily be exposed by extending the DT file?
No. The HDMI i2c is managed via the HDMI IP, not the omap's i2c hardware.
It is possible to write a new i2c driver, which which exposes the HDMI i2c as a linux i2c bus. I accept patches for that ;).
- DSS does not try to load a lcd panel driver
You need to set the compatible string in the panel driver to "omapdss,lg,lh500wf1".
Ah, yes!
I think you have already updated it for the TD028TTEC1 so that I didn't see a problem on the GTA04 board. Just on the EVM with a non-mainline driver for the display...
I had another minor bug with duplicate pinctrl-name entries which also did reject the driver loading.
But now the driver loads. Thanks!
Still without any /dev/fb*
Yep, it's the module load problem I described above.
Another question: did you also see messages like (there is no USB device connected at all)
[ 6.713976] usb 1-2: new high-speed USB device number 3 using ehci-omap [ 6.785253] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 7.685261] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 8.525305] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 9.365256] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 10.205302] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 10.834045] usb usb1-port2: Cannot enable. Maybe the USB cable is bad? [ 10.895259] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 11.795263] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 12.635299] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 13.475249] ehci-omap 4a064c00.ehci: port 2 reset error -110 [ 14.315259] ehci-omap 4a064c00.ehci: port 2 reset error -110
I did also have it sometimes with the ti-3.8 kernel so I wonder if it is a hardware bug on my EVM board.
No, I don't see that. I've attached my kconfig in case you want to test/compare.
Tomi