Hi
Am 02.07.25 um 22:43 schrieb Krzysztof Kozlowski:
On 30/06/2025 10:40, Hans de Goede wrote:
No one asks to drop them from the driver. I only want specific front
compatible which will list and constrain the properties. It is not
contradictory to your statements, U-boot support, driver support. I
really do not see ANY argument why this cannot follow standard DT rules.
So what you are saying is that you want something like:
framebuffer0: framebuffer@1d385000 {
compatible = "qcom.simple-framebuffer-sm8650-mdss",
"simple-framebuffer";
}
and that the binding for qcom.simple-framebuffer-sm8650-mdss
can then list interconnects ?
IMO yes (after adjusting above to coding style), but as mentioned in
other response you can just get an ack or opinion from Rob or Conor.
But does that work with *any* device that requires interconnects? The
next such simple-framebuffer device should work out of the box *without*
the kernel knowing anything about it. That's one of the key features of
the simple-framebuffer. If we have to maintainer per-device feature
sets, it breaks that assumption.
Best regards
Thomas
Best regards,
Krzysztof
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
