zephyr/dts/bindings/led_strip/apa,apa-102.yaml

title: APA102 SPI LED strip

description: APA102 SPI LED strip binding

compatible: "apa,apa102"

include: spi-device.yaml
led_strip: add a APA102 driver. The APA102 is a RGB LED with integrated controller. LEDs can be daisy-chained and use SPI for communication. The SPI port is configured via Device Tree. Tested on the Adafruit Trinket M0. Signed-off-by: Michael Hope <mlhx@google.com> 2018-02-13 05:35:20 +08:00			`title: APA102 SPI LED strip`

			`description: APA102 SPI LED strip binding`

scripts: dts: Simplify and improve 'compatible' matching Instead of properties: compatible: constraint: "foo" , just have compatible: "foo" at the top level of the binding. For backwards compatibility, the old 'properties: compatible: ...' form is still accepted for now, and is treated the same as a single-element 'compatible:'. The old syntax was inspired by dt-schema (though it isn't dt-schema-compatible), which is in turn a thin wrapper around json-schema (the idea is to transform .dts files into YAML and then verify them). Maybe the idea was to gradually switch the syntax over to dt-schema and then be able to use unmodified dt-schema bindings, but dt-schema is really a different kind of tool (a completely standalone linter), and works very differently from our stuff (see schemas/dt-core.yaml in the dt-schema repo to get an idea of just how differently). Better to keep it simple. This commit also piggybacks some clarifications to the binding template re. '#cells:'. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-08-20 02:32:25 +08:00			`compatible: "apa,apa102"`
led_strip: add a APA102 driver. The APA102 is a RGB LED with integrated controller. LEDs can be daisy-chained and use SPI for communication. The SPI port is configured via Device Tree. Tested on the Adafruit Trinket M0. Signed-off-by: Michael Hope <mlhx@google.com> 2018-02-13 05:35:20 +08:00
scripts: dts: Simplify and improve 'compatible' matching Instead of properties: compatible: constraint: "foo" , just have compatible: "foo" at the top level of the binding. For backwards compatibility, the old 'properties: compatible: ...' form is still accepted for now, and is treated the same as a single-element 'compatible:'. The old syntax was inspired by dt-schema (though it isn't dt-schema-compatible), which is in turn a thin wrapper around json-schema (the idea is to transform .dts files into YAML and then verify them). Maybe the idea was to gradually switch the syntax over to dt-schema and then be able to use unmodified dt-schema bindings, but dt-schema is really a different kind of tool (a completely standalone linter), and works very differently from our stuff (see schemas/dt-core.yaml in the dt-schema repo to get an idea of just how differently). Better to keep it simple. This commit also piggybacks some clarifications to the binding template re. '#cells:'. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-08-20 02:32:25 +08:00			`include: spi-device.yaml`