From: Paolo Abeni <pabeni@redhat.com>
To: Daniel Golle <daniel@makrotopia.org>,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <olteanv@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev
Subject: Re: [PATCH net-next v18 0/6] net: dsa: mxl862xx: devlink flash and rescue
Date: Thu, 1 Oct 2026 13:19:01 +0200 [thread overview]
Message-ID: <80fdcb30-be96-49da-8499-2c673e95b75b@redhat.com> (raw)
In-Reply-To: <cover.1790426599.git.daniel@makrotopia.org>
On 9/26/26 15:48, Daniel Golle wrote:
> This series adds "devlink dev flash" and "devlink dev info" support to
> the MaxLinear MxL862xx DSA driver, and makes a switch stuck in its
> MCUboot loader recoverable through the same path.
>
> The switch is flashed over the loader's clause-22 SMDIO download
> interface after the firmware API has rebooted it into MCUboot, and the
> driver reinitialises through a deferred detach and re-probe once the
> new image runs. A switch found in MCUboot at probe registers in a
> reduced rescue mode with firmware version 0.0.0, so the same flash flow
> recovers it; an interrupted download is drained in the background
> first. The deferred re-probe comes from a new driver-core helper,
> device_schedule_reprobe(), which the bound driver calls without a
> module reference; it also replaces the open-coded self-reprobe that
> iwlwifi, hci_h5 and btintel_pcie carry, whose work function frees its
> own module text from under a racing rmmod. fwupd's devlink plugin
> carries the matching quirks [17].
>
> Patch 3 is a driver-core change and patch 4 does not link without it,
> so the series needs a driver-core ack before net-next can take it.
>
> Tested on an MxL86252C switch of the BananaPi R4 Pro 8X: an upgrade
> through fwupd; an unbind and a reboot issued while a flash was running,
> which wait out the transfer and announce the wait; a host crash and a
> power cut mid-transfer, recovered by the background drain and by the
> rescue path on the next boot; and an unbind and a reboot issued while a
> background drain was running, which abort the drain at once and let it
> resume and complete on the rebind or reboot.
>
> Changes since v17 [23]:
Out of sheer curiosity, what represent the number in the square brackets?
More feedback from clashiko. Requests about comments clarification
are IMHO mostly pedant and could be ignored, but AFAICS there are a
few actionable items on patches 3 and 4.
/P
next prev parent reply other threads:[~2026-10-01 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 13:48 Daniel Golle
2026-09-26 13:48 ` [PATCH net-next v18 1/6] net: dsa: add devlink flash_update callback to dsa_switch_ops Daniel Golle
2026-09-26 13:49 ` [PATCH net-next v18 2/6] net: dsa: mxl862xx: add SMDIO clause-22 register access Daniel Golle
2026-09-26 13:49 ` [PATCH net-next v18 3/6] driver core: add device_schedule_reprobe() Daniel Golle
2026-09-26 13:49 ` [PATCH net-next v18 4/6] net: dsa: mxl862xx: add devlink flash_update and info_get Daniel Golle
2026-09-26 13:49 ` [PATCH net-next v18 5/6] net: dsa: mxl862xx: recover switch stuck in MCUboot rescue mode Daniel Golle
2026-09-26 13:50 ` [PATCH net-next v18 6/6] net: dsa: mxl862xx: document devlink flash and info support Daniel Golle
2026-10-01 11:19 ` Paolo Abeni [this message]
2026-10-01 11:49 ` [PATCH net-next v18 0/6] net: dsa: mxl862xx: devlink flash and rescue Daniel Golle
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=80fdcb30-be96-49da-8499-2c673e95b75b@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=driver-core@lists.linux.dev \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
/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®