| Message ID | 20210305183236.11784-1-zajec5@gmail.com |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
| Series | [V2,1/2] dt-bindings: nvmem: add Broadcom's NVRAM | expand |
| Context | Check | Description |
|---|---|---|
| robh/checkpatch | success | |
| robh/dt-meta-schema | success | |
| robh/dtbs-check | success |
On Fri, 05 Mar 2021 19:32:35 +0100, Rafał Miłecki wrote: > From: Rafał Miłecki <rafal@milecki.pl> > > Broadcom's NVRAM structure contains device data and can be accessed > using I/O mapping. > > Signed-off-by: Rafał Miłecki <rafal@milecki.pl> > --- > 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 <robh@kernel.org>
On 05/03/2021 18:32, Rafał Miłecki wrote: > From: Rafał Miłecki <rafal@milecki.pl> > > Broadcom's NVRAM structure contains device data and can be accessed > using I/O mapping. > > Signed-off-by: Rafał Miłecki <rafal@milecki.pl> > --- 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 000000000000..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 <rafal@milecki.pl> > + > +allOf: > + - $ref: "nvmem.yaml#" > + > +properties: > + compatible: > + const: brcm,nvram > + > +unevaluatedProperties: false > + > +examples: > + - | > + nvram@1eff0000 { > + compatible = "brcm,nvram"; > + reg = <0x1eff0000 0x10000>; > + }; >
diff --git a/Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml b/Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml new file mode 100644 index 000000000000..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 <rafal@milecki.pl> + +allOf: + - $ref: "nvmem.yaml#" + +properties: + compatible: + const: brcm,nvram + +unevaluatedProperties: false + +examples: + - | + nvram@1eff0000 { + compatible = "brcm,nvram"; + reg = <0x1eff0000 0x10000>; + };