From: Stefan Wahren <stefan.wahren@i2se.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Eric Anholt <eric@anholt.net>, Arnd Bergmann <arnd@arndb.de>,
gregkh@linuxfoundation.org
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] dt-bindings: nvmem: add binding for Raspberry Pi OTP
Date: Wed, 21 Nov 2018 14:11:40 +0100 [thread overview]
Message-ID: <1542805904-6446-2-git-send-email-stefan.wahren@i2se.com> (raw)
In-Reply-To: <1542805904-6446-1-git-send-email-stefan.wahren@i2se.com>
This patch adds the devicetree binding for Raspberry Pi customer OTP
driver.
Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
---
.../nvmem/raspberrypi,bcm2835-customer-otp.txt | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/raspberrypi,bcm2835-customer-otp.txt
diff --git a/Documentation/devicetree/bindings/nvmem/raspberrypi,bcm2835-customer-otp.txt b/Documentation/devicetree/bindings/nvmem/raspberrypi,bcm2835-customer-otp.txt
new file mode 100644
index 0000000..041ff17
--- /dev/null
+++ b/Documentation/devicetree/bindings/nvmem/raspberrypi,bcm2835-customer-otp.txt
@@ -0,0 +1,22 @@
+Customer OTP Memory for Raspberry Pi
+
+The VC4 firmware exposes a mailbox interface that allows the ARM core
+to access the customer part of the OTP memory.
+
+The OTP node must be a child node of the Raspberry Pi firmware node.
+
+Required properties :
+- compatible : Should be "raspberrypi,bcm2835-customer-otp"
+
+See nvmem.txt for more information.
+
+Example:
+
+firmware: firmware-rpi {
+ compatible = "raspberrypi,bcm2835-firmware";
+ mboxes = <&mailbox>;
+
+ customer_otp: otp {
+ compatible = "raspberrypi,bcm2835-customer-otp";
+ };
+};
--
2.7.4
next prev parent reply other threads:[~2018-11-21 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 13:11 [PATCH 0/5] nvmem: Enable OTP access for Raspberry Pi Stefan Wahren
2018-11-21 13:11 ` Stefan Wahren [this message]
2018-12-06 23:49 ` [PATCH 1/5] dt-bindings: nvmem: add binding for Raspberry Pi OTP Rob Herring
2018-12-07 8:10 ` Stefan Wahren
2018-12-28 15:46 ` Stefan Wahren
2018-11-21 13:11 ` [PATCH 2/5] nvmem: add driver " Stefan Wahren
2018-11-21 13:11 ` [PATCH 3/5] ARM: dts: bcm2835-rpi: Enable OTP access for Raspberry Pi Stefan Wahren
2018-11-21 13:11 ` [PATCH 4/5] ARM: bcm2835_defconfig: Enable Raspberry Pi OTP driver Stefan Wahren
2018-11-21 13:11 ` [PATCH 5/5] ARM: multi_v7_defconfig: " Stefan Wahren
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=1542805904-6446-2-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=srinivas.kandagatla@linaro.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).