public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Alison Schofield <amsfield22@gmail.com>
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: Mon, 27 Jun 2016 13:40:58 -0700	[thread overview]
Message-ID: <20160627204058.GB5891@roeck-us.net> (raw)
In-Reply-To: <20160627191317.GA4530@d830.WORKGROUP>

On Mon, Jun 27, 2016 at 12:13:19PM -0700, Alison Schofield wrote:

[ ... ]

> > 
> > Great. Can you send a patch for the jc42 driver ?
> > 
> > Thanks,
> > Guenter
> > 
> Guenther,
> 
> I have the patch, but am stumbling on the changelog.
> 
> I hoped to simply state in the changelog that MCP9808 is a jc-42
> compliant sensor, but I don't think it's 100% true, and I'm not
> sure of where it falls short of compliance.
> 
> jc42 currently supports these Microchip sensors:
> MCP9804, MCP9805, MCP98242, MCP98243, MCP98244, MCP9843
> 
> All, with the exception of 9804 (and my 9808), clearly state they
> are jc-42 compliant in their datasheet.
> 
> 9804 is 9808's twin and I've tested with 9808.
> 
> Wondering if the non-compliance has to do with the lack of a capability
> register for 9804 & 9808, which doesn't affect the drivers functioning.
> 

The capabilities register is there, it is just not officially supported.
It does report useful values, though, at least as far as we need it.
The chip does have a resolution register, which doesn't exist in JC-42.

"
hwmon: (jc42) Add support for Microchip MCP9808

MCP9808 is not officially compliant to JC-42, similar to MCP9804,
but its registers are compatible to JC-42.
"

is good enough. If you want to be fancy, add "The sensor resolution
register is not currently supported".

Hope this helps,

Guenter

      reply	other threads:[~2016-06-27 20:41 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
2016-06-25  2:11             ` Guenter Roeck
2016-06-27 19:13               ` Alison Schofield
2016-06-27 20:40                 ` Guenter Roeck [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=20160627204058.GB5891@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=amsfield22@gmail.com \
    --cc=daniel.baluta@intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    /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