[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4be3e736-8bd5-b9e4-9c5b-e69b164e152d@linaro.org>
Date: Wed, 10 Mar 2021 10:23:36 +0000
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Rafał Miłecki <zajec5@...il.com>,
Rob Herring <robh+dt@...nel.org>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mips@...r.kernel.org,
Florian Fainelli <f.fainelli@...il.com>,
Vivek Unune <npcomplete13@...il.com>,
bcm-kernel-feedback-list@...adcom.com,
linux-kernel@...r.kernel.org,
Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH V2 1/2] dt-bindings: nvmem: add Broadcom's NVRAM
On 05/03/2021 18:32, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> Broadcom's NVRAM structure contains device data and can be accessed
> using I/O mapping.
>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.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@...ecki.pl>
> +
> +allOf:
> + - $ref: "nvmem.yaml#"
> +
> +properties:
> + compatible:
> + const: brcm,nvram
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + nvram@...f0000 {
> + compatible = "brcm,nvram";
> + reg = <0x1eff0000 0x10000>;
> + };
>
Powered by blists - more mailing lists