11:35 <phh> is there some example commit somewhere of driving a RGB panel on rk3288 on linux mainline? is it supported?

11:36 <phh> looks like it is going through lvds hw component and we kinda need to declare it as a lvds panel?

12:24 <a1batross> Hello there! Can somebody explain to me, can I2S actually work with two devices connected? For example, I have one I2S that on TX is connected to RK809 codec and on RX is connected to the radio. RK809 and radio can be configured as consumers. I think it should work if I will configure them both at same clock but I also haven't tried stupidly declaring them both in device tree yet.

12:27 <phh> a1batross: radio receives sound from rk809?

12:27 <phh> wrt clock, i2s has a "master" which is the one generating the clock, the other side just uses that clock

12:29 <a1batross> phh, nope, it's just an FM radio. In Linux it looks like a capture device, where RK809 is only playback.

12:30 <phh> so you have a RX I2S for the FM radio on the SoC and a TX I2S for playback on RK809?

13:21 <a1batross> phh: yeah, and it's all the same I2S channel

13:23 <a1batross> I just don't have a second I2S, that's why I'm doing this evil thing.

16:58 <phh> oh great my panel doesn't use "normal" 18bits wiring, but rather

16:58 <phh> #define OUT_D888_P666 0x21 //18bit screen,connect to lcdc D2~D7, D10~D15, D18~D23