Tool/software: Linux
Hello TI team,
we have created a custom AM5728 SOM and baseboard.
We have a LCD display attached to the parallel video output VOUT1:
/* ET0700G0DH6 + ETM0700G0DH6 + ETM0700G0BDH6 + S070WV106H-CT44 */
lcd: display {
compatible = "panel-dpi";
bits-per-pixel = <32>; /* 32: RGB888/666 mode */
/* change it to 18 for new hw rev. */
bus-width = <24>;
label = "lcd";
Upon initialising the omap dss driver, a test pattern (showing 1 second fullscreen of each red, green, blue, black, white, black and white box shapes, gray).
I would have expected to see the linux bootup logo and the console later.
It definitely starts with loading the driver and is not a test application running on the rootfs.
It is also not "fill_fb" function in
drivers/video/fbdev/omap2/omapfb/omapfb-main.c
as I verfied with a debug print.
The bootcommand includes these lines:
omapdss.def_disp=lcd omapdss.debug=n omapfb.debug=n
I am curious where in the driver(s) this output pattern comes from.
When using the hdmi interface
(omapdss.def_disp=hdmi omapdss.debug=n omapfb.debug=n)
we correctly see linux logo and console on the hdmi monitor.
Can you help?
We are using mainline linux kernel 4.9.77
and mainline denx u-boot 2018.01
See attached our device tree, bootlog and defconfig:
/cfs-file/__key/communityserver-discussions-components-files/791/1680.bootlog.txt
/cfs-file/__key/communityserver-discussions-components-files/791/tqma57xx_5F00_defconfig.txt
/cfs-file/__key/communityserver-discussions-components-files/791/3755.tqma572x.dtsi.txt
/cfs-file/__key/communityserver-discussions-components-files/791/6470.tqma572x_2D00_mba57xx.dts.txt
(I had to rename the files to a .txt ending do to .dts ending beeing blocked with inserted files here)
Thanks and best regards,
Stefan
