Netdev List
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Roman Kuzmitskii <roman@damex.org>,
	linux-hwmon@vger.kernel.org, netdev@vger.kernel.org
Cc: robert.marko@sartura.hr, luka.perkov@sartura.hr,
	o.rempel@pengutronix.de, kory.maincent@bootlin.com
Subject: Re: [RFC] hwmon: (tps23861) PSE-PD support, extend hwmon driver or move to pse-pd?
Date: Sun, 1 Nov 2026 11:09:42 -0800	[thread overview]
Message-ID: <4d12314e-56db-412c-a558-e4026cd03528@roeck-us.net> (raw)
In-Reply-To: <8cd41211-b026-4158-8e18-454a9ac0bae4@damex.org>

On 11/1/26 10:50, Roman Kuzmitskii wrote:
> On 11/2/26 1:38 AM, Guenter Roeck wrote:
>> On 11/1/26 10:02, Roman Kuzmitskii wrote:
>>> openwrt reviewers asked me to check with you first which way you prefer:
>>> 1. extend hwmon driver with PSE-PD (like it is done right now)
>>> 2. move driver to drivers/net/pse-pd and extend it with PSE-PD
>>> 3. something else
>>>
>> The hardware monitoring "enable" attribute is supposed to enable monitoring,
>> not to enable some power delivery or network (or any other) port. That "port
>> enable" feature using the hwmon ABI was sneaked in, and I am inclined to just
>> remove the upstream driver for severe ABI violation.
>>
>> Guenter
> 
> thanks, does second option look okay with taking tps23861 to drivers/net/pse-pd
> with enable attribute going away?
> 
A perfect solution would be to move the driver to drivers/net/pse-pd (or elsewhere)
and implement the hwmon part as auxiliary driver, but I am also ok with moving it all.
Note that I do not review hwmon drivers outside drivers/hwmon, so if you move the
driver to drivers/net/pse-pd you can abuse the hwmon ABI as much as you want.

Guenter


  reply	other threads:[~2026-11-01 19:09 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 [this message]
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
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=4d12314e-56db-412c-a558-e4026cd03528@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=kory.maincent@bootlin.com \
    --cc=linux-hwmon@vger.kernel.org \
    --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