[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cd79f999-f2f5-8cd4-2d2a-3b6ef9a84583@gmail.com>
Date: Thu, 29 Nov 2018 11:31:23 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Baruch Siach <baruch@...s.co.il>,
Russell King <linux@...linux.org.uk>, netdev@...r.kernel.org
Cc: Maxime Chevallier <maxime.chevallier@...tlin.com>,
Antoine Tenart <antoine.tenart@...tlin.com>
Subject: Re: [RFC PATCH] net: mvpp2: fix detection of 10G SFP modules
On 11/29/2018 4:49 AM, Baruch Siach wrote:
> The mvpp2_phylink_validate() relies on the interface field of
> phylink_link_state to determine valid link modes. However, when called
> from phylink_sfp_module_insert() this field in not initialized. The
> default switch case then excludes 10G link modes. This allows 10G SFP
> modules that are detected correctly to be configured at max rate of
> 2.5G.
>
> Catch the uninitialized PHY mode case, and allow 10G rates.
>
> Cc: Maxime Chevallier <maxime.chevallier@...tlin.com>
> Cc: Antoine Tenart <antoine.tenart@...tlin.com>
> Signed-off-by: Baruch Siach <baruch@...s.co.il>
> ---
> Is that the right fix?
It would be a bit surprising that this is the right fix, you would
expect validate to be called once everything has been parsed
successfully from the SFP, is not that the case here? If not, can you
find out what happens?
--
Florian
Powered by blists - more mailing lists