* ionic: hwmon in the NIC driver or as an auxiliary driver?
@ 2026-10-09 3:51 Nikhil P. Rao
0 siblings, 0 replies; only message in thread
From: Nikhil P. Rao @ 2026-10-09 3:51 UTC (permalink / raw)
To: Guenter Roeck
Cc: linux-hwmon, netdev, Brett Creeley, Arun Kumar Prakash,
Eric Joyner, nikhil.rao
Hi Guenter,
Before posting a series, I'd like to check how you want hardware
monitoring for a NIC structured.
We see two options:
(a) Register hwmon from the ionic driver itself, as other NIC drivers
do today.
(b) Have ionic create an "hwmon" auxiliary device, with a new driver
in drivers/hwmon/ binding to it.
The hwmon guidance in the Sashiko review prompts suggests an auxiliary
driver in drivers/hwmon/ for chips whose main function isn't hardware
monitoring, which would be (b). Which would you prefer?
If (b), should the drivers/hwmon patch go through your tree, or would
you Ack it so the whole series can go through net-next?
Thanks,
Nikhil
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-10-09 3:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-09 3:51 ionic: hwmon in the NIC driver or as an auxiliary driver? Nikhil P. Rao
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox