[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e676df0e-b736-069c-77c4-ae58ad1e24f8@intel.com>
Date: Sun, 20 Aug 2023 12:20:43 -0700
From: "Greenwalt, Paul" <paul.greenwalt@...el.com>
To: Andrew Lunn <andrew@...n.ch>
CC: <intel-wired-lan@...ts.osuosl.org>, <netdev@...r.kernel.org>,
<pawel.chmielewski@...el.com>, <aelior@...vell.com>, <manishc@...vell.com>
Subject: Re: [PATCH iwl-next v2 2/9] ethtool: Add forced speed to supported
link modes maps
On 8/20/2023 11:54 AM, Andrew Lunn wrote:
> On Sat, Aug 19, 2023 at 02:39:41AM -0700, Paul Greenwalt wrote:
>> The need to map Ethtool forced speeds to Ethtool supported link modes is
>> common among drivers. To support this move the supported link modes maps
>> implementation from the qede driver. This is an efficient solution
>> introduced in commit 1d4e4ecccb11 ("qede: populate supported link modes
>> maps on module init") for qede driver.
>>
>> ethtool_forced_speed_maps_init() should be called during driver init
>> with an array of struct ethtool_forced_speed_map to populate the
>> mapping. The macro ETHTOOL_FORCED_SPEED_MAP is a helper to initialized
>> the struct ethtool_forced_speed_map.
>
> Is there any way to reuse this table:
>
> https://elixir.bootlin.com/linux/latest/source/drivers/net/phy/phy-core.c#L161
>
> Seems silly to have multiple tables if this one can be made to work.
> It is also used a lot more than anything you will add, which has just
> two users so far, so problems with it a likely to be noticed faster.
>
> Andrew
Yes, we'll can look into that.
Powered by blists - more mailing lists