The 88e1545 PHY has its interrupts wired to the VF610, so we might as
well use them.
Signed-off-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxx>
---
This is certainly not correct, as all PHYs on this device share the
same interrupt line, but we can't specify the pinmux settings
individually on each PHY. How should this be handled?
---
arch/arm/boot/dts/vf610-zii-dev-rev-b.dts | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts b/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
index 782b69a3acdf..d6786c5d0109 100644
--- a/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
+++ b/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
@@ -312,12 +312,20 @@
#size-cells = <0>;
switch2phy0: phy@0 {
+ interrupt-parent = <&gpio0>;
+ interrupts = <22 IRQ_TYPE_LEVEL_LOW>;
reg = <0>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_mv88e1545>;
};
switch2phy1: phy@1 {
+ interrupt-parent = <&gpio0>;
+ interrupts = <22 IRQ_TYPE_LEVEL_LOW>;
reg = <1>;
};
switch2phy2: phy@2 {
+ interrupt-parent = <&gpio0>;
+ interrupts = <22 IRQ_TYPE_LEVEL_LOW>;
reg = <2>;
};
};
@@ -488,6 +496,12 @@
>;
};
+ pinctrl_mv88e1545: pinctrl-mv88e1545 {
+ fsl,pins = <
+ VF610_PAD_PTB0__GPIO_22 0x219d
+ >;
+ };
+
pinctrl_pca9554_22: pinctrl-pca95540-22 {
fsl,pins = <
VF610_PAD_PTB28__GPIO_98 0x219d
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
