From: Lukasz Kulga <lukasz.kulga@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Akshat Chandra" <notmissinge@gmail.com>,
linux-iio@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-kernel@vger.kernel.org,
"Andreas Klinger" <ak@it-klinger.de>
Subject: Re: [PATCH] iio: chemical: add SGP41 driver
Date: Wed, 28 Oct 2026 14:13:14 +0100 [thread overview]
Message-ID: <0d584595-4479-4116-a52b-710e01f20bb3@gmail.com> (raw)
In-Reply-To: <20260904042215.0e21cf29@jic23-huawei>
On 9/4/26 05:22, Jonathan Cameron wrote:
> Whilst it should be a separate patch, the route here to use
> trivial-devices might make sense. Only thing that might be
> worth documenting would be vdd-supply.
>
> I'm would be looking for description in the cover letter of how this
> is different from, and not suited to extension of another drive
> such as the sgp40 (obviously there are more channels on one than
> the other so it isn't trivial!)
>
> Jonathan
Hi Akshat,
I'd like to pick up SGP41 support, taking the approach Jonathan
suggested above and extending the sgp40 driver rather than adding
a separate one. I have SGP40 and SGP41 boards on the way for
testing.
Unless you already have a v2 close to ready, I plan to post a
series in the next few weeks and will Cc you on it. Your review
and testing would be very welcome.
Thanks,
Lukasz Kulga
next prev parent reply other threads:[~2026-10-28 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 15:12 Akshat Chandra
2026-08-31 17:27 ` Andy Shevchenko
2026-08-31 21:21 ` Joshua Crofts
2026-09-04 3:22 ` Jonathan Cameron
2026-10-28 13:13 ` Lukasz Kulga [this message]
2026-10-29 16:19 ` Not More
2026-10-29 16:52 ` Not More
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=0d584595-4479-4116-a52b-710e01f20bb3@gmail.com \
--to=lukasz.kulga@gmail.com \
--cc=ak@it-klinger.de \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=notmissinge@gmail.com \
--cc=nuno.sa@analog.com \
/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
all inboxes | Powered by JetHome®