Devicetree
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Alessandro Zini <alessandro.zini@siemens.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] hwmon: (sht4x): Add support for Sensirion STS4x temperature sensors
Date: Fri, 21 Aug 2026 07:23:25 -0700	[thread overview]
Message-ID: <e081c728-92e5-493b-ac28-9473eade7e82@roeck-us.net> (raw)
In-Reply-To: <20260821091924.18975-3-alessandro.zini@siemens.com>

On Fri, Aug 21, 2026 at 11:19:24AM +0200, Alessandro Zini wrote:
> The Sensirion STS4x series is the temperature-only variant of the
> SHT4x family. It shares the same I2C command set, conversion formulas,
> CRC checksum, and timing with the SHT4x, but only returns temperature
> data (3 bytes: 2 data bytes + 1 CRC byte).
> 
> Add support for the STS4x series by dynamically adjusting the read
> response length, suppressing humidity channel attributes when probed
> as STS4x, and omitting heater sysfs attributes.
> 
> Link: https://sensirion.com/resource/datasheet/sts4x
> Signed-off-by: Alessandro Zini <alessandro.zini@siemens.com>

Applied. I'll send patches fixing the pre-existing issues reported by
Sashiko later today.

Thanks,
Guenter

      parent reply	other threads:[~2026-08-21 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  9:19 [PATCH v2 0/2] hwmon: Add Sensirion STS4x temperature sensor support Alessandro Zini
2026-08-21  9:19 ` [PATCH v2 1/2] dt-bindings: trivial-devices: Add Sensirion STS4x series Alessandro Zini
2026-08-21  9:23   ` sashiko-bot
2026-08-21 14:21   ` Guenter Roeck
2026-08-21  9:19 ` [PATCH v2 2/2] hwmon: (sht4x): Add support for Sensirion STS4x temperature sensors Alessandro Zini
2026-08-21  9:29   ` sashiko-bot
2026-08-21 14:23   ` Guenter Roeck [this message]

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=e081c728-92e5-493b-ac28-9473eade7e82@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=alessandro.zini@siemens.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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