From: Thomas Wismer <thomas@wismer.xyz>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
Kory Maincent <kory.maincent@bootlin.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>
Cc: Thomas Wismer <thomas@wismer.xyz>,
Thomas Wismer <thomas.wismer@scs.ch>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next v3 0/2] net: pse-pd: Add TPS23881B support
Date: Wed, 29 Oct 2025 22:23:08 +0100 [thread overview]
Message-ID: <20251029212312.108749-1-thomas@wismer.xyz> (raw)
This patch series aims at adding support for the TI TPS23881B PoE
PSE controller.
Changes in v3:
- Incorporate review comments from Oleksij
- Link to v2: https://lore.kernel.org/netdev/20251022220519.11252-2-thomas@wismer.xyz/
Changes in v2:
- Repost after net-next reopened
- Split off bugfix commit
- Improve commit messages
- Link to v1: https://lore.kernel.org/netdev/20251004180351.118779-2-thomas@wismer.xyz/
Thomas Wismer (2):
net: pse-pd: tps23881: Add support for TPS23881B
dt-bindings: pse-pd: ti,tps23881: Add TPS23881B
.../bindings/net/pse-pd/ti,tps23881.yaml | 1 +
drivers/net/pse-pd/tps23881.c | 69 +++++++++++++++----
2 files changed, 55 insertions(+), 15 deletions(-)
--
2.43.0
next reply other threads:[~2025-10-29 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 21:23 Thomas Wismer [this message]
2025-10-29 21:23 ` [PATCH net-next v3 1/2] net: pse-pd: tps23881: Add support for TPS23881B Thomas Wismer
2025-10-30 9:40 ` Kory Maincent
2025-10-30 10:22 ` Oleksij Rempel
2025-10-29 21:23 ` [PATCH net-next v3 2/2] dt-bindings: pse-pd: ti,tps23881: Add TPS23881B Thomas Wismer
2025-10-30 9:29 ` Kory Maincent
2025-11-01 1:00 ` [PATCH net-next v3 0/2] net: pse-pd: Add TPS23881B support patchwork-bot+netdevbpf
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=20251029212312.108749-1-thomas@wismer.xyz \
--to=thomas@wismer.xyz \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=thomas.wismer@scs.ch \
/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