[PATCH RFC 1/3] dt-bindings: nvmem: add binding for Raspberry Pi OTP
From: robh@kernel.org (Rob Herring)
Date: 2018-03-18 12:48:15
Also in:
linux-devicetree
On Fri, Mar 09, 2018 at 02:32:06PM +0100, Stefan Wahren wrote:
quoted hunk ↗ jump to hunk
This patch adds the devicetree binding for Raspberry Pi customer OTP driver. Signed-off-by: Stefan Wahren <redacted> --- .../nvmem/raspberrypi,bcm2835-customer-otp.txt | 27 ++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/raspberrypi,bcm2835-customer-otp.txtdiff --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..3f57744 --- /dev/null +++ b/Documentation/devicetree/bindings/nvmem/raspberrypi,bcm2835-customer-otp.txt@@ -0,0 +1,27 @@ +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" +- #address-cells : Should be 1 +- #size-cells : Should be 1 + +See nvmem.txt for more information. + +Example: + +firmware: firmware-rpi { + compatible = "raspberrypi,bcm2835-firmware"; + mboxes = <&mailbox>; + + customer_otp: otp { + compatible = "raspberrypi,bcm2835-customer-otp"; + firmware = <&firmware>;
Not documented nor necessary. It's the parent.
+ #address-cells = <1>; + #size-cells = <1>;
Are there some child nodes? If not, there's no point in having this node. Rob