Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jan-Henrik Bruhn" <kernel@jhbruhn.de>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v4] hwmon: (lm63) expose PWM frequency and LUT hysteresis as writable
Date: Sat, 23 May 2026 14:13:21 +0000	[thread overview]
Message-ID: <20260523141322.2F1821F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260523133617.3439102-1-kernel@jhbruhn.de>

> The driver caches the PWM frequency register and the CONFIG_FAN slow-clock
> select bit, but never lets userspace pick a different output frequency.
> Add a pwm1_freq sysfs attribute that selects the closest SCS + PFR
> combination for the requested value in Hz, gated by manual mode like
> set_pwm1(). PFR is clamped to 31 so that 2*PFR fits in the chip's 6-bit
> PWM register (matching the existing scaling assumption in show_pwm1).
> 
> The hardware LUT hysteresis register is shared by all LUT entries, so
> the per-point pwm1_auto_pointN_temp_hyst attributes can't be made RW
> without N-to-1 cross-attribute side effects. Following the max31760
> precedent, expose a single chip-wide pwm1_auto_point_temp_hyst attribute
> holding the hysteresis amount in millidegrees; the per-point attributes
> stay RO and continue to show the resulting absolute trip-down
> temperature for each entry.
> 
> This was tested on a Linksys LGS328MPC switch hardware where the fan
> would not spin with the default PWM Frequency, which is why this change
> is required.
> 
> Signed-off-by: Jan-Henrik Bruhn <kernel@jhbruhn.de>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260523133617.3439102-1-kernel@jhbruhn.de?part=1


  reply	other threads:[~2026-05-23 14:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 13:54 [PATCH] hwmon: (lm63) expose PWM frequency and LUT hysteresis as writable Jan-Henrik Bruhn
2026-05-22 14:28 ` sashiko-bot
2026-05-22 18:47   ` Jan-Henrik Bruhn
2026-05-22 19:34     ` Guenter Roeck
2026-05-22 19:55       ` Jan-Henrik Bruhn
2026-05-22 20:22   ` [PATCH v2] " Jan-Henrik Bruhn
2026-05-22 20:59     ` sashiko-bot
2026-05-23  9:53       ` Jan-Henrik Bruhn
2026-05-23 13:11         ` Guenter Roeck
2026-05-23 13:31           ` Jan-Henrik Bruhn
2026-05-23  9:54       ` [PATCH v3] " Jan-Henrik Bruhn
2026-05-23 10:58         ` sashiko-bot
2026-05-23 13:36           ` [PATCH v4] " Jan-Henrik Bruhn
2026-05-23 14:13             ` sashiko-bot [this message]
2026-05-24 15:26             ` Guenter Roeck

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=20260523141322.2F1821F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=kernel@jhbruhn.de \
    --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