Phil Elwell

As I said above: > it's likely that the device is holding one or both of the lines low when it shouldn't. If you are also on a Pi 5...

If (and it currently is an "if") the hardware is permanently holding one of the I2C lines low, possibly as a result of an incomplete reset, then there is nothing...

I don't know if there is a generic way to reset a display, but I doubt it. The DSI interface is only for pixel data, the control signals must go...

> Most of the times it works but sometimes the display will not show anything and I will just keep getting these i2c timeouts. > even if I unplug power...

``` 40: a2 pu | lo // CD1_SDA/GPIO40 = SDA4 ``` If that state is semi-permanent (you can monitor the line for changes with `pinctrl poll 40`) then that is...

You are asking for help with a third-party display I don't possess. Any suggestions, @waveshare?

It's fixed already. It will take a while for the new kernel to reach a normal `apt` kernel update, but if you `sudo rpi-update` you'll get a beta kernel with...

I think you can cover all downstream dtbs by putting the changes in `bcm2708-rpi.dtsi`, `bcm2711-rpi-ds.dtsi` and `bcm2712-rpi.dtsi`. If we want to change upstream as well, move them to `bcm2835-common.dtsi` and...

I also notice that the 2712 nvmem entries are in `/soc`, whereas the others are in `/`.

See https://github.com/pelwell/linux/tree/nvmem - the output is identical. Also consider moving the 2712 nvmem nodes to /