From: Guenter Roeck <linux@roeck-us.net>
To: Rong Zhang <i@rong.moe>, Sergio Melas <sergiomelas@gmail.com>
Cc: "Derek J. Clark" <derekjohn.clark@gmail.com>,
Armin Wolf <W_Armin@gmx.de>, Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86 <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v14] Subject: [PATCH v14] hwmon: (yogafan) Extend support to more Lenovo consumer models
Date: Sat, 11 Apr 2026 08:56:28 -0700 [thread overview]
Message-ID: <8f7812ec-3c8a-4673-8222-28ba22796e22@roeck-us.net> (raw)
In-Reply-To: <4c627b63e40d1a3b2923ebe8b42fedde176f35cd.camel@rong.moe>
On 4/11/26 07:31, Rong Zhang wrote:
> Hi Sergio,
>
> On Fri, 2026-04-10 at 22:14 +0200, Sergio Melas wrote:
>> Hi Rong, Hi Guenter,
>>
>> Thank you for the review and for pointing out the overlap with lenovo-wmi-other.
>>
>> 1. WMI Coexistence and Bogus Fans
>> I completely agree that double-reporting is suboptimal. I will
>> implement a check in the probe function using
>> wmi_has_guid(LENOVO_WMI_FAN_GUID). If the WMI interface is present,
>> yogafan will return -ENODEV and yield to your driver. This ensures my
>> driver only covers models where WMI reporting is unavailable.
>>
>
> You may also want to add a module parameter to override the WMI GUID
> check as some devices do not support the fan reporting/tuning interface
> despite having the WMI GUIDs.
>
Please, no new module parameters. If there are devices not supporting this,
add them to an exclude list. Or make sure that only devices supporting
the functionality are instantiated in the first place.
Thanks,
Guenter
next prev parent reply other threads:[~2026-04-11 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 16:43 Sergio Melas
2026-04-05 4:40 ` Guenter Roeck
2026-04-05 7:56 ` Sergio Melas
2026-04-10 17:14 ` Rong Zhang
2026-04-10 20:14 ` Sergio Melas
2026-04-11 14:31 ` Rong Zhang
2026-04-11 15:56 ` Guenter Roeck [this message]
2026-04-11 17:06 ` Rong Zhang
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=8f7812ec-3c8a-4673-8222-28ba22796e22@roeck-us.net \
--to=linux@roeck-us.net \
--cc=W_Armin@gmx.de \
--cc=derekjohn.clark@gmail.com \
--cc=i@rong.moe \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sergiomelas@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
all inboxes | Powered by JetHome®