From: Vladimir Oltean <olteanv@gmail.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Daniel Machon <daniel.machon@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>, Felix Fietkau <nbd@nbd.name>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Jakub Kicinski <kuba@kernel.org>, John Crispin <john@phrozen.org>,
Jose Abreu <Jose.Abreu@synopsys.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Marcin Wojtas <mw@semihalf.com>,
Mark Lee <Mark-MC.Lee@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Paolo Abeni <pabeni@redhat.com>,
Sean Wang <sean.wang@mediatek.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Taras Chornyi <taras.chornyi@plvision.eu>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
UNGLinuxDriver@microchip.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [PATCH RFC] Providing a helper for PCS inband negotiation
Date: Mon, 15 May 2023 22:56:16 +0300 [thread overview]
Message-ID: <20230515195616.uwg62f7hw47mktfu@skbuf> (raw)
In-Reply-To: <ZGIkGmyL8yL1q1zp@shell.armlinux.org.uk>
Hello,
On Mon, May 15, 2023 at 01:22:50PM +0100, Russell King (Oracle) wrote:
> 1. Should 10GBASE-KR be included in the SGMII et.al. case in the code?
> Any other interface modes that should be there? Obviously,
> PHYLINK_PCS_NEG_NONE is not correct for 10GBASE-KR since it does use
> inband AN. Does it make sense for the user to disable inband AN for
> 10GBASE-KR? If so, maybe it should be under the 1000base-X case.
What physical process (reference to IEEE 802.3 clause is fine) would be
controlled by the phylink_pcs_neg_mode() function for the so-called
10GBASE-KR phy-mode?
next prev parent reply other threads:[~2023-05-15 19:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 12:22 [PATCH RFC] Providing a helper for PCS inband negotiation Russell King (Oracle)
2023-05-15 13:58 ` Andrew Lunn
2023-05-15 15:34 ` Russell King (Oracle)
2023-05-15 15:44 ` Russell King (Oracle)
2023-05-15 19:56 ` Vladimir Oltean [this message]
2023-05-15 21:45 ` Russell King (Oracle)
2023-05-15 22:08 ` Vladimir Oltean
2023-05-15 23:36 ` Russell King (Oracle)
2023-05-16 9:00 ` Vladimir Oltean
2023-05-16 11:49 ` Russell King (Oracle)
2023-05-16 14:15 ` Vladimir Oltean
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=20230515195616.uwg62f7hw47mktfu@skbuf \
--to=olteanv@gmail.com \
--cc=Jose.Abreu@synopsys.com \
--cc=Mark-MC.Lee@mediatek.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=ioana.ciornei@nxp.com \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mw@semihalf.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.com \
--cc=taras.chornyi@plvision.eu \
--cc=thomas.petazzoni@bootlin.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