linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Borja <kuurtb@gmail.com>
To: Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	 Jonathan Corbet <corbet@lwn.net>,
	 Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	 Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>
Cc: linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	 Kurt Borja <kuurtb@gmail.com>
Subject: [PATCH v4 0/4] hwmon: (sht21) Add devicetree support
Date: Mon, 08 Sep 2025 10:54:48 -0500	[thread overview]
Message-ID: <20250908-sht2x-v4-0-bc15f68af7de@gmail.com> (raw)

Hi all,

The sht21 driver actually supports all i2c sht2x chips so add support
for those names and additionally add DT support.

Tested for sht20 and verified against the datasheet for sht25.

Thanks!

Signed-off-by: Kurt Borja <kuurtb@gmail.com>
---
Changes in v4:
- Reorder dt-bindings patch
- Drop stable tags
- Link to v3: https://lore.kernel.org/r/20250907-sht2x-v3-0-bf846bd1534b@gmail.com

Changes in v3:
- Add MODULE_DEVICE_TABLE() (I forgot, sorry for the noise!)
- Link to v2: https://lore.kernel.org/r/20250907-sht2x-v2-0-1c7dc90abf8e@gmail.com

Changes in v2:
- Add a documentation cleanup patch
- Add entry for each chip instead of sht2x placeholder
- Update Kconfig too
- Link to v1: https://lore.kernel.org/r/20250907-sht2x-v1-0-fd56843b1b43@gmail.com

---
Kurt Borja (4):
      hwmon: (sht21) Documentation cleanup
      hwmon: (sht21) Add support for SHT20, SHT25 chips
      dt-bindings: trivial-devices: Add sht2x sensors
      hwmon: (sht21) Add devicetree support

 .../devicetree/bindings/trivial-devices.yaml       |  3 +++
 Documentation/hwmon/sht21.rst                      | 26 +++++++++++++---------
 drivers/hwmon/Kconfig                              |  4 ++--
 drivers/hwmon/sht21.c                              | 15 ++++++++++++-
 4 files changed, 34 insertions(+), 14 deletions(-)
---
base-commit: 76eeb9b8de9880ca38696b2fb56ac45ac0a25c6c
change-id: 20250907-sht2x-9b96125a0cf5
-- 
 ~ Kurt


             reply	other threads:[~2025-09-08 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 15:54 Kurt Borja [this message]
2025-09-08 15:54 ` [PATCH v4 1/4] hwmon: (sht21) Documentation cleanup Kurt Borja
2025-09-08 19:20   ` Guenter Roeck
2025-09-08 15:54 ` [PATCH v4 2/4] hwmon: (sht21) Add support for SHT20, SHT25 chips Kurt Borja
2025-09-08 19:21   ` Guenter Roeck
2025-09-08 15:54 ` [PATCH v4 3/4] dt-bindings: trivial-devices: Add sht2x sensors Kurt Borja
2025-09-09  7:02   ` Krzysztof Kozlowski
2025-09-09 12:25   ` Guenter Roeck
2025-09-09 17:18     ` Kurt Borja
2025-09-08 15:54 ` [PATCH v4 4/4] hwmon: (sht21) Add devicetree support Kurt Borja
2025-09-09 12:26   ` 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=20250908-sht2x-v4-0-bc15f68af7de@gmail.com \
    --to=kuurtb@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).