Linux IIO development
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Maíra Canal" <maira.canal@usp.br>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.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: Wed, 13 Apr 2022 08:52:01 +0200	[thread overview]
Message-ID: <e6c272a05b9073718a6b869533537bf163bf4ad5.camel@gmail.com> (raw)
In-Reply-To: <YlXR0d7waKW9xncd@fedora>

On Tue, 2022-04-12 at 16:24 -0300, Maíra Canal wrote:
> On 04/12, Jonathan Cameron wrote:
> > On Tue, 12 Apr 2022 16:23:55 +0200
> > Nuno Sá <noname.nuno@gmail.com> wrote:
> > 
> > > On Tue, 2022-04-12 at 09:24 -0300, Maíra Canal wrote:
> > > > 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?
> > Hmm. The fifo is interesting, but I'm somewhat doubtful that it's
> > actually
> > much use when connected to a linux system.  The sampling rate is
> > 1Hz.
> > At that rate even in busy systems or low power situations, there is
> > little reason not to just poll the device.
> > 
> > You 'could' wire up a PWM or similar to the gpio and have it
> > operate
> > like a 'self clocked' device but with sampling rates so low it's a
> > fairly
> > contrived situation.
> > 
> > Temperature sensors in general are often a bad fit for IIO
> > precisely because
> > they are mostly designed for monitoring type purposes which HWMON
> > covers.
> > The exceptions are high speed or high accuracy devices or weird
> > ones like
> > infrared thermometers.
> 
> Okay, so temperature sensors are not a good choice for an IIO
> project.
> 
> Just another two suggestions: AD5124/AD5144/AD5144A potenciometer and
> AD7294-2
> ADC. Any of those are a good idea for IIO?
> 

Both options look promising being AD7294-2, at first glance, more
complex. The latter actually looks like it fits iio/addac category of
devices. I just briefly looked at the datasheets so I cannot really say
for sure if buffering makese sense for these (for adc/dac often it
does).

- Nuno Sá
> > 


  reply	other threads:[~2022-04-13  6: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
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á [this message]
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=e6c272a05b9073718a6b869533537bf163bf4ad5.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --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=maira.canal@usp.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox