[PATCH v3 1/2] devicetree: add binding for Aurora VLSI NB8800 Ethernet controller

[Mans Rullgard]

This adds a binding for the Aurora VLSI NB8800 Ethernet controller
using the "aurora,nb8800" compatible string.  When used in Sigma
Designs chips a few additional features are available.  These variants
are indicated by a "sigma,<chip>-ethernet" compatible string.

Signed-off-by: Mans Rullgard <mans@xxxxxxxxx>
---
Changes:
- added phy child node
---
 .../devicetree/bindings/net/aurora,nb8800.txt      | 37 ++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/net/aurora,nb8800.txt

diff --git a/Documentation/devicetree/bindings/net/aurora,nb8800.txt b/Documentation/devicetree/bindings/net/aurora,nb8800.txt
new file mode 100644
index 0000000..df12ff1
--- /dev/null
+++ b/Documentation/devicetree/bindings/net/aurora,nb8800.txt
@@ -0,0 +1,37 @@
+* Aurora VLSI AU-NB8800 Ethernet controller
+
+Required properties:
+- compatible: Should be "sigma,<chip>-ethernet", "aurora,nb8800"
+- reg: Should be MMIO address space of the device
+- interrupts: Should contain the interrupt specifier for the device
+- interrupt-parent: Should be a phandle for the interrupt controller
+- clocks: Should be a phandle for the clock for the device
+- #address-cells: Should be <1>
+- #size-cells: Should be <0>
+
+Common properties described in ethernet.txt:
+- local-mac-address
+- mac-address
+- phy-handle
+- phy-mode
+
+The attached PHY should be specified in a child node as per phy.txt.
+
+Example:
+
+ethernet@26000 {
+	compatible = "sigma,smp8642-ethernet", "aurora,nb8800";
+	reg = <0x26000 0x800>;
+	interrupts = <38>;
+	clocks = <&sys_clk>;
+	max-speed = <1000>;
+	phy-connection-type = "rgmii";
+	phy-handle = <&eth0_phy>;
+	#address-cells = <1>;
+	#size-cells = <0>;
+
+	eth0_phy: ethernet-phy@1 {
+		compatible = "ethernet-phy-ieee802.3-c22";
+		reg = <1>;
+	};
+};
-- 
2.6.2

--
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/