From: Jonathan Cameron <jic23@kernel.org>
To: ShiHao <i.shihao.999@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
marcelo.schmitt@analog.com, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, mazziesaccount@gmail.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
till@linux.com
Subject: Re: Request for guidence
Date: Sun, 22 Mar 2026 12:06:21 +0000 [thread overview]
Message-ID: <20260322120621.5eaf627f@jic23-huawei> (raw)
In-Reply-To: <abD572bpEU8f9Uil@fedora>
On Wed, 11 Mar 2026 10:43:19 +0530
ShiHao <i.shihao.999@gmail.com> wrote:
> On Tue, Mar 10, 2026 at 12:28:29PM +0200, Andy Shevchenko wrote:
> > We are already in the relevant mailing list, so if ShiHao wants to work on IIO
> > drivers, welcome!
>
> > With Best Regards,
> > Andy Shevchenko
> >
> >
> Hello,
> First of all, thank you all for your time and responses. After
> learning that the IIO driver development project will not be
> part of this year’s GSoC, I shifted my preparation toward the
> DT binding project idea since it aligns with my driver development
> goals and Thank you, Andy, for letting me know that I can still
> work on driver development. However, I still have no clear idea
> how to get started.
>
> My main questions are: how should I begin, which sensors currently
> need drivers, and what happens if someone else is already working
> on a particular driver? Would it still be possible for me to
> contribute?
For devices that need drivers, best bet is normally to see if a commonly
available part with a break out board (to avoid having to design and build
circuit boards!) is not yet supported. Works best when it's something
you are interested in.
Other alternatives that can be good places to learn are around modernising or
debugging existing drivers. Either get the hardware if possible, or
another useful skill to learn is how to emulate that hardware.
Personally I tend to do that on QEMU but that's because I'm more familiar
with that than other alternatives.
Other than mechanical changes where we can easily see there is no functional
affect I wouldn't advise trying to work on drivers unless you have good
emulation to test against. Doing emulation for a device that isn't currently
supported is also unwise because it's hard to know if it is right without
getting that thoroughly reviewed. As such it tends to be most helpful when
you can assume the existing code works, test the emulation using that and
then test your refactors and updates.
Jonathan
>
> Therefore, I would really appreciate some guidance on how to get
> started. Any help would be greatly appreciated. Thank you all again.
>
> With sincere regards,
> Shi Hao
>
>
prev parent reply other threads:[~2026-03-22 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 5:18 Request for guidence ShiHao
2026-03-07 21:43 ` Marcelo Schmitt
2026-03-09 4:14 ` ShiHao
2026-03-09 22:55 ` Till Kamppeter
2026-03-10 10:28 ` Andy Shevchenko
2026-03-10 14:37 ` Request for guidance ChenLei
2026-03-10 16:54 ` Andy Shevchenko
2026-03-11 5:13 ` Request for guidence ShiHao
2026-03-22 12:06 ` 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=20260322120621.5eaf627f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=i.shihao.999@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=mazziesaccount@gmail.com \
--cc=nuno.sa@analog.com \
--cc=till@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.