Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ethan Jimmy" <duhxu0@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] hwmon: (acer-aspire14-ec) Add driver for Acer Aspire 14 52MT and 52M fan
Date: Sat, 10 Oct 2026 04:21:26 +0000	[thread overview]
Message-ID: <sashiko-outbox-166253@kernel.org> (raw)
In-Reply-To: <20261010041313.34153-1-duhxu0@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] hwmon: architectural violation of HID layering rules
--

commit fa48d917bd5280e6dd85fd709932750623717a15
Author: Ethan Jimmy <duhxu0@gmail.com>
Subject: hwmon: (acer-aspire14-ec) Add driver for Acer Aspire 14 52MT and 52M fan

This commit introduces a new hardware monitoring driver for the Acer Aspire 14
AI series (A14-52M and A14-52MT). It reads the fan speed via an I2C HID
embedded controller that also serves as the system keyboard.

diff --git a/drivers/hwmon/acer-aspire14-ec.c b/drivers/hwmon/acer-aspire14-ec.c
new file mode 100644
index 0000000000000..9d100f2a0b807
--- /dev/null
+++ b/drivers/hwmon/acer-aspire14-ec.c

[ ... ]

> +static const struct hid_device_id acer_aspire14_id_table[] = {
> +	{ HID_I2C_DEVICE(ACER_ASPIRE14_VID, ACER_ASPIRE14_PID) },
> +	{ }
> +};
> +
> +static struct hid_driver acer_aspire14_driver = {
> +	.name = "acer-aspire14-ec",
> +	.id_table = acer_aspire14_id_table,
> +	.probe = acer_aspire14_probe,

[Severity: Medium]
Does this driver architecture bypass the HID subsystem layering?

The hardware monitoring subsystem guidelines state that if the main
functionality of a chip is not hardware monitoring (such as a system
keyboard EC), its primary driver should reside in its respective subsystem
directory (e.g., drivers/hid/). The hardware monitoring functionality should
then be implemented as an auxiliary device driver residing in drivers/hwmon/.

By defining and registering a complete hid_driver directly within the hwmon
directory, this bypasses the HID subsystem maintainer review for the transport
layer integration. Could the primary hid_driver be placed in drivers/hid/ to
spawn an auxiliary_device, allowing an auxiliary_driver in drivers/hwmon/ to
bind to the fan monitoring feature?

> +	.remove = acer_aspire14_remove,
> +	.reset_resume = acer_aspire14_reset_resume,
> +};
> +
> +static int __init acer_aspire14_init(void)

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261010041313.34153-1-duhxu0@gmail.com?part=1

      reply	other threads:[~2026-10-10  4:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10  4:13 [PATCH] hwmon: (acer-aspire14-ec) Add driver for Acer Aspire 14 52MT and 52M fan Ethan Jimmy
2026-10-10  4:21 ` sashiko-bot [this message]

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=sashiko-outbox-166253@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=duhxu0@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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