Browse Source

bindings: i2c: use consistent naming for i2c binding descriptions

Filenames of devictree binding documentation seems to be arbitrary and
for me it is unneeded hazzle to find the corresponding documentation for
a specific driver.

Naming the description the same as the driver is a lot easier and makes
sense to me since the driver defines the binding it understands.

Also, remove a reference in one source to the binding documentation, since path
information easily gets stale.

Signed-off-by: Wolfram Sang <wolfram@the-dreams.de>
Cc: Rob Herring <robherring2@gmail.com>
Cc: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
Wolfram Sang 12 years ago
parent
commit
16c4c52435

+ 0 - 0
Documentation/devicetree/bindings/i2c/atmel-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-at91.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/davinci.txt → Documentation/devicetree/bindings/i2c/i2c-davinci.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/gpio-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-gpio.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/fsl-imx-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-imx.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/fsl-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-mpc.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/mux.txt → Documentation/devicetree/bindings/i2c/i2c-mux.txt


+ 18 - 0
Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt

@@ -0,0 +1,18 @@
+
+* Marvell MV64XXX I2C controller
+
+Required properties :
+
+ - reg             : Offset and length of the register set for the device
+ - compatible      : Should be "marvell,mv64xxx-i2c"
+ - interrupts      : The interrupt number
+ - clock-frequency : Desired I2C bus clock frequency in Hz.
+
+Examples:
+
+	i2c@11000 {
+		compatible = "marvell,mv64xxx-i2c";
+		reg = <0x11000 0x20>;
+		interrupts = <29>;
+		clock-frequency = <100000>;
+	};

+ 0 - 0
Documentation/devicetree/bindings/i2c/nomadik.txt → Documentation/devicetree/bindings/i2c/i2c-nomadik.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/cavium-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-octeon.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/omap-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-omap.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/pnx.txt → Documentation/devicetree/bindings/i2c/i2c-pnx.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/ce4100-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-pxa-pci-ce4100.txt


+ 0 - 18
Documentation/devicetree/bindings/i2c/mrvl-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-pxa.txt

@@ -31,21 +31,3 @@ Examples:
 		reg = <0xd4025000 0x1000>;
 		interrupts = <58>;
 	};
-
-* Marvell MV64XXX I2C controller
-
-Required properties :
-
- - reg             : Offset and length of the register set for the device
- - compatible      : Should be "marvell,mv64xxx-i2c"
- - interrupts      : The interrupt number
- - clock-frequency : Desired I2C bus clock frequency in Hz.
-
-Examples:
-
-	i2c@11000 {
-		compatible = "marvell,mv64xxx-i2c";
-		reg = <0x11000 0x20>;
-		interrupts = <29>;
-		clock-frequency = <100000>;
-	};

+ 0 - 0
Documentation/devicetree/bindings/i2c/samsung-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-s3c2410.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/sirf-i2c.txt → Documentation/devicetree/bindings/i2c/i2c-sirf.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/arm-versatile.txt → Documentation/devicetree/bindings/i2c/i2c-versatile.txt


+ 0 - 0
Documentation/devicetree/bindings/i2c/xiic.txt → Documentation/devicetree/bindings/i2c/i2c-xiic.txt


+ 0 - 4
drivers/i2c/busses/i2c-ocores.c

@@ -9,10 +9,6 @@
  * kind, whether express or implied.
  */
 
-/*
- * This driver can be used from the device tree, see
- *     Documentation/devicetree/bindings/i2c/ocore-i2c.txt
- */
 #include <linux/kernel.h>
 #include <linux/module.h>
 #include <linux/init.h>