Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: "Maíra Canal" <maira.canal@usp.br>,
	"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: Tue, 12 Apr 2022 17:19:33 +0100	[thread overview]
Message-ID: <20220412171933.00002d1d@Huawei.com> (raw)
In-Reply-To: <a5f002afb956c96b20c5f5589c34ecaa1bdfadc6.camel@gmail.com>

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.

For the corner cases we have the option of the iio-hwmon bridge driver
but they need to be more obviously not suited to hwmon than this one to
justify their presence in IIO. In general hwmon drivers are simpler, so
if you can get away with it they are a better choice. (also some hwmon
specific features like multiple levels of even of the same type for
warning / critical detection).

Jonathan

> >   
> 
> At first glance, it looks like a better choice when compared with
> MAX31875...
> 
> - Nuno Sá
> >   
> > >   
> 


  reply	other threads:[~2022-04-12 16:19 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 [this message]
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=20220412171933.00002d1d@Huawei.com \
    --to=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox