From: Jonathan Cameron <jic23@kernel.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [RFC PATCH 0/3] Add Sensirion STS30 temperature sensor driver
Date: Thu, 2 Jul 2026 21:15:28 +0100 [thread overview]
Message-ID: <20260702211528.13fbb841@jic23-huawei> (raw)
In-Reply-To: <20260620044010.1082621-1-m32285159@gmail.com>
On Fri, 19 Jun 2026 23:40:04 -0500
Maxwell Doose <m32285159@gmail.com> wrote:
> Hi all,
>
> This patch adds support for the Sensirion STS30 family of temperature
> sensor drivers. It currently supports single-shot non-clock stretched
> readings as well as the entirety of the STS30 family.
>
> I'm sending this as an RFC patch as I unfortunately do not have the
> hardware right now. I have compile-tested it successfully and have done
> a tad bit of testing on QEMU, with it properly registering with no
> errors reported in dmesg. Unfortunately due to the way I had compiled
> the kernel used to test the driver it did not expose the I2C bus to
> userspace properly and I was not able to retrieve values from the
> driver, but I can continue more testing over the next few days and am
> happy to answer any questions anyone may have. Additionally, regarding
> dmesg logs, I neglected to save them while in my testing, but as stated
> previously, I can continue more testing over the next couple of days.
Hi Maxwell,
If sending a driver out prior to getting access to hardware (nothing wrong
with doing that to get early feebdack!) Then mark it RFC and state
at top of cover letter it's because it is untested on real hardware.
Note there are exceptions to this where we will merge kernel code against
emulation but that is normally about large cross industry standards or similar
not small drivers like this one.
Thanks,
Jonathan
>
> Maxwell Doose (3):
> dt-bindings: iio: temperature: Add STS30 devicetree bindings
> iio: temperature: Add STS30 temperature sensor driver
> MAINTAINERS: Add entry for Sensirion STS30 driver
>
> .../iio/temperature/sensirion,sts30.yaml | 49 +++
> MAINTAINERS | 6 +
> drivers/iio/temperature/Kconfig | 11 +
> drivers/iio/temperature/Makefile | 1 +
> drivers/iio/temperature/sts30.c | 321 ++++++++++++++++++
> 5 files changed, 388 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/temperature/sensirion,sts30.yaml
> create mode 100644 drivers/iio/temperature/sts30.c
>
prev parent reply other threads:[~2026-07-02 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 4:40 [RFC PATCH 0/3] Add Sensirion STS30 temperature sensor driver Maxwell Doose
2026-06-20 4:40 ` [RFC PATCH 1/3] dt-bindings: iio: temperature: Add STS30 devicetree bindings Maxwell Doose
2026-06-20 4:52 ` sashiko-bot
2026-06-20 4:40 ` [RFC PATCH 2/3] iio: temperature: Add STS30 temperature sensor driver Maxwell Doose
2026-06-20 4:48 ` sashiko-bot
2026-06-20 7:43 ` Joshua Crofts
2026-06-20 15:15 ` Maxwell Doose
2026-06-20 4:40 ` [RFC PATCH 3/3] MAINTAINERS: Add entry for Sensirion STS30 driver Maxwell Doose
2026-06-20 7:00 ` Joshua Crofts
2026-07-02 20:15 ` Jonathan Cameron [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=20260702211528.13fbb841@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=nuno.sa@analog.com \
--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