public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 v4 0/1] hwmon: (sht3x) read out sensor serial number
Date: Wed, 31 Jan 2024 12:15:11 +0100	[thread overview]
Message-ID: <20240131111512.25321-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.

A "sht3x" debugfs directory is created when loading the driver.
Within this parent directory, another directory is created for each
sensor instantiation which contains the serial number.
The sensor-specific directories are managed by devres, such that
they are cleaned up upon deinstantation or if hwmon registration fails.
The top-level directory is removed when the driver is unloaded.

Changelog
=========

v3 -> v4:
	- Remove debugfs entry with devm_add_action_or_reset()

v2 -> v3:
	- Remove #ifdef for debugfs
	- Add debugfs cleanup
	- Do not expose serial number if read fails

v1 -> v2:
	- Change from sysfs to debugfs
	- Add documentation improvements

Stefan Gloor (1):
  hwmon: (sht3x) read out sensor serial number

 Documentation/hwmon/sht3x.rst | 11 ++++++
 drivers/hwmon/sht3x.c         | 66 ++++++++++++++++++++++++++++++++++-
 2 files changed, 76 insertions(+), 1 deletion(-)

-- 
2.41.0


             reply	other threads:[~2024-01-31 11:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 11:15 Stefan Gloor [this message]
2024-01-31 11:15 ` [PATCH v4 1/1] hwmon: (sht3x) read out sensor serial number Stefan Gloor
2024-01-31 13: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=20240131111512.25321-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