I feel like I must be missing something simple here. I've reviewed the cutiepi dts file and its corresponding nwe080.c file, but it is not clear to me how the parameters of the dts file correlate to the .c file as the naming conventions/keywords are different (reg vs regulator, for example)
I'm at a bit of a loss for how to configure the dts file so that the https://github.com/torvalds/linux/blob/ ... x-st7701.c driver gets pointed to as the driver.
Also, the vendor specific file is just to set the device as 480x800 rather than 480x854 as the mainline driver is configured.
I used this as a starting place and was able to get a dtoverlay solution didn't get the screen working but also still allowed the RPI to fully boot into the desktop environment via HDMI.
I'm at a bit of a loss for how to configure the dts file so that the https://github.com/torvalds/linux/blob/ ... x-st7701.c driver gets pointed to as the driver.
Also, the vendor specific file is just to set the device as 480x800 rather than 480x854 as the mainline driver is configured.
I used this as a starting place and was able to get a dtoverlay solution didn't get the screen working but also still allowed the RPI to fully boot into the desktop environment via HDMI.
Code:
/dts-v1/;/plugin/;/ { compatible = ""brcm,bcm2711"; fragment@0 { target=<&dsi1>; __overlay__ { status = "okay"; #address-cells = <1>; #size-cells = <0>; power-domains = <&power 18>; port { dsi1_out_port: endpoint { remote-endpoint = <&panel_dsi_in>; }; }; panel_test: panel@0 { compatible = "sitronix,st7701"; reg=<0>; label= "test_display"; vc4_dsi = <&dsi1>; port { panel_dsi_in: endpoint { remote-endpoint = <&dsi1_out_port>; }; }; }; }; };};Statistics: Posted by ncarley — Wed Dec 27, 2023 11:49 pm