[PATCH v4 01/10] mtd: st_spi_fsm: dt-bindings: Deprecate generic compatible string

From: Lee Jones
Date: Wed Jan 21 2015 - 10:25:13 EST


This driver now obtains platform information via DT matching, which requires
a compatible string per platform. This change introduces the new specific
strings and deprecates the old generic one.

We also take out all of the old, unused properties which are no longer
required.

Cc: devicetree@xxxxxxxxxxxxxxx
Signed-off-by: Lee Jones <lee.jones@xxxxxxxxxx>
---
Documentation/devicetree/bindings/mtd/st-fsm.txt | 19 ++++++-------------
1 file changed, 6 insertions(+), 13 deletions(-)

diff --git a/Documentation/devicetree/bindings/mtd/st-fsm.txt b/Documentation/devicetree/bindings/mtd/st-fsm.txt
index c248939..389e43d 100644
--- a/Documentation/devicetree/bindings/mtd/st-fsm.txt
+++ b/Documentation/devicetree/bindings/mtd/st-fsm.txt
@@ -1,26 +1,19 @@
* ST-Microelectronics SPI FSM Serial (NOR) Flash Controller

Required properties:
- - compatible : Should be "st,spi-fsm"
+ - compatible : Should be one of;
+ "st,stid127-spi-fsm"
+ "st,stih407-spi-fsm"
+ "st,stih416-spi-fsm"
- reg : Contains register's location and length.
- - reg-names : Should contain the reg names "spi-fsm"
- interrupts : The interrupt number
- pinctrl-0 : Standard Pinctrl phandle (see: pinctrl/pinctrl-bindings.txt)
-
-Optional properties:
- - st,syscfg : Phandle to boot-device system configuration registers
- - st,boot-device-reg : Address of the aforementioned boot-device register(s)
- - st,boot-device-spi : Expected boot-device value if booted via this device
+ - st,syscfg : Phandle to boot-device system configuration registers

Example:
spifsm: spifsm@fe902000{
- compatible = "st,spi-fsm";
+ compatible = "st,stih407-spi-fsm";
reg = <0xfe902000 0x1000>;
- reg-names = "spi-fsm";
pinctrl-0 = <&pinctrl_fsm>;
st,syscfg = <&syscfg_rear>;
- st,boot-device-reg = <0x958>;
- st,boot-device-spi = <0x1a>;
- status = "okay";
};
-
--
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/