On Thu, Jan 14, 2021 at 12:15:04PM +0100, Maxime Ripard wrote: > Hi Rob, > > I just encountered a weird error with the led-gpios bindings. > > Indeed, if we run, on today's next and the current master of the > dt-schema tools: > > DT_SCHEMA_FILES=Documentation/devicetree/bindings/leds/leds-gpio.yaml make -j18 dt_binding_check > > we end up with: > CHECK Documentation/devicetree/bindings/leds/leds-gpio.example.dt.yaml > /home/max/Work/allwinner/build/arm64/Documentation/devicetree/bindings/leds/leds-gpio.example.dt.yaml: leds: led-1:default-state:0: 'keep' is not of type 'array' > From schema: /home/max/Work/repos/linux/Documentation/devicetree/bindings/leds/leds-gpio.yaml > /home/max/Work/allwinner/build/arm64/Documentation/devicetree/bindings/leds/leds-gpio.example.dt.yaml: run-control: led-0:default-state:0: 'off' is not of type 'array' > From schema: /home/max/Work/repos/linux/Documentation/devicetree/bindings/leds/leds-gpio.yaml > /home/max/Work/allwinner/build/arm64/Documentation/devicetree/bindings/leds/leds-gpio.example.dt.yaml: run-control: led-1:default-state:0: 'on' is not of type 'array' > From schema: /home/max/Work/repos/linux/Documentation/devicetree/bindings/leds/leds-gpio.yaml > > What's being especially weird is that linux,default-trigger has the > exact same definition than default-state in leds/common.yaml (aside from > the set of valid values), and just works fine. > > Changing the name of default-state to something else also doesn't change > anything, so it doesn't look like this is some other schema interfering. > Do you have an idea? Ping? This error is still there on today's -next Maxime
Attachment:
signature.asc
Description: PGP signature
