All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Mike Looijmans <mike.looijmans@topic.nl>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-hwmon@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jdelvare@suse.com,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH v2] hwmon: Add LTC2471/LTC2473 driver
Date: Thu, 29 Jun 2017 06:41:11 -0700	[thread overview]
Message-ID: <1fdc6985-f6ca-2751-3503-a6de67b517e0@roeck-us.net> (raw)
In-Reply-To: <7c14b49d-5878-b665-fd4f-0582058cedd5@topic.nl>

On 06/29/2017 06:22 AM, Mike Looijmans wrote:
> On 29-06-17 14:30, Lars-Peter Clausen wrote:
>> On 06/29/2017 02:13 PM, Mike Looijmans wrote:
>>> The LTC2741 and LTC2473 are single voltage monitoring chips. The LTC2473
>>> is similar to the LTC2471 but outputs a signed differential value.
>>>
>>> Datasheet:
>>>    http://cds.linear.com/docs/en/datasheet/24713fb.pdf
>>
>> This looks more like a general purpose ADC rather than a specialized voltage
>> monitoring chip. In my opinion this driver would be better suited for the
>> IIO framework. But before you start working on that lets try to hear what
>> others think about this.
> 
> I'm neutral on it, it's being used as a hardware monitor on the board I have, but it's indeed a generic I2C ADC.
> 
> Do you have a suggestion for a similar device (simple I2C ADC) that I could base the IIO driver on? I've come across the AD799x which seems a good starting point.
> 

ltc2485, ltc2497 ? No idea how close they are.

Guenter

  reply	other threads:[~2017-06-29 13:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 10:45 [PATCH] hwmon: Add LTC2471/LTC2473 driver Mike Looijmans
2017-06-29 11:18 ` Frans Klaver
2017-06-29 11:30   ` Mike Looijmans
2017-06-29 11:38     ` Frans Klaver
2017-06-29 12:08       ` Mike Looijmans
2017-06-29 13:37   ` Guenter Roeck
2017-06-29 12:13 ` [PATCH v2] " Mike Looijmans
2017-06-29 12:30   ` Lars-Peter Clausen
2017-06-29 13:22     ` Mike Looijmans
2017-06-29 13:41       ` Guenter Roeck [this message]
2017-06-29 13:40     ` Guenter Roeck
2017-06-29 14:11       ` Mike Looijmans
2017-06-29 15:08         ` Guenter Roeck
2017-06-29 15:30         ` Lars-Peter Clausen
2017-06-29 13:34 ` [PATCH] " Guenter Roeck
2017-07-01  9:58   ` Jonathan Cameron

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=1fdc6985-f6ca-2751-3503-a6de67b517e0@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.looijmans@topic.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.