Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Markus Stockhausen <markus.stockhausen@gmx.de>
Cc: linux-hwmon@vger.kernel.org, wsa+renesas@sang-engineering.com,
	alkuor@gmail.com
Subject: Re: [PATCH v3 2/2] hwmon: (lm75) Fix configuration register writes.
Date: Sat, 2 May 2026 11:14:51 -0700	[thread overview]
Message-ID: <dc90fe56-8ffd-4654-a7d5-0d7a57ee0a85@roeck-us.net> (raw)
In-Reply-To: <20260502173207.3567876-3-markus.stockhausen@gmx.de>

On Sat, May 02, 2026 at 07:32:07PM +0200, Markus Stockhausen wrote:
> Sensors configurations are defined by set and clear masks. These
> do not follow a consistent "clear mask is a superset of set mask"
> rule. This relaxed definition breaks lm75_write_config()
> 
> static inline int lm75_write_config(struct lm75_data *data, u16 set_mask,
> 				    u16 clr_mask)
> {
> 	return regmap_update_bits(data->regmap, LM75_REG_CONF,
> 				  clr_mask | LM75_SHUTDOWN, set_mask);
> }
> 
> Basically all bits from set_mask that are not defined in clr_mask are
> dropped. Fix that by enhancing the helper to always combine clr_mask
> and set_mask into the mask bits of regmap_update_bits().
> 
> Fixes: 6da24a25f766 ("hwmon: (lm75) Hide register size differences in regmap access functions")
> Suggested-by: Guenter Roeck <linux@roeck-us.net>
> Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>

Applied, after fixing the Fixes: tag as seen above.

Thanks,
Guenter

  reply	other threads:[~2026-05-02 18:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-02 17:32 [PATCH v3 0/2] hwmon: (lm75) Fix AS6200 and config register handling Markus Stockhausen
2026-05-02 17:32 ` [PATCH v3 1/2] hwmon: (lm75) Fix AS6200 setup and alarm handling Markus Stockhausen
2026-05-02 17:58   ` sashiko-bot
2026-05-02 18:13   ` Guenter Roeck
2026-05-02 17:32 ` [PATCH v3 2/2] hwmon: (lm75) Fix configuration register writes Markus Stockhausen
2026-05-02 18:14   ` Guenter Roeck [this message]
2026-05-02 18:19   ` 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=dc90fe56-8ffd-4654-a7d5-0d7a57ee0a85@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=alkuor@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=markus.stockhausen@gmx.de \
    --cc=wsa+renesas@sang-engineering.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