public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Mugilraj D <dmugil2000@gmail.com>
To: linux-iio <linux-iio@vger.kernel.org>, dragos.bogdan@analog.com
Subject: Re: [RFC] GSoC'21 IIO project: Mugil
Date: Sun, 28 Mar 2021 23:12:39 +0530	[thread overview]
Message-ID: <6e95cf24-9b8b-dd8d-d9cd-c3302d0f7993@gmail.com> (raw)
In-Reply-To: <CAOgtOjMw0UDhOgXU=HY=+kUhVU+Ya_N=Mvxj-cA_gvj-r9HwuQ@mail.gmail.com>



On 26/03/21 3:20 pm, Mugil Raj wrote:
> Hello All,
> 
> [Dragos here you have a quick intro about me if you want,
> https://lore.kernel.org/linux-iio/CAOgtOjMwnwsiXd8rPeGBBTVkZUeabQ5nLtPts2RQDDMc-TDgKA@mail.gmail.com/]
> 
> For GSoC'21 IIO project I would like to choose  AD4695/AD4696 device
> for implementing the driver.
> I referred Analog Device, Inc.'s page that lists all drivers and
> their kernel tree, but there is no existence of any compatible drivers
> for this component.
> 
> About AD4695:
> - 16-Channel, 16-bit 500 kSPS SAR ADC
> - "Recommended for New Designs" phase
> - SPI digital output
> - Datasheet in [1]
> - Product overview in [2]
> 
> Is there any other factor I should consider before choosing a component
> to make a driver for? Do I go ahead with AD4695  in my
> proposal? If yes, are there any recommendations/suggestions you'd like
> to provide for a beginner indulging in making a kernel driver for such a
> component?
> 

I would like to hear from Dragos but seems like he is busy/out of station. 
So, if possible can any other ADI peoples comment on this?

> Thanks,
> Mugil
> 
> [1] https://www.analog.com/media/en/technical-documentation/data-sheets/ad4695_4696.pdf
> [2] https://www.analog.com/en/products/ad4695.html#product-overview
> 

      parent reply	other threads:[~2021-03-28 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26  9:50 [RFC] GSoC'21 IIO project: Mugil Mugil Raj
2021-03-26 11:07 ` Andy Shevchenko
2021-03-27 10:27   ` Mugilraj D
2021-03-26 11:21 ` Jonathan Cameron
2021-03-28 17:42 ` Mugilraj D [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=6e95cf24-9b8b-dd8d-d9cd-c3302d0f7993@gmail.com \
    --to=dmugil2000@gmail.com \
    --cc=dragos.bogdan@analog.com \
    --cc=linux-iio@vger.kernel.org \
    /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