As I was investigating why my nyan_big's screen was staying dark when testing 4.12, it appeared that the tegra drm driver does not get probed at all on my setup (read: host1x_drm_probe never gets called). I have also tested on jetson- tk1, with the same result. I am using a finely-tuned out-of-tree config[0], but it appears (from looking at the lack of drm line in the logs) that the same is happening with the tegra and multi_v7 defconfigs hooked to kernelci. First, I am wondering whether the tegra drm driver is probing for anyone following this list on any tegra124 device with 4.12. If so, feel free to raise your voice so we can find out what is wrong with my setup. I initially thought that it was caused by missing firmwares (that are now needed for falcon/vic support), but disabling that (by removing the &tegra_vic_driver entry and associated compatible string in drm.c) does not help. Hopefully, I will have time to run a bisect this week-end and identify the commit that introduced the regression. It would be quite important to get this fixed for the 4.13 release. In the meantime, test results with different setups are more than welcome :) [0]: http://git.code.paulk.fr/gitweb/?p=libettereboot.git;a=blob;f=projects/linux/configs/tegra124/config;h=4bd57ffdd8fa3d36e5dfadbbafc753a4f9b34266;hb=HEAD -- Paul Kocialkowski, developer of free digital technology and hardware support Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
Attachment:
signature.asc
Description: This is a digitally signed message part
