From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>,
"Rob Herring" <robh@kernel.org>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>
Subject: [PATCH 04/10] dt-bindings: nvmem: add Broadcom's NVRAM
Date: Tue, 30 Mar 2021 12:12:35 +0100 [thread overview]
Message-ID: <20210330111241.19401-5-srinivas.kandagatla@linaro.org> (raw)
In-Reply-To: <20210330111241.19401-1-srinivas.kandagatla@linaro.org>
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>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
---
.../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>;
+ };
--
2.21.0
next prev parent reply other threads:[~2021-03-30 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 11:12 [PATCH 00/10] nvmem: patches (set 1) for 5.13 Srinivas Kandagatla
2021-03-30 11:12 ` [PATCH 01/10] dt-bindings: nvmem: mediatek: add support for MediaTek mt8192 SoC Srinivas Kandagatla
2021-03-30 11:12 ` [PATCH 02/10] nvmem: convert comma to semicolon Srinivas Kandagatla
2021-03-30 11:12 ` [PATCH 03/10] drivers: nvmem: Fix voltage settings for QTI qfprom-efuse Srinivas Kandagatla
2021-03-30 11:12 ` Srinivas Kandagatla [this message]
2021-03-30 11:12 ` [PATCH 05/10] nvmem: brcm_nvram: new driver exposing Broadcom's NVRAM Srinivas Kandagatla
2021-03-30 11:12 ` [PATCH 06/10] nvmem: core: Add functions to make number reading easy Srinivas Kandagatla
2021-03-30 11:12 ` [PATCH 07/10] nvmem: core: Fix unintentional sign extension issue Srinivas Kandagatla
2021-03-30 11:12 ` [PATCH 08/10] nvmem: rmem: fix undefined reference to memremap Srinivas Kandagatla
2021-03-30 11:12 ` [PATCH 09/10] dt-bindings: nvmem: Add SoC compatible for sc7280 Srinivas Kandagatla
2021-03-30 11:12 ` [PATCH 10/10] nvmem: qfprom: Add support for fuse blowing on sc7280 Srinivas Kandagatla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210330111241.19401-5-srinivas.kandagatla@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).