From: Alison Schofield <amsfield22@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Daniel Baluta <daniel.baluta@intel.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
linux-hwmon@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>
Subject: Re: MCP9808 iio or hwmon
Date: Fri, 24 Jun 2016 17:36:57 -0700 [thread overview]
Message-ID: <20160625003656.GA2726@d830.WORKGROUP> (raw)
In-Reply-To: <20160621234246.GA23912@roeck-us.net>
On Tue, Jun 21, 2016 at 04:42:46PM -0700, Guenter Roeck wrote:
> On Tue, Jun 21, 2016 at 03:26:11PM -0700, Alison Schofield wrote:
> > On Tue, Jun 14, 2016 at 06:27:50AM -0700, Guenter Roeck wrote:
> > > On 06/14/2016 01:22 AM, Daniel Baluta wrote:
> > > >[fixing IIO, hwmon lists emails]
> > > >
> > > >On Tue, Jun 14, 2016 at 11:20 AM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
> > > >>On Tue, Jun 14, 2016 at 1:08 AM, Alison Schofield <amsfield22@gmail.com> wrote:
> > > >>>
> > > >>>I was working on an iio driver for MCP9808 when Jonathan took notice
> > > >>>and suggested we have the iio or hwmon discussion.
> > > >>>
> > > >>>So, where should this sensor driver reside?
> > > >>>
> > > >>>http://ww1.microchip.com/downloads/en/DeviceDoc/25095A.pdf
> > > >>>
> > > >>>It's a digital temp sensor with user programmable registers for
> > > >>>sensing applications. Supports shutdown, low power modes,
> > > >>>specifying of event & critical output boundaries. Can support
> > > >>>8 sensors on a single serial bus. Touted as 'ideal for sophisticated
> > > >>>multi-zone temperature-monitoring applications.'
> > > >>
> > > >>This is debatable, looking to the datasheet this driver could reside
> > > >>in both places.
> > > >>
> > > >>Because this sensor has Industrial utility (e.g freezers, refrigerators) I
> > > >>am inclined to say we should support it in IIO.
> > > >>
> > >
> > > Literally every sensor has that utility.
> > >
> > > Alternatively, you might consider adding its device ID to the jc42 driver.
> > > If you want to be fancy, you could add optional support for resolution
> > > selection to the driver.
> > >
> > > Guenter
> >
> > Hi Guenter,
> > I'm using the mcp9808 with the jc42 driver by instantiating it.
> >
> > I've added the device ID info so that the .detect callback can recognize
> > it, but can't figure out how to test that. When/how does that .detect
> > get called? I am using the Diolan.
> >
> Not sure if it works, but try to load the the jc42 driver using modprobe
> first, and _then_ insert the diolan adapter.
>
> Guenter
Finally got it! I had to add I2C_CLASS_SPD (jc42's class) to Diolan and
then follow the order you suggested.
next prev parent reply other threads:[~2016-06-25 0:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160613220843.GA4235@d830.WORKGROUP>
[not found] ` <CAEnQRZBZcQZRYGbk-6Eh5sN7_D90HTZPPo=uOSSZF2obB5VD+w@mail.gmail.com>
2016-06-14 8:22 ` MCP9808 iio or hwmon Daniel Baluta
2016-06-14 13:27 ` Guenter Roeck
2016-06-21 22:26 ` Alison Schofield
2016-06-21 23:42 ` Guenter Roeck
2016-06-25 0:36 ` Alison Schofield [this message]
2016-06-25 2:11 ` Guenter Roeck
2016-06-27 19:13 ` Alison Schofield
2016-06-27 20:40 ` Guenter Roeck
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=20160625003656.GA2726@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).