| Message ID | 20200512131334.1750-1-etienne.carriere@linaro.org (mailing list archive) |
|---|---|
| State | Mainlined |
| Commit | df5f3b6f5357202b86ed96071d258a9b8659154d |
| Headers | show |
| Series | [v2] dt-bindings: nvmem: stm32: new property for data access | expand |
On Tue, 12 May 2020 15:13:34 +0200, Etienne Carriere wrote: > From: Etienne Carriere <etienne.carriere@st.com> > > Introduce boolean property st,non-secure-otp for OTP data located > in a factory programmed area that only secure firmware can access > by default and that shall be reachable from the non-secure world. > > This change also allows additional properties for NVMEM nodes that > were forbidden prior this change. > > Signed-off-by: Etienne Carriere <etienne.carriere@st.com> > --- > Changes since v1: > Change nvmem.yaml to allow additional properties in NVMEM nodes. > > Link to v1: > https://lore.kernel.org/patchwork/patch/1239028/ > > .../devicetree/bindings/nvmem/nvmem.yaml | 2 -- > .../bindings/nvmem/st,stm32-romem.yaml | 17 +++++++++++++++++ > 2 files changed, 17 insertions(+), 2 deletions(-) > Applied, thanks!
diff --git a/Documentation/devicetree/bindings/nvmem/nvmem.yaml b/Documentation/devicetree/bindings/nvmem/nvmem.yaml index 65980224d550..b459f9dba6c9 100644 --- a/Documentation/devicetree/bindings/nvmem/nvmem.yaml +++ b/Documentation/devicetree/bindings/nvmem/nvmem.yaml @@ -67,8 +67,6 @@ patternProperties: required: - reg - additionalProperties: false - examples: - | #include <dt-bindings/gpio/gpio.h> diff --git a/Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml b/Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml index d84deb4774a4..c11c99f085d7 100644 --- a/Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml +++ b/Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml @@ -24,6 +24,18 @@ properties: - st,stm32f4-otp - st,stm32mp15-bsec +patternProperties: + "^.*@[0-9a-f]+$": + type: object + + properties: + st,non-secure-otp: + description: | + This property explicits a factory programmed area that both secure + and non-secure worlds can access. It is needed when, by default, the + related area can only be reached by the secure world. + type: boolean + required: - "#address-cells" - "#size-cells" @@ -41,6 +53,11 @@ examples: calib@22c { reg = <0x22c 0x2>; }; + + mac_addr@e4 { + reg = <0xe4 0x8>; + st,non-secure-otp; + }; }; ...