NishanthMenon changed the topic of #linux-ti to: Linux development for TI SoCs | Logs: https://libera.irclog.whitequark.org/linux-ti/ | Let it rock! Vendor SDK/kernel: Also see e2e.ti.com
<lucaceresoli>
I'm currently facing the lack of /dev/fb0 after upgrading from ti/ti-linux-4.19.y to ti/ti-linux-5.10.y
<lucaceresoli>
Any hints on what I should check first?
<lucaceresoli>
my panel driver (not yet published) gets probed; in DT it has ports/port@0/endpoint/remote-endpoint = <&dpi_out>, basically the same as the LCD in am57xx-evm-common.dts from ti-linux-5.10.y
<lucaceresoli>
Should I take am57xx-evm-common.dts from ti-linux-5.10.y as working code so I can use it as an example?
rob_w has quit [Quit: Leaving]
LokeshV is now known as LokeshVutla
<NiksDev>
lucaceresoli, Make sure following configs are enabled:
<NiksDev>
CONFIG_DRM_KMS_HELPER=y
<NiksDev>
CONFIG_DRM_KMS_FB_HELPER=y
<NiksDev>
CONFIG_DRM_FBDEV_OVERALLOC=100
<NiksDev>
CONFIG_DRM_FBDEV_EMULATION=y
<NiksDev>
Once you have the basic DRM functionality working (can be verified by running modetest), you can enable the FBDEV emulation to get /dev/fb0. No special change in DTS is required
<lucaceresoli>
NiksDev, thanks. All the config parameters are there, but...
<lucaceresoli>
(ignore the last line, bad copy paste)
<lucaceresoli>
yet the omapdrm driver is instantiated, dss_probe() returns 0... I'm not sure I understood exactly which part of the omapdrm driver I should see enabled
<NiksDev>
I would suggest to enable dynamic debugs and check the prints
<NiksDev>
first step is to get the modetest running, fbdev gets automatically enabled after that if above configs are present
<lucaceresoli>
NiksDev, OK, I'm now building with DYNAMIC_DEBUG and omapdrm as a module...
<lucaceresoli>
NiksDev, with dynamic debug I'm not getting much info :(
<lucaceresoli>
What would you expect to find in the logs?
<lucaceresoli>
(I'm now building the same setup on the 4.19 branch to see what is different there)
<lucaceresoli>
nonono, wait, I _do_ have more messages in dmesg, but they happen while booting, not after modprobe. They must be triggered by the LCD controller which is described in DT:
<lucaceresoli>
[ 9.991038] omapdss_dss 58000000.dss: trying to bring up master
<lucaceresoli>
[ 9.991047] omapdss_dss 58000000.dss: Looking for component 0
<lucaceresoli>
[ 9.991054] omapdss_dss 58000000.dss: master has incomplete components
<NishanthMenon>
lucaceresoli, also a future reference, please use https://pastebin.ubuntu.com/ => unfortunately our TI IT security folks have blocked pastebin.com and hastebin.com among others.. :( I updated the $topic to reflect that