netdev - Re: Device Tree Binding for Marvell DSA Switch on imx28 board over Mdio Interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141117160934.GR2001@lunn.ch>
Date:	Mon, 17 Nov 2014 17:09:34 +0100
From:	Andrew Lunn <andrew@...n.ch>
To:	Oliver Graute <oliver.graute@...il.com>
Cc:	netdev@...r.kernel.org, andrew@...n.ch,
	Florian Fainelli <f.fainelli@...il.com>, buytenh@...tstofly.org
Subject: Re: Device Tree Binding for Marvell DSA Switch on imx28 board over
 Mdio Interface

> dsa@0 {
>         compatible = "marvell,dsa";
>         #address-cells = <2>;
>         #size-cells = <0>;
> 
>         interrupts = <10>;
>         //dsa,ethernet = <&ethphy1>;
>         //dsa,ethernet = <&eth1>;
>         dsa,ethernet = <&mac1>;
>         //dsa,ethernet = <&mac0>;
>         dsa,mii-bus = <&mdio_bus>;
> 
>         switch@0 {
>             #address-cells = <1>;
>             #size-cells = <0>;
>             reg = <5 0>;   /* MDIO address 5, switch 0 in tree */

Hi Oliver

How do you have the strapping pins on the switch set? They determine
what address on the mdio bus the chip responds to.

Does your u-boot have commands to read arbitrary phy registers?
Generally, reading a register that does not exist gives 0xffff.  So
try some reads at different addresses and see what you can find.

    Andrew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html