From: Simon Horman <horms@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: netdev@vger.kernel.org,
"Conor Dooley" <conor.dooley@microchip.com>,
Valentina.FernandezAlanis@microchip.com,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Daire McNamara" <daire.mcnamara@microchip.com>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Richard Cochran" <richardcochran@gmail.com>,
"Samuel Holland" <samuel.holland@sifive.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
"Sean Anderson" <sean.anderson@linux.dev>,
"Vineeth Karumanchi" <vineeth.karumanchi@amd.com>,
"Abin Joseph" <abin.joseph@amd.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
Ryan.Wanner@microchip.com
Subject: Re: [PATCH net-next v4 00/13] macb usrio/tsu patches
Date: Thu, 19 Mar 2026 19:52:38 +0000 [thread overview]
Message-ID: <20260319195238.GT1753385@horms.kernel.org> (raw)
In-Reply-To: <20260318-surpass-puzzle-f94b46aa8808@spud>
On Wed, Mar 18, 2026 at 04:37:31PM +0000, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Hey folks,
>
> At the very least, it'd be good of the soc vendor folks could check
> their platforms and see if their usrio stuff actually lines up with what
> the driver currently calls "macb_default_usrio". Ours didn't and it was
> a nasty surprise.
>
> Ryan and I figured out that the sama7g5 stuff is not actually using the
> same usrio bits as earlier devices, so there's now more patches in this
> series to split them apart. I've not tested the split or the new
> property due to lack of hardware, but Ryan has.
>
> Marking this stuff net-next, because although they're fixes I don't see
> any particular urgency, and it avoids creating some dependencies between
> cleanup items and the fixes.
>
> Cheers,
> Conor.
>
> v4:
> - deprecate instead of remove existing devicetree property
> - pick up Theo's patches
>
> v3:
> - reorder patches
> - fix smatch issue reported by Simon
> - add patches reworking usrio handling of clken/refclk (and remove the
> issue the llm reported in the process)
> - add a new devicetree property for refclk selection, replacing the
> existing one.
> - drop the dts patch
Hi Conor,
Unfortunately this does not apply cleanly to net-next, which breaks our CI.
Please rebase and repost.
Thanks!
--
pw-bot: changes-requested
prev parent reply other threads:[~2026-03-19 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 16:37 [PATCH net-next v4 00/13] macb usrio/tsu patches Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 01/13] net: macb: rename macb_default_usrio to at91_default_usrio as not all platforms have mii mode control in usrio Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 02/13] net: macb: split USRIO_HAS_CLKEN capability in two Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 03/13] dt-bindings: net: cdns,macb: replace cdns,refclk-ext with cdns,refclk-source Conor Dooley
2026-03-25 21:46 ` Rob Herring (Arm)
2026-03-18 16:37 ` [PATCH net-next v4 04/13] net: macb: rework usrio refclk selection code Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 05/13] net: macb: np4 doesn't need a usrio pointer Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 06/13] net: macb: add mpfs specific usrio configuration Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 07/13] net: macb: warn on pclk use as a tsu_clk fallback Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 08/13] net: macb: clean up tsu clk rate acquisition Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 09/13] dt-bindings: net: macb: add property indicating timer adjust mode Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 10/13] net: macb: timer adjust mode is not supported Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 11/13] net: macb: runtime detect MACB_CAPS_USRIO_DISABLED Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 12/13] net: macb: set MACB_CAPS_USRIO_DISABLED if no usrio config is provided Conor Dooley
2026-03-18 16:37 ` [PATCH net-next v4 13/13] net: macb: drop usrio pointer on EyeQ5 config Conor Dooley
2026-03-19 19:52 ` Simon Horman [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=20260319195238.GT1753385@horms.kernel.org \
--to=horms@kernel.org \
--cc=Ryan.Wanner@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=abin.joseph@amd.com \
--cc=alex@ghiti.fr \
--cc=andrew+netdev@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=sean.anderson@linux.dev \
--cc=theo.lebrun@bootlin.com \
--cc=vineeth.karumanchi@amd.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