From: Guenter Roeck <linux@roeck-us.net>
To: Wayne Ho <wayneho219@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Pascal Sachs <pascal.sachs@sensirion.com>,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (sht3x) Fix alarm attribute names in documentation
Date: Thu, 12 Nov 2026 10:05:22 -0800 [thread overview]
Message-ID: <05bae14d-5530-45ab-a14c-d068f7587724@roeck-us.net> (raw)
In-Reply-To: <20261112-sht3x-doc-alarm-attr-v1-1-91676362d133@gmail.com>
On 11/11/26 22:01, Wayne Ho wrote:
> The description of the periodic measure mode says that "the alert
> attribute" is set when a reading exceeds the configured limits. The
> driver has no such attribute, and never had one. The alarm state has
> been exposed through temp1_alarm and humidity1_alarm since the driver
> was added, which is also what the sysfs interface table further down in
> the same document lists.
>
> Refer to the actual attribute names.
>
> Fixes: 7c84f7f80d6f ("hwmon: add support for Sensirion SHT3x sensors")
> Signed-off-by: Wayne Ho <wayneho219@gmail.com>
> ---
> Documentation/hwmon/sht3x.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/hwmon/sht3x.rst b/Documentation/hwmon/sht3x.rst
> index 4f67671eb0c..3c022c058be 100644
> --- a/Documentation/hwmon/sht3x.rst
> +++ b/Documentation/hwmon/sht3x.rst
> @@ -78,11 +78,11 @@ The allowed update_interval in milliseconds are as follows:
>
> In the periodic measure mode, the sensor automatically triggers a measurement
> with the configured update interval on the chip. When a temperature or humidity
> -reading exceeds the configured limits, the alert attribute is set to 1 and
> -the alert pin on the sensor is set to high.
> +reading exceeds the configured limits, the temp1_alarm or humidity1_alarm
> +attribute is set to 1 and the alert pin on the sensor is set to high.
Just replacing "alert" with "alarm", as below, would do the trick as well.
If you resend with those changes, I'll apply it, but for the future please
refrain from sending cosmetic patches. If you want to contribute, please
consider fixing real bugs.
Thanks,
Guenter
> When the temperature and humidity readings move back between the hysteresis
> -values, the alert bit is set to 0 and the alert pin on the sensor is set to
> -low.
> +values, the alarm attribute is set to 0 and the alert pin on the sensor is set
> +to low.
>
> The serial number exposed to debugfs allows for unique identification of the
> sensors. For sts32, sts33 and sht33, the manufacturer provides calibration
>
> ---
> base-commit: 44c8ceae2dd3ae536c5f4f956cedb24c157aac23
> change-id: 20261112-sht3x-doc-alarm-attr-118ddfebc6ae
>
> Best regards,
> --
> Wayne Ho <wayneho219@gmail.com>
next prev parent reply other threads:[~2026-11-12 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 6:01 Wayne Ho
2026-11-12 18:05 ` Guenter Roeck [this message]
2026-11-13 0:43 ` 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=05bae14d-5530-45ab-a14c-d068f7587724@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pascal.sachs@sensirion.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=wayneho219@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®