Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Siddharth Menon <simeddon@gmail.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: GSoC IIO project: Siddharth Menon
Date: Sat, 22 Feb 2025 15:11:43 +0000	[thread overview]
Message-ID: <20250222151143.7ca7f718@jic23-huawei> (raw)
In-Reply-To: <CAGd6pzNTB5f++sbirWxnD1Tq_rjTkBDVmSrpFYsMisEasAq4Rg@mail.gmail.com>

On Fri, 21 Feb 2025 21:23:35 +0530
Siddharth Menon <simeddon@gmail.com> wrote:

> subject: Permission to work on dt bindings for staging drivers
> 
> I am interested in applying for GSoC under the IIO driver project.
> 
> I have a couple of patches that have been merged into the kernel,
> and am now exploring DT bindings.
> 
> Currently, I am working on Coding Task 1 (sending cleanup patches).
> While running checkpatch.pl, I noticed warnings about undocumented
> DT-compatible strings.
> Would creating the appropriate binding count as a cleanup patch or were
> they left undocumented intentionally because they are staging drivers?

There has been a long term reluctance to pin down DT bindings for
drivers that are known to not be in a suitable state for long term
maintenance etc.  So I'd skip adding bindings for these. Also
they tend to be far from what I'd call cleanup patches!

Some of those staging/iio drivers will probably get dropped at somepoint
so before doing any more major work on them, please send an email to
check they are still of interest!

Your email motivated me to take a quick look.
The accel/adis16240 is now marked obsolete at 
https://www.analog.com/en/products/adis16240.html
I'll send out a patch shortly to suggest we drop that one as unlikely
anyone will expend work on a part that is getting hard to get.

The other drivers all cover at least 1 supported part.

Jonathan

> 
> Regards,
> Siddharth Menon
> 


  reply	other threads:[~2025-02-22 15:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 15:53 GSoC IIO project: Siddharth Menon Siddharth Menon
2025-02-22 15:11 ` Jonathan Cameron [this message]
2025-02-28  5:37   ` Siddharth Menon
2025-03-03  4:48     ` Marcelo Schmitt
2025-03-05 13:36       ` Siddharth Menon
2025-03-05 14:07         ` Marcelo Schmitt
2025-03-05 14:57       ` Jonathan Cameron
2025-03-06 18:55         ` Siddharth Menon
2025-03-09 16:11           ` Jonathan Cameron
2025-04-07 22:45             ` Siddharth Menon
2025-04-08  3:57               ` Marcelo Schmitt
2025-04-08  7:40                 ` Siddharth Menon

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=20250222151143.7ca7f718@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=simeddon@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