linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Jonathan Cameron <jic23@kernel.org>,
	Alexandru Ardelean <ardeleanalex@gmail.com>,
	linux-iio <linux-iio@vger.kernel.org>,
	<linux-hwmon@vger.kernel.org>
Subject: Re: IIO Driver for TMP117 Temperature sensor
Date: Mon, 14 Dec 2020 15:11:24 +0000	[thread overview]
Message-ID: <20201214151124.00007c55@Huawei.com> (raw)
In-Reply-To: <CANk7y0gaq9Qb6BBpv4PY8T50Xep19Vh=wEx3hBWG_jDcqGSZJg@mail.gmail.com>

On Mon, 14 Dec 2020 01:40:32 +0530
Puranjay Mohan <puranjay12@gmail.com> wrote:

> On Sun, Dec 13, 2020 at 9:38 PM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > On 12/13/20 7:12 AM, Jonathan Cameron wrote:  
> > > On Wed, 9 Dec 2020 11:48:40 -0800
> > > Guenter Roeck <linux@roeck-us.net> wrote:
> > >  
> > >> On 12/9/20 12:11 AM, Alexandru Ardelean wrote:  
> > >>> On Tue, Dec 8, 2020 at 6:10 PM Puranjay Mohan <puranjay12@gmail.com> wrote:  
> > >>>>
> > >>>> I have this TI's TMP117 sensor with me and I was thinking about writing an
> > >>>> IIO driver for it as a hobby project. Is the IIO subsystem the correct
> > >>>> place for this driver? if yes, can someone help me get started with this,
> > >>>> I haven't written an IIO driver before. I have this sensor and also a
> > >>>> raspberry pi with me for testing.  
> > >>>
> > >>> This could also fit into drivers/hwmon.
> > >>> Looking at the HWMON subsystem there are more TMP drivers there
> > >>> (TMP102/103/108/401/513).
> > >>> The first 3 seem a bit more similar to TMP117 (in terms of register map).
> > >>>  
> > >>
> > >> It would probably be better suited for hwmon (it has limit registers,
> > >> suggesting a common use as hardware monitoring device).  
> > > It is a curious part.  I suspect TI based their design for a medical grade
> > > digital thermometer chip on an existing hwmon part.
> > >
> > > The limit registers are very simple so could be supported by IIO.
> > > This sits somewhere in the middle of high end thermocouple chips which
> > > tend to be in IIO and typically lower accuracy / range hwmon parts.
> > >
> > > It's in the fuzzy borderline region so I doubt anyone would raise strong
> > > objections to which subsystem it was in.  Guenter has fallen on the
> > > hwmon side of things and I'm fine with that.
> > >  
> >
> > On the other side, it turns out that there is already tmp107 support
> > in iio, and tmp107 is pretty much the spi equivalent of the same chip.  
> 
> Yes, you are right, tmp107 is very similar to tmp117, but it is less accurate
> and it doesn't include the OFFSET functionality. Actually, I had seen the
> tmp107 register in IIO and thought that tmp117 should go in IIO,
> hence, I wrote this email.
> 
> So, is it fine if I write the IIO driver for this sensor? Actually,
> this will just
> be a hobby project for me so It doesn't bother me if it goes in hwmon or IIO.

Sounds good to me.

Jonathan


> 
> > So it really depends on the use case. If the user wants to use the iio
> > subsystem, I am fine with it. We just need to remind people that this
> > implies no or only limited hwmon support.
> >
> > [ I really need to spend the time to write a hwmon->iio bridge.
> >   The iio->hwmon bridge is a bit limited - I have not been able to
> >   figure out how to support limit registers (or event values)
> >   and events, and I don't think it is possible. ]
> >
> > Guenter
> >  
> > > Jonathan
> > >  
> > >>  
> > >>> Let's see what others have to add.
> > >>> But, all-in-all whatever driver you end up writing, the easiest method
> > >>> is to copy an existing similar driver and extend it.
> > >>> Sometimes, a part can be added to an existing driver.
> > >>> At a quick scan through existing drivers, it doesn't look like TMP117
> > >>> is similar to existing drivers, so it may require a new driver
> > >>> altogether.  
> > >>
> > >> I don't see an immediate match either, but the tmp102 hwmon driver
> > >> might be a good start.
> > >>
> > >> Guenter
> > >>  
> > >>> I may have missed something though.
> > >>>
> > >>> Thanks
> > >>> Alex
> > >>>  
> > >>>>
> > >>>> --
> > >>>> Thanks and Regards
> > >>>>
> > >>>> Yours Truly,
> > >>>>
> > >>>> Puranjay Mohan  
> > >>  
> > >  
> >  
> 
> 


      reply	other threads:[~2020-12-14 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 16:06 IIO Driver for TMP117 Temperature sensor Puranjay Mohan
2020-12-09  8:11 ` Alexandru Ardelean
2020-12-09 19:48   ` Guenter Roeck
2020-12-13 15:12     ` Jonathan Cameron
2020-12-13 16:08       ` Guenter Roeck
2020-12-13 16:50         ` Jonathan Cameron
2020-12-13 20:14           ` Puranjay Mohan
2020-12-14 15:10             ` Jonathan Cameron
2020-12-13 20:10         ` Puranjay Mohan
2020-12-14 15:11           ` Jonathan Cameron [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=20201214151124.00007c55@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=ardeleanalex@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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;
as well as URLs for NNTP newsgroup(s).