On 20/01/2026 13:50, Sudarshan Shetty wrote: > Update the gpio-backlight binding to support configurations that require > more than one GPIO for enabling/disabling the backlight.
Why? Which devices need it? How a backlight would have three enable GPIOs? I really do not believe, so you need to write proper hardware justification. > > Signed-off-by: Sudarshan Shetty <[email protected]> > --- > .../leds/backlight/gpio-backlight.yaml | 24 +++++++++++++++++-- > 1 file changed, 22 insertions(+), 2 deletions(-) > > diff --git > a/Documentation/devicetree/bindings/leds/backlight/gpio-backlight.yaml > b/Documentation/devicetree/bindings/leds/backlight/gpio-backlight.yaml > index 584030b6b0b9..4e4a856cbcd7 100644 > --- a/Documentation/devicetree/bindings/leds/backlight/gpio-backlight.yaml > +++ b/Documentation/devicetree/bindings/leds/backlight/gpio-backlight.yaml > @@ -16,8 +16,18 @@ properties: > const: gpio-backlight > > gpios: > - description: The gpio that is used for enabling/disabling the backlight. > - maxItems: 1 > + description: | > + The gpio that is used for enabling/disabling the backlight. > + Multiple GPIOs can be specified for panels that require several > + enable signals. All GPIOs are controlled together. > + type: array There is no such syntax in the bindings, from where did you get it? Type is already defined. items: minItems: 1 maxItems: 3 > + minItems: 1 > + items: > + type: array > + minItems: 3 > + maxItems: 3 > + items: > + type: integer All this is some odd stuff - just to be clear, don't send us LLM output. I don't want to waste my time to review microslop. Was it done with help of Microslop? Best regards, Krzysztof
