From: Jakub Kicinski <kuba@kernel.org>
To: Elad Nachman <enachman@marvell.com>,
Alok Tiwari <alok.a.tiwari@oracle.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: Wed, 4 Feb 2026 18:27:58 -0800 [thread overview]
Message-ID: <20260204182758.7ba3fd43@kernel.org> (raw)
In-Reply-To: <BL1PR18MB4248EFE8E7D182A5601927E1DB98A@BL1PR18MB4248.namprd18.prod.outlook.com>
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.
--
pw-bot: cr
next prev parent reply other threads:[~2026-02-05 2:27 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 [this message]
2026-02-05 3:16 ` ALOK TIWARI
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=20260204182758.7ba3fd43@kernel.org \
--to=kuba@kernel.org \
--cc=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=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