zephyr/dts/bindings/flash_controller/nxp,kinetis-ftfe.yaml

description: NXP Kinetis Flash Memory Module E (FTFE)

compatible: "nxp,kinetis-ftfe"

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: NXP Kinetis Flash Memory Module E (FTFE)`
drivers: flash: NXP k6x/kw2xd: Convert to use device tree Convert NXP k6x and kw2xd flash driver to use device tree to get the flash controller name from device tree. We introduce yaml bindings for the "nxp,kinetis-ftfe" and "nxp,kinetis-ftfl" devices. Fixes: #5788 Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2018-01-19 03:40:18 +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: "nxp,kinetis-ftfe"`
drivers: flash: NXP k6x/kw2xd: Convert to use device tree Convert NXP k6x and kw2xd flash driver to use device tree to get the flash controller name from device tree. We introduce yaml bindings for the "nxp,kinetis-ftfe" and "nxp,kinetis-ftfl" devices. Fixes: #5788 Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2018-01-19 03:40:18 +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`