From: "Nikhil P. Rao" <nikhil.rao@amd.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: <linux-hwmon@vger.kernel.org>, <netdev@vger.kernel.org>,
Brett Creeley <brett.creeley@amd.com>,
Arun Kumar Prakash <ArunKumar.Prakash@amd.com>,
"Eric Joyner" <eric.joyner@amd.com>, <nikhil.rao@amd.com>
Subject: ionic: hwmon in the NIC driver or as an auxiliary driver?
Date: Fri, 9 Oct 2026 03:51:09 +0000 [thread overview]
Message-ID: <20261009035120.3098398-1-nikhil.rao@amd.com> (raw)
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
reply other threads:[~2026-10-09 3:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261009035120.3098398-1-nikhil.rao@amd.com \
--to=nikhil.rao@amd.com \
--cc=ArunKumar.Prakash@amd.com \
--cc=brett.creeley@amd.com \
--cc=eric.joyner@amd.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.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