From: Kory Maincent <kory.maincent@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Guenter Roeck <linux@roeck-us.net>,
Roman Kuzmitskii <roman@damex.org>,
linux-hwmon@vger.kernel.org, netdev@vger.kernel.org,
robert.marko@sartura.hr, luka.perkov@sartura.hr,
o.rempel@pengutronix.de
Subject: Re: [RFC] hwmon: (tps23861) PSE-PD support, extend hwmon driver or move to pse-pd?
Date: Mon, 2 Nov 2026 17:57:06 +0100 [thread overview]
Message-ID: <d7f5a3b3-a3e9-47bf-8f08-5c8feb0c88e7@bootlin.com> (raw)
In-Reply-To: <e422d6e8-3385-43f2-bcd3-1c5060a5b45e@lunn.ch>
On 11/2/26 17:36, Andrew Lunn wrote:
>> I am not using at all the hwmon framework in that development.
>> But as the binding tps23861 is already reserved for hwmon I use a new
>> "tps23861-poe" compatible name binding.
>> To me, I agree to remove the hwmon driver but this will break backward
>> compatibility. I am not a hwmon maintainer so it's not my decision to take.
>
> Is the hwmon code applicable to the tps238XX range of devices?
>
> Can that hwmon code by merged into the PoE driver? Without API
> changes, apart from dropping the API abuse case? The compatible can
> then be transplanted into the PoE driver?
Should we really want to add the hwmon framework in the driver only to
keep the binding name?
We are managing PSEs through ethtool why should we add another user
interface (sysfs)?
Anyway old devicetree won't work, all the PSE PIs should be described
for the PSE to function properly.
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-11-02 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 18:02 [RFC] hwmon: (tps23861) PSE-PD support, extend hwmon driver or move to pse-pd? Roman Kuzmitskii
2026-11-01 18:38 ` Guenter Roeck
2026-11-01 18:50 ` Roman Kuzmitskii
2026-11-01 19:09 ` Guenter Roeck
2026-11-01 19:57 ` Andrew Lunn
2026-11-02 9:49 ` Kory Maincent
2026-11-02 14:54 ` Guenter Roeck
2026-11-02 15:05 ` Kory Maincent
2026-11-02 16:36 ` Andrew Lunn
2026-11-02 16:57 ` Kory Maincent [this message]
2026-11-02 17:33 ` Andrew Lunn
2026-11-02 17:56 ` Kory Maincent
2026-11-01 20:57 ` Robert Marko
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=d7f5a3b3-a3e9-47bf-8f08-5c8feb0c88e7@bootlin.com \
--to=kory.maincent@bootlin.com \
--cc=andrew@lunn.ch \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luka.perkov@sartura.hr \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robert.marko@sartura.hr \
--cc=roman@damex.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