Add the binding to expose MTD partitions as nvmem providers.

Signed-off-by: Alban <al...@free.fr>
---
 .../devicetree/bindings/nvmem/mtd-nvmem.txt        | 29 ++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/nvmem/mtd-nvmem.txt

diff --git a/Documentation/devicetree/bindings/nvmem/mtd-nvmem.txt 
b/Documentation/devicetree/bindings/nvmem/mtd-nvmem.txt
new file mode 100644
index 0000000..47602f7
--- /dev/null
+++ b/Documentation/devicetree/bindings/nvmem/mtd-nvmem.txt
@@ -0,0 +1,29 @@
+= NVMEM in MTD =
+
+Config data for drivers is often stored in MTD devices. This binding
+define how such data can be represented in device tree.
+
+An MTD can be defined as an NVMEM provider by adding the `nvmem-provider`
+property to their node. Data cells can then be defined as child nodes
+of the partition as defined in nvmem.txt.
+
+Example:
+
+       flash@0 {
+               ...
+
+               partition@2 {
+                       label = "art";
+                       reg = <0x7F0000 0x010000>;
+                       read-only;
+
+                       nvmem-provider;
+                       #address-cells = <1>;
+                       #size-cells = <1>;
+
+                       eeprom@1000 {
+                               label = "wmac-eeprom";
+                               reg = <0x1000 0x1000>;
+                       };
+               };
+       };
-- 
2.7.4

Reply via email to