Re: [PATCH V2 1/2] dt-bindings: nvmem: add Broadcom's NVRAM

[Srinivas Kandagatla]

On 05/03/2021 18:32, Rafał Miłecki wrote:

From: Rafał Miłecki 

Broadcom's NVRAM structure contains device data and can be accessed
using I/O mapping.

Signed-off-by: Rafał Miłecki 
---



Applied both patches!


thanks
-srini


V2: Use Broadcom's NVRAM specific binding. Generic "nvmem-iomap" binding
 didn't make much sense. Thanks Srinivas!
---
  .../devicetree/bindings/nvmem/brcm,nvram.yaml | 34 +++
  1 file changed, 34 insertions(+)
  create mode 100644 Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml

diff --git a/Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml 
b/Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml
new file mode 100644
index ..58ff6b0bdb1a
--- /dev/null
+++ b/Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml
@@ -0,0 +1,34 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/nvmem/brcm,nvram.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Broadcom's NVRAM
+
+description: |
+  Broadcom's NVRAM is a structure containing device specific environment
+  variables. It is used for storing device configuration, booting parameters
+  and calibration data.
+
+  NVRAM can be accessed on Broadcom BCM47xx MIPS and Northstar ARM Cortex-A9
+  devices usiong I/O mapped memory.
+
+maintainers:
+  - Rafał Miłecki 
+
+allOf:
+  - $ref: "nvmem.yaml#"
+
+properties:
+  compatible:
+const: brcm,nvram
+
+unevaluatedProperties: false
+
+examples:
+  - |
+nvram@1eff {
+compatible = "brcm,nvram";
+reg = <0x1eff 0x1>;
+};

Re: [PATCH V2 1/2] dt-bindings: nvmem: add Broadcom's NVRAM

[Rob Herring]

On Fri, 05 Mar 2021 19:32:35 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki 
> 
> Broadcom's NVRAM structure contains device data and can be accessed
> using I/O mapping.
> 
> Signed-off-by: Rafał Miłecki 
> ---
> V2: Use Broadcom's NVRAM specific binding. Generic "nvmem-iomap" binding
> didn't make much sense. Thanks Srinivas!
> ---
>  .../devicetree/bindings/nvmem/brcm,nvram.yaml | 34 +++
>  1 file changed, 34 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml
> 

Reviewed-by: Rob Herring 

[PATCH V2 1/2] dt-bindings: nvmem: add Broadcom's NVRAM

[Rafał Miłecki]

From: Rafał Miłecki 

Broadcom's NVRAM structure contains device data and can be accessed
using I/O mapping.

Signed-off-by: Rafał Miłecki 
---
V2: Use Broadcom's NVRAM specific binding. Generic "nvmem-iomap" binding
didn't make much sense. Thanks Srinivas!
---
 .../devicetree/bindings/nvmem/brcm,nvram.yaml | 34 +++
 1 file changed, 34 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml

diff --git a/Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml 
b/Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml
new file mode 100644
index ..58ff6b0bdb1a
--- /dev/null
+++ b/Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml
@@ -0,0 +1,34 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/nvmem/brcm,nvram.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Broadcom's NVRAM
+
+description: |
+  Broadcom's NVRAM is a structure containing device specific environment
+  variables. It is used for storing device configuration, booting parameters
+  and calibration data.
+
+  NVRAM can be accessed on Broadcom BCM47xx MIPS and Northstar ARM Cortex-A9
+  devices usiong I/O mapped memory.
+
+maintainers:
+  - Rafał Miłecki 
+
+allOf:
+  - $ref: "nvmem.yaml#"
+
+properties:
+  compatible:
+const: brcm,nvram
+
+unevaluatedProperties: false
+
+examples:
+  - |
+nvram@1eff {
+compatible = "brcm,nvram";
+reg = <0x1eff 0x1>;
+};
-- 
2.26.2