public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: Jakub Kicinski <kuba@kernel.org>, Elad Nachman <enachman@marvell.com>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
	"Taras Chornyi [C]" <tchornyi@marvell.com>,
	"Volodymyr Mytnyk [C]" <vmytnyk@marvell.com>,
	Yevhen Orlov <yevhen.orlov@plvision.eu>,
	"Vadym Kochan [C]" <vkochan@marvell.com>,
	Taras Chornyi <taras.chornyi@plvision.eu>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"alok.a.tiwarilinux@gmail.com" <alok.a.tiwarilinux@gmail.com>
Subject: Re: [EXTERNAL] Re: [PATCH net-next] net: marvell: prestera: fix FEC error message for SFP ports
Date: Thu, 5 Feb 2026 08:46:22 +0530	[thread overview]
Message-ID: <e60ec48e-6b4f-4a32-bfc9-c29ee4f30be4@oracle.com> (raw)
In-Reply-To: <20260204182758.7ba3fd43@kernel.org>



On 2/5/2026 7:57 AM, Jakub Kicinski wrote:
> On Wed, 4 Feb 2026 13:13:31 +0000 Elad Nachman wrote:
>>>> I'm pretty sure that the condition here is wrong, not the error message.
>>>>
>>>> AFAIK it doesn't make sense to configure FEC on ethernet/copper ports,
>>>> but for SFP ports, it may be required depending on the transceiver or
>>>> cable used, especially for fiber modules.
>>>>
>>>> I may be wrong though.
>>>>
>>>> This check was introduced with bb5dbf2cc64d ("net: marvell: prestera:
>>>> add firmware v4.0 support"), but that commit does not offer any
>>>> explanation for it in the commit message.
>>>
>>> Elad, could you clarify this? A bit hard to tell whether CR is included
>>> in "SFP" from glancing at the code.
>>
>> Basically, the supported devices have FEC on 10G-BASE-KR and upwards
>> (CR: from 40G-BASE-CR), and for USXGMII SERDES, which drives multiple
>> copper PHYs.
>>
>> Judging based on all of the above,
>> I think it is best to remove this check (plus said error message)
>> altogether and let the firmware return an error if the mode/speed/FEC
>> combination is invalid.
> 
> SG, thanks for explaining
> 
> Alok, pls respin as suggested.

Thanks for the clarification.
I will send a v2 that removes the "port->caps.transceiver == 
PRESTERA_PORT_TCVR_SFP"
check and lets the firmware handle validation.

Thanks,
Alok

      reply	other threads:[~2026-02-05  3:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02  5:28 [PATCH net-next] net: marvell: prestera: fix FEC error message for SFP ports Alok Tiwari
2026-02-02  9:47 ` [EXTERNAL] " Elad Nachman
2026-02-02 10:26 ` Jonas Gorski
2026-02-04  3:15   ` Jakub Kicinski
2026-02-04 13:13     ` [EXTERNAL] " Elad Nachman
2026-02-05  2:27       ` Jakub Kicinski
2026-02-05  3:16         ` ALOK TIWARI [this message]

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=e60ec48e-6b4f-4a32-bfc9-c29ee4f30be4@oracle.com \
    --to=alok.a.tiwari@oracle.com \
    --cc=alok.a.tiwarilinux@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=enachman@marvell.com \
    --cc=jonas.gorski@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=taras.chornyi@plvision.eu \
    --cc=tchornyi@marvell.com \
    --cc=vkochan@marvell.com \
    --cc=vmytnyk@marvell.com \
    --cc=yevhen.orlov@plvision.eu \
    /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