From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752492AbcEYV2A (ORCPT ); Wed, 25 May 2016 17:28:00 -0400 Received: from mail-pa0-f50.google.com ([209.85.220.50]:34617 "EHLO mail-pa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751119AbcEYV07 (ORCPT ); Wed, 25 May 2016 17:26:59 -0400 From: Moritz Fischer To: dwmw2@infradead.org Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, devicetree@vger.kernel.org, computersforpeace@gmail.com, boris.brezillon@free-electrons.com, Moritz Fischer Subject: [RFC/PATCH 1/2] doc: bindings: Add bindings documentation for mtd otp nvmem Date: Wed, 25 May 2016 14:26:46 -0700 Message-Id: <1464211607-8843-2-git-send-email-moritz.fischer@ettus.com> X-Mailer: git-send-email 2.5.5 In-Reply-To: <1464211607-8843-1-git-send-email-moritz.fischer@ettus.com> References: <1464211607-8843-1-git-send-email-moritz.fischer@ettus.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This commit adds documentation describing the bindings for exposing mtd flash otp regions as nvmem providers via devicetree. Signed-off-by: Moritz Fischer --- .../devicetree/bindings/mtd/otp-nvmem.txt | 62 ++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 Documentation/devicetree/bindings/mtd/otp-nvmem.txt diff --git a/Documentation/devicetree/bindings/mtd/otp-nvmem.txt b/Documentation/devicetree/bindings/mtd/otp-nvmem.txt new file mode 100644 index 0000000..a83a7da --- /dev/null +++ b/Documentation/devicetree/bindings/mtd/otp-nvmem.txt @@ -0,0 +1,62 @@ +Representing OTP regions in devicetree + +OTP regions can be represented by sub-nodes of an mtd device. + +The partition table should be a subnode of the mtd node and should be names +'otp-partitions'. This node should have the following property: + +- compatible: (required) must be 'fixed-partitions' + +OTP regions are then defined in subnodes of the partitions node. + +Required properties for OTP regions: +- reg: The region's offset and size within the mtd device + +Optional properties: +- label: The label / name for this region. If ommited, the label is taken + from the node name (excluding the unit address). + +Example: + +flash@0 { + partitions { + compatible = "fixed-partitions"; + #address-cells = <1>; + #size-cells = <1>; + + partition@0 { + label = "uboot-spl"; + reg = <0x0 0xe0000>; + }; + partition@1 { + label = "uboot-env"; + reg = <0xe0000 0x20000>; + }; + partition@2 { + label = "uboot"; + reg = <0x100000 0x100000>; + }; + }; + + otp-partitions { + compatible = "fixed-partitions"; + #address-cells = <1>; + #size-cells = <1>; + + region@0 { + label = "factory-data"; + reg = <0x0 0x40>; + + #address-cells = <0x1>; + #size-cells = <0x1>; + + product: nvmem@0 { + reg = <0x0 0x2>; + }; + + revision: nvmem@3 { + reg = <0x3 0x2>; + }; + }; + }; +} -- 2.5.5