OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/dts/bindings/flash_controller/nordic,nrf91-flash-controll...

9 lines
176 B
YAML
Raw Normal View History

dts: nordic: add missing nRF91 flash controller binding This commits adds the binding for nRF9160 flash controller. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2019-01-15 21:16:10 +08:00
title: Nordic NVMC
dts: bindings: Preserve newlines in descriptions With https://github.com/zephyrproject-rtos/zephyr/pull/20185, multi-line descriptions will be formatted nicely, but using '>' breaks it, because it removes internal newlines (including between paragraphs). See https://yaml-multiline.info/. Replace 'description: >' with 'description: |' to encourage '|'. That'll prevent '>' from getting copied around and messing up long descriptions. This will lead to some extra newlines in the output, but it's fine. Line-wrapping messes up any manual formatting. The replacement was done with $ git ls-files 'dts/bindings/*.yaml' | \ xargs sed -i 's/description:\s*>/description: |/' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-10-29 00:34:12 +08:00
description: |
dts: nordic: add missing nRF91 flash controller binding This commits adds the binding for nRF9160 flash controller. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2019-01-15 21:16:10 +08:00
This binding gives a base representation of the Nordic NVMC
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,nrf91-flash-controller"
dts: nordic: add missing nRF91 flash controller binding This commits adds the binding for nRF9160 flash controller. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2019-01-15 21:16:10 +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