Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nikita Dubrovskih" <testname142@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v3] hwmon: Add fan monitoring support for HONOR FMI-XX
Date: Sat, 15 Aug 2026 23:33:40 +0000	[thread overview]
Message-ID: <20260815233340.A7F9E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260815232405.2107574-1-testname142@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `SENSORS_HONOR_FMI` Kconfig option is missing a dependency on `ACPI`.
--

--- Patch [1]: [PATCH v3] hwmon: Add fan monitoring support for HONOR FMI-XX ---
commit 049ec54bdd36a31d06eb1fb6aa8b9f74bd2a4a59
Author: Nikita Dubrovskih <testname142@gmail.com>

hwmon: Add fan monitoring support for HONOR FMI-XX
    
The HONOR FMI-XX firmware exposes a serialized \GFNS ACPI method to return
fan speeds. This commit adds a DMI-restricted, read-only hwmon driver to
monitor these speeds, without exposing direct Embedded Controller access.

> diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
> index 2bfbcc033d599..8a11a304d2fd2 100644
> --- a/drivers/hwmon/Kconfig
> +++ b/drivers/hwmon/Kconfig
[ ... ]
> @@ -2785,6 +2785,16 @@ config SENSORS_ASUS_EC
>  	  This driver can also be built as a module. If so, the module
>  	  will be called asus_ec_sensors.
>  
> +config SENSORS_HONOR_FMI
> +	tristate "HONOR FMI-XX fan monitor"
> +	depends on X86

[Severity: Low]
Does this Kconfig entry need a dependency on ACPI?

Without CONFIG_ACPI, ACPICA core functions like acpi_get_handle() are
replaced with static inline stubs that return AE_NOT_CONFIGURED. This means
the driver probe function will unconditionally fail with -ENODEV, and the
driver effectively becomes dead code when configured this way.

> +	help
> +	  If you say yes here, you get support for fan speed monitoring on
> +	  the HONOR FMI-XX laptop through its firmware ACPI method.
[ ... ]

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

  reply	other threads:[~2026-08-15 23:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 19:22 [RFC PATCH] hwmon: Add fan monitoring support for HONOR FMI-XX Nikita Dubrovskih
2026-08-12 19:32 ` sashiko-bot
2026-08-12 22:49 ` Guenter Roeck
2026-08-13  9:14 ` [RFC PATCH v2] " Nikita Dubrovskih
2026-08-13  9:25   ` sashiko-bot
2026-08-14  3:39   ` Guenter Roeck
2026-08-15 23:24   ` [PATCH v3] " Nikita Dubrovskih
2026-08-15 23:33     ` sashiko-bot [this message]
2026-08-15 23:40     ` [PATCH v4] " Nikita Dubrovskih
2026-08-15 23:46       ` sashiko-bot

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=20260815233340.A7F9E1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=testname142@gmail.com \
    /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