Re: [PATCH 10/10] mtd: ngpmb_nvram: Add bindings for Juniper's ngpmb NVRAM
From: Rob Herring <hidden>
Date: 2016-10-10 18:18:51
Also in:
linux-gpio, linux-i2c, linux-watchdog, lkml
On Fri, Oct 07, 2016 at 06:17:31PM +0300, Pantelis Antoniou wrote:
quoted hunk ↗ jump to hunk
From: Georgi Vlaev <redacted> Add device tree binging document for the ngpmb NVRAM device. Signed-off-by: Georgi Vlaev <redacted> [Ported from Juniper kernel] Signed-off-by: Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org> --- .../devicetree/bindings/mtd/ngpmb-nvram.txt | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 Documentation/devicetree/bindings/mtd/ngpmb-nvram.txtdiff --git a/Documentation/devicetree/bindings/mtd/ngpmb-nvram.txt b/Documentation/devicetree/bindings/mtd/ngpmb-nvram.txt new file mode 100644 index 0000000..297ad0e --- /dev/null +++ b/Documentation/devicetree/bindings/mtd/ngpmb-nvram.txt
mtd is really flash. sram/ or nvmem/ are probably better choices.
quoted hunk ↗ jump to hunk
@@ -0,0 +1,22 @@ +Non Volatile RAM device on a Juniper NG PMB FPGA + +These devices are found in the PTX series of Juniper routers. + +Required properties: +- compatible : must be "jnx,ngpmb-nvram"
Compatible with mmio-sram?
+ +Optional properties: +- reg : memory address for the RAM, note that this is not +required since usually the device is a subdevice of the SAM MFD +driver which fills in the register fields. + +For the rest of the properties, see mtd-physmap.txt. + +The device tree may optionally contain sub-nodes describing partitions of the +address space. See partition.txt for more detail.
sram or nvmem style partitioning is probably more appropriate.
+
+Example:
+
+ngpmb_nvram {
+ compatible = "jnx,ngpmb-nvram";
+};
--
1.9.1-- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html