dtoverlay=vc4-kms-dsi-7inch does indeed improve things for the better. Both console output and wayland-weston now work. I had to specify it together with dtoverlay=vc4-kms-v3d-pi4, which confirm the observations you posted in some previous mail.
Caveats: * wayland-weston does no longer deactivate the backlight when locking the screen. * The following messages are posted into the kernel log at irregular intervals: (10 seconds to 5 minutes) [ 1268.647667] edt_ft5x06 10-0038: Unable to fetch data, error: -121 [ 1269.694193] i2c-bcm2835 fe205000.i2c: i2c transfer timed out [ 1269.700866] edt_ft5x06 10-0038: Unable to fetch data, error: -110 [ 1269.708008] edt_ft5x06 10-0038: Unable to fetch data, error: -5 I was completely unaware of the vc4-kms-dsi-7inch configuration option -- neither [1] nor [2] mention it. [1] https://www.raspberrypi.com/documentation/computers/config_txt.html [2] https://www.raspberrypi.com/documentation/accessories/display.html --------- Adding dtoverlay=rpi-ft5406 decreased the interval of the following messages down to one second(!): [ 620.227151] i2c-bcm2835 fe205000.i2c: i2c transfer timed out [ 620.234335] edt_ft5x06 10-0038: Unable to fetch data, error: -110 ---------- Adding hdmi_force_hotplug=1 didn't have any effects I observed. ---------- Also I observed the following *sporadic* phenomenons. Sporadic meaning, that they were gone after rebooting with unchanged configuration: * One time, I couldn't observe any of the kernel messages above. * One time, the visual output of the screen was mirrored on the vertical axis. (Right is left and vice versa.) Touch screen input was not affected. (I know there are rpi-ft5406 options to explicitly define screen mirroring which might help me with this issue.) * One time, when wayland-weston was deactivating the screen, the screen remained bright white instead as-black-as-it-can-get-with-backlight-on. I'm wondering if these observations can be explained by unstable communication. Maybe I should re-attach the DSI cable. On the other hand, fkms works absolutely rocksolid -- No issues whatsover. In which ways do the display and the kernel communicate with each other. Is backlight controlled through DSI, or are there seperate communication channels (I2C, SPI) for that? What about touch events? Am eager to learn more. I guess I'll just keep using fkms for now until I had a chance to upgrade to the newest kernel. Let's see if this issues are present there as well. All the observations above are with respect to Linux 5.15.34. Thanks everyone in this thread for your support! Am So, 25. Jun 2023, um 02:47, schrieb Markus Volk: > On Sun, Jun 25 2023 at 12:01:29 AM +0200, Manuel Wagesreither > <[email protected]> wrote: >> The HDMI port is unused on my raspi. I'm using the official Raspberry Pi 7" >> Touchscreen connected via DSI. > > Have you also added ? > > dtoverlay=vc4-kms-dsi-7inch > dtoverlay=rpi-ft5406 > > I never dealt with the 7'' Display but i guess they are needed for kms > > hdmi_force_hotplug=1 > > may also be needed
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60433): https://lists.yoctoproject.org/g/yocto/message/60433 Mute This Topic: https://lists.yoctoproject.org/mt/99727959/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
