From: Christophe Roullier <christophe.roullier@foss.st.com>
To: 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>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
<linusw@kernel.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Christophe Roullier <christophe.roullier@foss.st.com>
Cc: <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [net-next,PATCH v2 0/5] Some improve for STM32MP2X
Date: Wed, 12 Aug 2026 11:11:17 +0200 [thread overview]
Message-ID: <20260812091122.566439-1-christophe.roullier@foss.st.com> (raw)
Add PHY Regu for MP23/MP25-DK
Increase deassert value for PHY Reset for MP25-EV1
Add support of phy-supply regulator
Remove commit "net: stmmac: manage error case during stmmac_dvr_probe"
from my series to push in net-next networking tree
v2: Add reviewed-by from Linus
Add missing commit to manage phy-supply property
(yaml and glue support)
Christophe Roullier (5):
dt-bindings: net: add phy-supply property for stm32
net: ethernet: stmmac: stm32: support the phy-supply regulator binding
arm64: dts: st: add 3v3 regulator to ethernet on stm32mp235f-dk
arm64: dts: st: add 3v3 regulator to ethernet on stm32mp257f-dk
arm64: dts: st: increase deassert of PHY reset in stm32mp257f-ev1
.../devicetree/bindings/net/stm32-dwmac.yaml | 3 ++
arch/arm64/boot/dts/st/stm32mp235f-dk.dts | 1 +
arch/arm64/boot/dts/st/stm32mp257f-dk.dts | 1 +
arch/arm64/boot/dts/st/stm32mp257f-ev1.dts | 2 +-
.../net/ethernet/stmicro/stmmac/dwmac-stm32.c | 51 ++++++++++++++++++-
5 files changed, 56 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-12 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 9:11 Christophe Roullier [this message]
2026-08-12 9:11 ` [net-next,PATCH v2 1/5] dt-bindings: net: add phy-supply property for stm32 Christophe Roullier
2026-08-12 9:11 ` [net-next,PATCH v2 2/5] net: ethernet: stmmac: stm32: support the phy-supply regulator binding Christophe Roullier
2026-08-12 9:11 ` [net-next,PATCH v2 3/5] arm64: dts: st: add 3v3 regulator to ethernet on stm32mp235f-dk Christophe Roullier
2026-08-12 9:11 ` [net-next,PATCH v2 4/5] arm64: dts: st: add 3v3 regulator to ethernet on stm32mp257f-dk Christophe Roullier
2026-08-12 9:11 ` [net-next,PATCH v2 5/5] arm64: dts: st: increase deassert of PHY reset in stm32mp257f-ev1 Christophe Roullier
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=20260812091122.566439-1-christophe.roullier@foss.st.com \
--to=christophe.roullier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=vladimir.oltean@nxp.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