On 16/11/2025 12:33, Krzysztof Kozlowski wrote: > On Sat, Nov 15, 2025 at 03:13:46PM +0100, Jernej Skrabec wrote: >> As it turns out, current H616 DE33 binding was written based on >> incomplete understanding of DE33 design. Namely, planes are shared >> resource and not tied to specific mixer, which was the case for previous >> generations of Display Engine (DE3 and earlier). >> >> This means that current DE33 binding doesn't properly reflect HW and >> using it would mean that second mixer (used for second display output) >> can't be supported. >> >> Update DE33 mixer binding so instead of referencing planes register >> space, it contains phandle to newly introduced DE33 planes node. >> >> There is no user of this binding yet, so changes can be made safely, >> without breaking any backward compatibility. > > And why would you configure statically - per soc - always the same plane > as per mixer? If you do that, it means it is really fixed and internal > to display engine thus should not be exposed in DT. > > Describing each IP block resource in DT is way too granular. >
BTW, everything is update, thus subject is really non-informative. Best regards, Krzysztof
