Emma Anholt

You'll need to attach the dmesg for us to do anything. And, yes, use 4.9.

It should work, but you do need the alsalib config file that is in rpi downstream, and I think may have made it upstream.

A long time ago Gerd was submitting the pi3 patch series with the fxl6408 gpio expander driver present, which would fight over i2c0 (iirc) with the firmware. I think that...

I think this should do it. Without the curr_msg check, it gave me a bunch of nicely formatted DONE messages. [0001-i2c-bcm2835-Debug-test-for-curr_msg.patch.txt](https://github.com/anholt/linux/files/778234/0001-i2c-bcm2835-Debug-test-for-curr_msg.patch.txt)

We shouldn't try to harden our isr against spurious IRQs, we should just disable the controller in the DT. We don't get to drive it, and if we ever do...

v3d is not a display driver, and thus doesn't expose the dumb ioctls. For pi4, you do display on the vc4 drm node, and use that node with Mesa so...

My guess would be that baseline ALSA is just defaulting to whatever module probes first, and module probe order in Linux is arbitrary. You should probably be using some software...

I'm glad the DPI stuff is working for you! If you're using X, you can add modes at runtime with xrandr --newmode, xrandr --addmode, xrandr --addmode, xrandr --mode (yes, this...

Yeah, just "simple-panel" won't do anything, as nothing matches that. I think you need panel-simple.c changes, because even with specifying a mode on the command line, you still need the...

http://www.spinics.net/lists/devicetree/msg145160.html may be an interesting route to go for supporting this.