zephyr/dts/bindings/arm/atmel,sam0-sercom.yaml

title: Atmel SERCOM binding

description: >
    Binding for the Atmel SAM0 multi-protocol (UART, SPI, I2C) SERCOM unit.

compatible: "atmel,sam0-sercom"

include: base.yaml

properties:
    reg:
      required: true

    interrupts:
      required: true
spi: sam0: use Device Tree for configuration. Switch the SoC device tree to define a single entry per SERCOM instead of one per mode. Define a Device Tree binding for the SAM0 SPI and use it instead of Kconfig for enabling / disabaling instances Switch the Arduino Zero, Adafruit Feather M0 Basic Proto, and Trinket M0 to use the new defintion. Add the APA102 LED that's on the Trinket as a test. Signed-off-by: Michael Hope <mlhx@google.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2018-01-29 03:13:54 +08:00			`title: Atmel SERCOM binding`

			`description: >`
			`Binding for the Atmel SAM0 multi-protocol (UART, SPI, I2C) SERCOM unit.`

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: "atmel,sam0-sercom"`

dts/bindings: Convert bindings to new include syntax Convert from: inherits: !include spi-device.yaml to: include: spi-device.yaml Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-08-22 07:10:12 +08:00			`include: base.yaml`
dts/bindings: Move common properties into a base.yaml Move common properties like 'compatible', 'reg', 'reg-names', 'interrupts', 'interrupt-names', and 'label' into one common base.yaml that all the other yaml's can inherit from. This removes both duplication and inconsistent definition. The device specific yamls just need to say if a property is 'required' or not. NOTE: due to some generation conflicts we did not covert 'soc-nv-flash.yaml' to use base.yaml. Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-06-08 00:12:49 +08:00
spi: sam0: use Device Tree for configuration. Switch the SoC device tree to define a single entry per SERCOM instead of one per mode. Define a Device Tree binding for the SAM0 SPI and use it instead of Kconfig for enabling / disabaling instances Switch the Arduino Zero, Adafruit Feather M0 Basic Proto, and Trinket M0 to use the new defintion. Add the APA102 LED that's on the Trinket as a test. Signed-off-by: Michael Hope <mlhx@google.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2018-01-29 03:13:54 +08:00			`properties:`
			`reg:`
dts: bindings: Have 'required: true/false' instead of 'category: ...' The 'category: required/optional' setting for properties is just a yes/no thing. Using a boolean makes it clearer, so have 'required: true/false' instead. Print a clear error when 'category:' is used: edtlib.EDTError: please put 'required: true' instead of 'category: required' in 'properties: foo: ...' in test-bindings/sub-node-parent.yaml - 'category' has been removed The old scripts in scripts/dts/ ignore this setting, and only print a warning if 'category: required' in an inherited binding is changed to 'category: optional'. Remove that code, since the new scripts already have the same check. The replacement was done with git ls-files 'dts/bindings/.yaml' \| xargs sed -i \ -e 's/category:\srequired/required: true/' \ -e 's/category:\s*optional/required: false/' dts/binding-template.yaml is updated as well. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-08-28 06:22:01 +08:00			`required: true`
spi: sam0: use Device Tree for configuration. Switch the SoC device tree to define a single entry per SERCOM instead of one per mode. Define a Device Tree binding for the SAM0 SPI and use it instead of Kconfig for enabling / disabaling instances Switch the Arduino Zero, Adafruit Feather M0 Basic Proto, and Trinket M0 to use the new defintion. Add the APA102 LED that's on the Trinket as a test. Signed-off-by: Michael Hope <mlhx@google.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2018-01-29 03:13:54 +08:00
			`interrupts:`
dts: bindings: Have 'required: true/false' instead of 'category: ...' The 'category: required/optional' setting for properties is just a yes/no thing. Using a boolean makes it clearer, so have 'required: true/false' instead. Print a clear error when 'category:' is used: edtlib.EDTError: please put 'required: true' instead of 'category: required' in 'properties: foo: ...' in test-bindings/sub-node-parent.yaml - 'category' has been removed The old scripts in scripts/dts/ ignore this setting, and only print a warning if 'category: required' in an inherited binding is changed to 'category: optional'. Remove that code, since the new scripts already have the same check. The replacement was done with git ls-files 'dts/bindings/.yaml' \| xargs sed -i \ -e 's/category:\srequired/required: true/' \ -e 's/category:\s*optional/required: false/' dts/binding-template.yaml is updated as well. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-08-28 06:22:01 +08:00			`required: true`