From: Florian Fainelli <f.fainelli@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Richard Cochran <richardcochran@gmail.com>,
Kevin Hilman <khilman@baylibre.com>,
Heiko Stuebner <heiko@sntech.de>
Cc: bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH net-next] net: phy: switch drivers to use dynamic feature detection
Date: Sun, 7 Apr 2019 13:31:37 -0700 [thread overview]
Message-ID: <53f5d96e-4594-7a32-792d-4837479da7f2@gmail.com> (raw)
In-Reply-To: <0cc96fab-e102-c0d1-ade0-90e3e06dc9f1@gmail.com>
On 4/7/2019 2:57 AM, Heiner Kallweit wrote:
> Recently genphy_read_abilities() has been added that dynamically detects
> clause 22 PHY abilities. I *think* this detection should work with all
> supported PHY's, at least for the ones with basic features sets, i.e.
> PHY_BASIC_FEATURES and PHY_GBIT_FEATURES. So let's remove setting these
> features explicitly and rely on phylib feature detection.
>
> I don't have access to most of these PHY's, therefore I'd appreciate
> regression testing.
The nice thing about the features is that we can right away tell which
PHY entries are Fast Ethernet/Gigabit etc... so if you remove that
assignment, we would need at least a standardized comment allowing us to
quickly grep for that information.
--
Florian
next prev parent reply other threads:[~2019-04-07 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 9:57 [PATCH net-next] net: phy: switch drivers to use dynamic feature detection Heiner Kallweit
2019-04-07 20:31 ` Florian Fainelli [this message]
2019-04-07 20:48 ` Heiner Kallweit
2019-04-07 22:13 ` Andrew Lunn
2019-04-08 17:45 ` Heiner Kallweit
2019-04-08 18:12 ` Andrew Lunn
2019-04-08 18:45 ` Heiner Kallweit
2019-04-08 2:38 ` Richard Cochran
2019-04-09 20:59 ` David Miller
2019-04-10 19:31 ` Heiner Kallweit
2019-04-10 19:33 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53f5d96e-4594-7a32-792d-4837479da7f2@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=heiko@sntech.de \
--cc=hkallweit1@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).