Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Olivier Tanoh <olivier.tanoh19@gmail.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Guidance for a first IIO sensor driver contribution
Date: Sat, 22 Aug 2026 00:59:27 +0100	[thread overview]
Message-ID: <20260822005927.55846ad4@jic23-huawei> (raw)
In-Reply-To: <CAM49wQtRt5JWDWZtu4Kc-Lk9miv-Uc0nYocd7JFiTVycXQExkw@mail.gmail.com>

On Thu, 6 Aug 2026 16:14:05 +0200
Olivier Tanoh <olivier.tanoh19@gmail.com> wrote:

> Hi all,

Hi Olivier,

Would have been better to reply to you earlier thread with the additional
context of the replies to that available to anyone seeing this message.

> 
> I'm an embedded Linux engineer looking to contribute my first sensor
> driver to IIO. I'm familiar with the submission process (I've had
> patches merged to staging), and I've studied the structure of existing
> IIO drivers, si7005.c in particular, so I'm comfortable with probe,
> channel definitions and read_raw.
> 
> I have I2C hardware for testing (Raspberry Pi CM4), so I can buy a
> part and validate on real hardware.
> 
> My difficulty is picking a target. Most of the simple
> temperature/humidity sensors I looked at (SHT3x, AHT20, ...) already
> have hwmon drivers, and the recent parts I found in vendor catalogs
> (e.g. MAX30210) are already being submitted upstream.
> 
No particular suggestions from me.

> Two questions:
> 
> Are there sensors the IIO community would like to see supported that
> currently have no driver?
> For a sensor that already has an hwmon driver, is an IIO driver
> considered worthwhile (for buffer/trigger support), or is that
> generally seen as redundant?

Very very rarely does it make sense to move a driver between subsystems
and it is painful to do.

Jonathan

> 
> I'd rather pick something useful than duplicate existing work. Any
> guidance would be appreciated.
> 
> Thanks,
> Olivier Tanoh
> 


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 14:14 Guidance for a first IIO sensor driver contribution Olivier Tanoh
2026-08-21 23:59 ` 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=20260822005927.55846ad4@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olivier.tanoh19@gmail.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