netdev - Re: [PATCH net-next 4/8] net: ethernet: add the Alpine Ethernet driver

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] [day] [month] [year] [list]

Message-ID: <20171105152227.GY24320@lunn.ch>
Date:   Sun, 5 Nov 2017 16:22:27 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     "BSHARA, Said" <saeedb@...zon.com>
Cc:     "f.fainelli@...il.com" <f.fainelli@...il.com>,
        "Chocron, Jonathan" <jonnyc@...zon.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "antoine.tenart@...e-electrons.com" 
        <antoine.tenart@...e-electrons.com>,
        "arnd@...db.de" <arnd@...db.de>,
        "thomas.petazzoni@...e-electrons.com" 
        <thomas.petazzoni@...e-electrons.com>
Subject: Re: [PATCH net-next 4/8] net: ethernet: add the Alpine Ethernet
 driver

> the problem is that physical MDIO controller actually belongs to one of
> the pcie devices and it's not independent interface, as the registers
> address belongs to that pcie device, also, a reset to that pcie device
> will reset the "shared" mdio controller.

What is the implications of resetting the mdio controller?

It still seems like you should only register one MDIO device with
linux, and then use phy-handle properties to point to the PHYs on the
bus.

       Andrew