Skip to contentSkip to conversation

dt-bindings: mtd: Convert mtd-physmap to DT schema

PATCH In review Rob Herring 3 participants 3 messages Jun 7, 2021 – Jun 9, 2021

Subsystems (3)
Device tree bindings Memory technology devices (MTD) Arm integrator, versatile and realview support
lore
Share & tools
lore

Rob Herring

author maintainer
#0 lore raw

PATCH 1/1 dt-bindings: mtd: Convert mtd-physmap to DT schema

Convert the mtd-physmap binding to DT schema format. The arm-versatile, cypress,hyperflash and intel,ixp4xx-flash are all just an additional compatible string, so they are all merged into the main schema.

There doesn't appear to be any users nor support for 'vendor-id' and 'device-id', so these have been dropped.

Cc Linus Walleij <[email protected]>
Cc Miquel Raynal <[email protected]>
Cc Richard Weinberger <[email protected]>
Cc Vignesh Raghavendra <[email protected]>
Cc [email protected]
Signed-off-by Rob Herring <[email protected]>
---
 .../devicetree/bindings/mtd/arm-versatile.txt |  26 ---
 .../bindings/mtd/cypress,hyperflash.txt       |  13 --
 .../bindings/mtd/intel,ixp4xx-flash.txt       |  22 --
 .../devicetree/bindings/mtd/mtd-physmap.txt   | 114 ----------
 .../devicetree/bindings/mtd/mtd-physmap.yaml  | 208 ++++++++++++++++++
 5 files changed, 208 insertions(+), 175 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/mtd/arm-versatile.txt
 delete mode 100644 Documentation/devicetree/bindings/mtd/cypress,hyperflash.txt
 delete mode 100644 Documentation/devicetree/bindings/mtd/intel,ixp4xx-flash.txt
 delete mode 100644 Documentation/devicetree/bindings/mtd/mtd-physmap.txt
 create mode 100644 Documentation/devicetree/bindings/mtd/mtd-physmap.yaml
Documentation/devicetree/bindings/mtd/arm-versatile.txt deleted +0 -26
deleted file mode 100644
index 4ec28796a3c0..000000000000
@@ -1,26 +0,0 @@
-Flash device on ARM Versatile board
-
-These flash chips are found in the ARM reference designs like Integrator,
-Versatile, RealView, Versatile Express etc.
-
-They are regular CFI compatible (Intel or AMD extended) flash chips with
-some special write protect/VPP bits that can be controlled by the machine's
-system controller.
-
-Required properties:
-- compatible : must be "arm,versatile-flash", "cfi-flash";
-- reg : memory address for the flash chip
-- bank-width : width in bytes of flash interface.
-
-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.
-
-Example:
-
-flash@34000000 {
-	compatible = "arm,versatile-flash", "cfi-flash";
-	reg = <0x34000000 0x4000000>;
-	bank-width = <4>;
-};
Documentation/devicetree/bindings/mtd/cypress,hyperflash.txt deleted +0 -13
deleted file mode 100644
index ad42f4db32f1..000000000000
@@ -1,13 +0,0 @@
-Bindings for HyperFlash NOR flash chips compliant with Cypress HyperBus
-specification and supports Cypress CFI specification 1.5 command set.
-
-Required properties:
-- compatible : "cypress,hyperflash", "cfi-flash" for HyperFlash NOR chips
-- reg : Address of flash's memory map
-
-Example:
-
-	flash@0 {
-		compatible = "cypress,hyperflash", "cfi-flash";
-		reg = <0x0 0x4000000>;
-	};
Documentation/devicetree/bindings/mtd/intel,ixp4xx-flash.txt deleted +0 -22
deleted file mode 100644
index 4bdcb92ae381..000000000000
@@ -1,22 +0,0 @@
-Flash device on Intel IXP4xx SoC
-
-This flash is regular CFI compatible (Intel or AMD extended) flash chips with
-specific big-endian or mixed-endian memory access pattern.
-
-Required properties:
-- compatible : must be "intel,ixp4xx-flash", "cfi-flash";
-- reg : memory address for the flash chip
-- bank-width : width in bytes of flash interface, should be <2>
-
-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.
-
-Example:
-
-flash@50000000 {
-	compatible = "intel,ixp4xx-flash", "cfi-flash";
-	reg = <0x50000000 0x01000000>;
-	bank-width = <2>;
-};
Documentation/devicetree/bindings/mtd/mtd-physmap.txt deleted +0 -114

114 lines not on this page · raw message

Documentation/devicetree/bindings/mtd/mtd-physmap.yaml new file +208 -0

208 lines not on this page · raw message

Signature · 1 line
2.27.0
maintainer Reviewed-by on v1 1/1
#1 lore raw

Hi Rob,

Rob Herring <[email protected]> wrote on Mon, 7 Jun 2021 14:35:00 -0500:

Quoted 7 lines

Convert the mtd-physmap binding to DT schema format. The arm-versatile, cypress,hyperflash and intel,ixp4xx-flash are all just an additional compatible string, so they are all merged into the main schema.

There doesn't appear to be any users nor support for 'vendor-id' and 'device-id', so these have been dropped.

Quoted 6 lines
Cc Linus Walleij <[email protected]>
Cc Miquel Raynal <[email protected]>
Cc Richard Weinberger <[email protected]>
Cc Vignesh Raghavendra <[email protected]>
Cc [email protected]
Signed-off-by Rob Herring <[email protected]>
Reviewed-by Miquel Raynal <[email protected]>

Thanks,
Miquèl

Reviewed-by on v1 1/1
#2 lore raw
In reply to Rob Herring
Quoted 7 lines · Rob Herring

Convert the mtd-physmap binding to DT schema format. The arm-versatile, cypress,hyperflash and intel,ixp4xx-flash are all just an additional compatible string, so they are all merged into the main schema.

There doesn't appear to be any users nor support for 'vendor-id' and 'device-id', so these have been dropped.

Quoted 6 lines
Cc Linus Walleij <[email protected]>
Cc Miquel Raynal <[email protected]>
Cc Richard Weinberger <[email protected]>
Cc Vignesh Raghavendra <[email protected]>
Cc [email protected]
Signed-off-by Rob Herring <[email protected]>

Very nice, thanks for doing this!

Reviewed-by Linus Walleij <[email protected]>

Yours,
Linus Walleij