mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Thompson <daniel@riscstar.com>
Cc: Alexander Duyck <alexanderduyck@fb.com>,
	Alex Elder <elder@riscstar.com>,
	hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: pcs: xpcs: select operating mode for 10G-baseR capable PCS
Date: Tue, 20 Oct 2026 02:08:21 +0200	[thread overview]
Message-ID: <2bd6d040-6e28-4323-b02e-c8cf11635b24@lunn.ch> (raw)
In-Reply-To: <atZJBaHU2QQGwcnG@aspen.lan>

> I have spotted a very obvious flaw in my reasoning above: the special
> case logic for FBNIC that suppresses the initial XPCS reset.
> Unfortunately the version history doesn't mention what bad thing we
> can avoid by suppressing the reset (perhaps a reset can clobber values
> such as PCS_TYPE_SEL that are injected by the firmware).

At a guess, they want to avoid disconnecting the BMC, which is sharing
the link. The firmware is probably doing an initial configuration of
the PCS, so that the BMC gets link, before the host boots. A reset
would upset that.

But just a guess.

We need a better story for links shared by BMCs. phylink should be
told, so it can tell the PCS to be extra special careful not to upset
the settings if they are already good. It can also reuse some of the
WoL code to not actually down the PCS, PHY, SFP etc when
phylink_stop() is called etc. But so far nobody has stepped up to do
that.

	Andrew

  reply	other threads:[~2026-10-20  0:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 22:30 [PATCH net-next 0/2] net: pcs: xpcs: fix operating mode selection Alex Elder
2026-10-14 22:30 ` [PATCH net-next 1/2] net: pcs: xpcs: re-order xpcs_pre_config() to update after the reset Alex Elder
2026-10-18 13:00   ` netdev-bot+sashiko
2026-10-20  8:38     ` Daniel Thompson
2026-10-14 22:30 ` [PATCH net-next 2/2] net: pcs: xpcs: select operating mode for 10G-baseR capable PCS Alex Elder
2026-10-15 21:09   ` Andrew Lunn
2026-10-16 14:30     ` Daniel Thompson
2026-10-18 15:48       ` Andrew Lunn
2026-10-19 16:44         ` Daniel Thompson
2026-10-20  0:08           ` Andrew Lunn [this message]
2026-10-18 13:00   ` netdev-bot+sashiko
2026-10-15 20:34 ` [PATCH net-next 0/2] net: pcs: xpcs: fix operating mode selection Andrew Lunn

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=2bd6d040-6e28-4323-b02e-c8cf11635b24@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=alexanderduyck@fb.com \
    --cc=daniel@riscstar.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=elder@riscstar.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®