From: <markus.stockhausen@gmx.de>
To: "'Guenter Roeck'" <linux@roeck-us.net>, <sashiko@lists.linux.dev>
Cc: <linux-hwmon@vger.kernel.org>
Subject: AW: AW: [PATCH 2/2] hwmon: (lm75) Support active-high alert polarity
Date: Fri, 1 May 2026 21:00:17 +0200 [thread overview]
Message-ID: <004101dcd99c$c0ade660$4209b320$@gmx.de> (raw)
In-Reply-To: <8776fc88-364e-4ac5-b30c-8a706716d8ff@roeck-us.net>
> Von: Guenter Roeck <groeck7@gmail.com> Im Auftrag von Guenter Roeck
> Gesendet: Freitag, 1. Mai 2026 19:38
> Betreff: Re: AW: [PATCH 2/2] hwmon: (lm75) Support active-high alert polarity
> ...
>>> - [High] The active-high alert polarity configuration is completely ignored by the hardware because it is not added to the register update mask.
>>> - [High] LM75_ALERT_POLARITY_HIGH_16_BIT targets the wrong byte of the configuration register.
>>> - [High] Changing the AS6200 default from active-high to active-low breaks devicetree backward compatibility.
>>
>> unsure if answering to you helps both of us further. So my 2 cents only shortly:
>>
>> - Issue 1: Existing definitions for tmp1XX devices do not not obey "clr_mask is superset of set_mask".
>
> I think you are saying that this is a pre-existing bug and that set_mask is effectively
> ignored. Is that a reason not to fix the problem ?
> ...
> 2) Fix lm75_write_config() to add set_mask to clr_mask to ensure
> that the bits which are supposed to be set are actually set.
I did not expect a bug in the current driver and was baffled by the bots
response. From your feedback that qualifies a "Fixes" tag. Am I right to
assume that 6da24a2 ("hwmon: (lm75) Hide register size differences in
regmap access functions") is the commit to blame?
Markus
next prev parent reply other threads:[~2026-05-01 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 12:05 [PATCH 0/2] Support active-high alert polarity for LM75 Markus Stockhausen
2026-05-01 12:05 ` [PATCH 1/2] dt-bindings: hwmon: lm75: Add lm75,alert-polarity-active-high property Markus Stockhausen
2026-05-01 12:24 ` sashiko-bot
2026-05-02 17:37 ` AW: " markus.stockhausen
2026-05-02 18:10 ` Guenter Roeck
2026-05-03 18:02 ` Conor Dooley
2026-05-01 12:05 ` [PATCH 2/2] hwmon: (lm75) Support active-high alert polarity Markus Stockhausen
2026-05-01 12:45 ` sashiko-bot
2026-05-01 14:06 ` AW: " markus.stockhausen
2026-05-01 17:37 ` Guenter Roeck
2026-05-01 19:00 ` markus.stockhausen [this message]
2026-05-01 19:24 ` AW: " Guenter Roeck
2026-05-01 20:14 ` Guenter Roeck
2026-05-01 20:42 ` AW: " markus.stockhausen
2026-05-01 21:19 ` Guenter Roeck
2026-05-01 17:05 ` Conor Dooley
2026-05-01 19:32 ` Guenter Roeck
2026-05-03 18:00 ` Conor Dooley
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='004101dcd99c$c0ade660$4209b320$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sashiko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.