zephyr/dts/bindings/flash_controller/nordic,nrf51-flash-controll...

description: Nordic NVMC (Non-Volatile Memory Controller)

compatible: "nordic,nrf51-flash-controller"

include: flash-controller.yaml
dts: bindings: Remove 'title:' and put all info. into 'description:' Add any useful information from 'title:' to the 'description:' strings (e.g. explanations of acronyms), and remove 'title:' as well as any copy-pasted "this binding gives a ..." boilerplate. Also clean some description strings up a bit. Some other things could probably be cleaned up (replacing 'GPIO node' with 'GPIO controller' on controllers for consistency, for example), but I kept things close to the original to avoid accidentally messing up. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-11-19 15:39:11 +08:00			`description: Nordic NVMC (Non-Volatile Memory Controller)`
dts: bindings: add support for the flash driver name So far, DT did not support the flash driver name. Any flash-controller should have the appropriate flash driver that should be identified by its name. This path adds generic support for extract the description from the flash-controller node, adds implementation of this property for all nrf5x targets. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no> 2018-01-22 21:48:38 +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			`compatible: "nordic,nrf51-flash-controller"`
dts: bindings: add support for the flash driver name So far, DT did not support the flash driver name. Any flash-controller should have the appropriate flash driver that should be identified by its name. This path adds generic support for extract the description from the flash-controller node, adds implementation of this property for all nrf5x targets. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no> 2018-01-22 21:48:38 +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: flash-controller.yaml`