On 21.10.2014 13:31, Sergei Shtylyov wrote:

Hello.

On 10/21/2014 12:53 PM, Sebastian Hesselbarth wrote:

quoted

From: Antoine T?nart <redacted>

quoted

Internal FastEthernet PHY on BG2Q is connected via MII, add a
corresponding phy-connection-type property.

quoted

Tested-by: Antoine T?nart <redacted>
Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
---
Cc: "David S. Miller" <davem@davemloft.net>
Cc: "Antoine T?nart" <redacted>
Cc: Florian Fainelli <f.fainelli@gmail.com>
Cc: Eric Miao <redacted>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
Cc: linux-arm-kernel at lists.infradead.org
Cc: netdev at vger.kernel.org
Cc: devicetree at vger.kernel.org
Cc: linux-kernel at vger.kernel.org
---
  arch/arm/boot/dts/berlin2q.dtsi | 1 +
  1 file changed, 1 insertion(+)

quoted

diff --git a/arch/arm/boot/dts/berlin2q.dtsi

b/arch/arm/boot/dts/berlin2q.dtsi
index 891d56b03922..6dbc520bddc1 100644

--- a/arch/arm/boot/dts/berlin2q.dtsi
+++ b/arch/arm/boot/dts/berlin2q.dtsi

@@ -127,6 +127,7 @@
              status = "disabled";

              ethphy0: ethernet-phy at 0 {
+                phy-connection-type = "mii";

    You're adding this prop to the PHY node? That's very weird...
normally, it's a property of a MDIO bus node.

Sergei,

How can this be a property of the MDIO bus node? Just think of an MDIO
bus with two PHYs where one is connected via GMII and the other via
RGMII? How should this work?

But you are right that the property should not be part of the PHY node
but the controller node instead. I'll rework and send an update, thanks
for the hint.

Sebastian