mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Fabio Baltieri <fabio.baltieri@gmail.com>,
	Johan Dahlin <jdahlin@gmail.com>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] hwmon: (nct6683) Enable pwm control on ASRock B850 Steel Legend WiFi
Date: Thu, 17 Sep 2026 13:03:35 -0700	[thread overview]
Message-ID: <94109b63-7886-4bd3-8879-5c6740c69964@roeck-us.net> (raw)
In-Reply-To: <aqwk3JIvOLD3rB_T@google.com>

On 9/17/26 10:35, Fabio Baltieri wrote:
> Hi,
> 
> On Tue, Aug 25, 2026 at 11:25:46AM +0200, Johan Dahlin wrote:
>> Fan control has been measured on this board: with a fan in manual mode the
>> applied pwm value tracks what is written, and the fan responds
>> proportionally from 337 RPM at pwm 60 to 933 RPM at pwm 255.
>>
>> Allow pwm writes on this board.
>>
>> Signed-off-by: Johan Dahlin <jdahlin@gmail.com>
>> ---
>>   drivers/hwmon/nct6683.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/hwmon/nct6683.c b/drivers/hwmon/nct6683.c
>> index 6825e6c3af34..df28055b1a1c 100644
>> --- a/drivers/hwmon/nct6683.c
>> +++ b/drivers/hwmon/nct6683.c
>> @@ -972,7 +972,8 @@ SENSOR_TEMPLATE(pwm, "pwm%d", S_IRUGO, show_pwm, store_pwm, 0);
>>    */
>>   static bool nct6683_has_fan_control(struct nct6683_data *data)
>>   {
>> -	return data->customer_id == NCT6683_CUSTOMER_ID_MITAC;
>> +	return data->customer_id == NCT6683_CUSTOMER_ID_MITAC ||
>> +	       data->customer_id == NCT6683_CUSTOMER_ID_ASROCK8;
>>   }
>>   
>>   /*
> 
> Thanks for the patches, I tried this on an ASRock BC-250, also NCT6686D,
> and it works fine there as well. The board id is
> NCT6683_CUSTOMER_ID_AMD and all it needed was:
> 
> -              data->customer_id == NCT6683_CUSTOMER_ID_ASROCK8;
> +              data->customer_id == NCT6683_CUSTOMER_ID_ASROCK8 ||
> +              data->customer_id == NCT6683_CUSTOMER_ID_AMD;
> 
> Maybe you can add that as well once you send the v2 of this? (and a
> Tested-by: Fabio Baltieri <fabio.baltieri@gmail.com>). Or I'm happy to
> send a followup myself once this gets merged, whatever you prefer.
> 
> Either way I feel like this list is going to grow, maybe a
> 
> switch (data->customer_id) {
> ...
> 
> would work out better long term here.
> 
Or maybe add a boolean have_fan_control or similar to struct nct6683_data,
populate it in the probe function, and just use it.

Thanks,
Guenter


      reply	other threads:[~2026-09-17 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  9:25 [PATCH 0/5] hwmon: (nct6683) Fan control for " Johan Dahlin
2026-08-25  9:25 ` [PATCH 1/5] hwmon: (nct6683) Retry pwm writes until they take effect Johan Dahlin
2026-08-25  9:25 ` [PATCH 2/5] hwmon: (nct6683) Add customer ID for ASRock B850 Steel Legend WiFi Johan Dahlin
2026-08-25  9:25 ` [PATCH 3/5] hwmon: (nct6683) Add pwm[1-8]_enable Johan Dahlin
2026-08-25  9:25 ` [PATCH 4/5] hwmon: (nct6683) Restore fan control mode on driver removal Johan Dahlin
2026-08-25  9:25 ` [PATCH 5/5] hwmon: (nct6683) Enable pwm control on ASRock B850 Steel Legend WiFi Johan Dahlin
2026-09-17 17:35   ` Fabio Baltieri
2026-09-17 20:03     ` Guenter Roeck [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=94109b63-7886-4bd3-8879-5c6740c69964@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=fabio.baltieri@gmail.com \
    --cc=jdahlin@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®