netdev - Re: i.mx6ul with DSA in multi chip addressing mode

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20190703155518.GE18473@lunn.ch>
Date:   Wed, 3 Jul 2019 17:55:18 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Benjamin Beckmeyer <beb@...-engel.de>
Cc:     netdev@...r.kernel.org
Subject: Re: i.mx6ul with DSA in multi chip addressing mode - no MDIO access

On Wed, Jul 03, 2019 at 03:10:34PM +0200, Benjamin Beckmeyer wrote:
> Hey folks,
> 
> I'm having a problem with a custom i.mx6ul board. When DSA is loaded I can't 
> get access to the switch via MDIO, but the DSA is working properly. I set up
> a bridge for testing and the switch is in forwarding mode and i can ping the 
> board. But the MDIO access isn't working at address 2 for the switch. When I 
> delete the DSA from the devicetree and start the board up, I can access the 
> switch via MDIO.
> 
> With DSA up and running:
> 
> mii -i 2 0 0x9800
> mii -i 2 1
> phyid:2, reg:0x01 -> 0x4000
> mii -i 2 0 0x9803
> mii -i 2 1
> phyid:2, reg:0x01 -> 0x4000
> mii -i 2 1 0x1883
> mii -i 2 1
> phyid:2, reg:0x01 -> 0x4000

Hi Benjamin

I'm guessing that the driver is also using register 0 and 1 at the
same time you are, e.g. to poll the PHYs for link status etc.

There are trace points for MDIO, so you can get the kernel to log all
registers access. That should confirm if i'm right.

	  Andrew