netdev - Re: [PATCH v2 1/6] mdio_bus: Add generic mdio_find

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]

Date:   Mon, 24 Feb 2020 14:59:13 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Jeremy Linton <jeremy.linton@....com>, netdev@...r.kernel.org
Cc:     opendmb@...il.com, davem@...emloft.net,
        bcm-kernel-feedback-list@...adcom.com,
        linux-kernel@...r.kernel.org, wahrenst@....net, andrew@...n.ch,
        hkallweit1@...il.com
Subject: Re: [PATCH v2 1/6] mdio_bus: Add generic mdio_find_bus()

On 2/24/20 2:53 PM, Jeremy Linton wrote:
> It appears most ethernet drivers follow one of two main strategies
> for mdio bus/phy management. A monolithic model where the net driver
> itself creates, probes and uses the phy, and one where an external
> mdio/phy driver instantiates the mdio bus/phy and the net driver
> only attaches to a known phy. Usually in this latter model the phys
> are discovered via DT relationships or simply phy name/address
> hardcoding.
> 
> This is a shame because modern well behaved mdio buses are self
> describing and can be probed. The mdio layer itself is fully capable
> of this, yet there isn't a clean way for a standalone net driver
> to attach and enumerate the discovered devices. This is because
> outside of of_mdio_find_bus() there isn't a straightforward way
> to acquire the mii_bus pointer.
> 
> So, lets add a mdio_find_bus which can return the mii_bus based
> only on its name.
> 
> Signed-off-by: Jeremy Linton <jeremy.linton@....com>

Acked-by: Florian Fainelli <f.fainelli@...il.com>
-- 
Florian