All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maíra Canal" <maira.canal@usp.br>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Jonathan Cameron <jic23@kernel.org>,
	linux-iio <linux-iio@vger.kernel.org>,
	"Bogdan, Dragos" <dragos.bogdan@analog.com>,
	"Hegbeli, Ciprian" <ciprian.hegbeli@analog.com>,
	Cosmin Tanislav <cosmin.tanislav@analog.com>,
	Puranjay Mohan <puranjay12@gmail.com>
Subject: Re: GSoC Proposal 2022
Date: Tue, 12 Apr 2022 09:24:38 -0300	[thread overview]
Message-ID: <YlVvhoBNap4Yip3O@fedora> (raw)
In-Reply-To: <59c37b67bbc4a24336e5220a7ad4f242d854fb76.camel@gmail.com>

On 04/12, Nuno Sá wrote:
> On Tue, 2022-04-12 at 11:48 +0300, Andy Shevchenko wrote:
> > On Tue, Apr 12, 2022 at 10:43 AM Maíra Canal <maira.canal@usp.br>
> > wrote:
> > > On 04/11, Jonathan Cameron wrote:
> 
> The MAX31875 looks to be a fairly simple one (maybe a good candidate
> for a first driver) but, IMO, having it in IIO boils down to have
> support for continuos mode which would mean triggered buffer support.

I took another look at the Maxim Integrated catalog and end up finding
the MAX31889 Temperature Sensor.

I guess this sensor has an interesting challenge level with the need to
implement FIFO and interrupts support. 

Have you guys some thoughts on this one?

> 
> The ADPD188BI looks to be more complicated which might be too much for
> GSOC? Not sure here... That said, it looks like you can have some fun
> with it.

P.S.: Although the ADPD188BI looks like a lot of fun, I was afraid to don't be
able to deliver a full driver at the end of 12-weeks. So, I'm trying to find
a safer choice.

Maíra Canal

> 
> - Nuno Sá
> 

  reply	other threads:[~2022-04-12 12:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  3:23 GSoC Proposal 2022 Maíra Canal
2022-04-10 17:28 ` Jonathan Cameron
2022-04-10 22:37   ` Maíra Canal
2022-04-11  8:52     ` Jonathan Cameron
2022-04-11  9:23       ` Jonathan Cameron
2022-04-11 13:13       ` Maíra Canal
2022-04-12  8:48         ` Andy Shevchenko
2022-04-12 12:06           ` Nuno Sá
2022-04-12 12:24             ` Maíra Canal [this message]
2022-04-12 14:23               ` Nuno Sá
2022-04-12 16:19                 ` Jonathan Cameron
2022-04-12 19:24                   ` Maíra Canal
2022-04-13  6:52                     ` Nuno Sá
2022-04-12 15:59             ` Jonathan Cameron
2022-04-13  6:28               ` Nuno Sá
2022-04-11 10:08   ` Andy Shevchenko

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=YlVvhoBNap4Yip3O@fedora \
    --to=maira.canal@usp.br \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=ciprian.hegbeli@analog.com \
    --cc=cosmin.tanislav@analog.com \
    --cc=dragos.bogdan@analog.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --cc=puranjay12@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 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.