03:06 <wens> hexdump0815: I don't really run anything on my devices, so I haven't seen it

09:07 <kholk> hexdump0815: it's like your panel is not powered on.... pretty odd. I don't have a 8183 Krane, otherwise I'd try to check that out...

09:11 <kholk> adomerle: why aren't you contributing your MT6735 patches upstream? :-)

09:11 <kholk> 6765*

10:00 <mwalle> wens: and why would that need to be in the device tree?

10:02 <mwalle> kholk: any news on https://lore.kernel.org/linux-mediatek/20240606092122.2026313-1-mwalle@kernel.org/ and https://lore.kernel.org/linux-mediatek/20240604083337.1879188-1-mwalle@kernel.org/

10:10 <kholk> mwalle: for the patches... the second one has got my R-b, I can't do anything else than that.... and the first one, I don't have BW *today* to test it, should be able to give it a go on Monday

10:11 <kholk> and for the instances to xyz fixed path as wens said, well, for example - merge8 can only connect to vdo0 and only to HDMI, but not to vdo1 and/or not to displayport

10:11 <kholk> so you need to know that merge8 is merge8

10:11 <wens> mwalle: how else would you identify (OVL, RDMA) components that are otherwise identical

10:11 <kholk> clearly that changes with my of graph series

10:11 <wens> yeah :D

10:11 <kholk> because you're connecting that stuff within the graph

10:12 <kholk> so you don't need to know what merge8 is from a driver perspective

10:12 <kholk> as you just follow the graph and call it a day :)))

10:12 <kholk> (well, I mean, what merge8 is == what merge instance is merge@12345678)