Linux IIO development
 help / color / mirror / Atom feed
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: Siddharth Menon <simeddon@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: GSoC IIO project: Siddharth Menon
Date: Tue, 8 Apr 2025 00:57:03 -0300	[thread overview]
Message-ID: <Z_Sej1XAW__ZBtOb@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <CAGd6pzPDL3FG6rRzBrT72eDdtE+ZMNx4A=WUj2xwA2jvYZBHdQ@mail.gmail.com>

Hi Siddharth,

On 04/08, Siddharth Menon wrote:
> subject: adt7316 driver viable as a gsoc project?
> 
> While working on the patch for the AD9832, I started looking for an available
> AD9832 board as I didn’t want to make too many changes without a testing unit
> on hand.
> 
> While I was browsing, I came across the ADT7316, which doesn’t seem to have
> existing driver support.

There's a driver in staging (drivers/staging/iio/addac/*).

> 
> I know this is last minute with proposal submissions closing tomorrow, but
> I’m considering working on it anyway and wanted to ask if it’d be worth getting
> this board.

While it would be possible to do a GSoC project for ADT7316, I think it wouldn't
be as interesting as developing a new driver, IMO. May be a good one for
contributing as non-gsoc project.

  reply	other threads:[~2025-04-08  3:55 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
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 [this message]
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=Z_Sej1XAW__ZBtOb@debian-BULLSEYE-live-builder-AMD64 \
    --to=marcelo.schmitt1@gmail.com \
    --cc=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