From: Stefan Gloor <code@stefan-gloor.ch>
To: jdelvare@suse.com, linux@roeck-us.net, corbet@lwn.net,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Stefan Gloor <code@stefan-gloor.ch>
Subject: [PATCH v2 0/2] hwmon: sht3x: improve docs, read serial number
Date: Mon, 4 Dec 2023 17:50:02 +0100 [thread overview]
Message-ID: <20231204165004.8491-1-code@stefan-gloor.ch> (raw)
The temperature/humidity sensors of the STS3x/SHT3x family are
calibrated and factory-programmed with a unique serial number.
For some sensors, this serial number can be used to obtain a calibration
certificate via an API provided by the manufacturer (Sensirion).
Expose the serial number via debugfs.
Documentation is missing information about the sts3x support, add it.
Changelog
=========
v1 -> v2:
- Change from sysfs to debugfs
- Add documentation improvements
In v1 I stated that the serial number readout was not
documented for the whole SHT3x/STS3x series. I found that there is a
separate document for SHT3x documenting this feature.
For STS3x, the manufacturer confirmed with me that both families work
identically. Therefore, it is not needed to introduce more IDs than "sts3x"
and "sht3x", as they don't have different functionality.
Stefan Gloor (2):
hwmon: sht3x: add sts3x support
hwmon: sht3x: read out sensor serial number
Documentation/hwmon/sht3x.rst | 40 ++++++++++++++++++++-----
drivers/hwmon/sht3x.c | 55 +++++++++++++++++++++++++++++++++++
2 files changed, 87 insertions(+), 8 deletions(-)
--
2.41.0
next reply other threads:[~2023-12-04 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 16:50 Stefan Gloor [this message]
2023-12-04 16:50 ` [PATCH v2 1/2] hwmon: sht3x: add sts3x support Stefan Gloor
2023-12-11 14:28 ` Guenter Roeck
2023-12-04 16:50 ` [PATCH v2 2/2] hwmon: sht3x: read out sensor serial number Stefan Gloor
2023-12-11 14:31 ` Guenter Roeck
2023-12-11 15:12 ` Stefan Gloor
2023-12-11 15:28 ` 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=20231204165004.8491-1-code@stefan-gloor.ch \
--to=code@stefan-gloor.ch \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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