From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
Mike Looijmans <mike.looijmans@topic.nl>,
linux-iio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Michael.Hennerich@analog.com,
knaack.h@gmx.de, pmeerw@pmeerw.net
Subject: Re: [PATCH v2] iio:ad5064: Add support for ltc2633 and similar devices
Date: Sun, 14 May 2017 16:18:17 +0100 [thread overview]
Message-ID: <9da01a92-e8bd-cadb-86bc-b2ef2e477bf8@kernel.org> (raw)
In-Reply-To: <c29df10c-8715-363e-02f4-e3231b65ad51@metafoo.de>
On 10/05/17 10:12, Lars-Peter Clausen wrote:
> On 05/08/2017 09:26 AM, Mike Looijmans wrote:
>> The Linear Technology LTC2631, LTC2633 and LTC2635 are very similar
>> to the AD5064 device, in particular the LTC2627.
>>
>> This patch adds support for those devices. Only the LTC2633 has been
>> tested, which is the 2-channel variant. The LTC2631 is the 1-channel,
>> and the LTC2635 the 4-channel version. The actual DAC resolution depends
>> on the exact chip type and can be 12, 10 or 8 bits, using the upper bits
>> so this has no effect on the register map. The internal reference is set
>> to 2.5V on "L" versions, and it's 4.096V for "H" versions.
>>
>> Datasheets:
>> LTC2631: http://www.linear.com/docs/26553
>> LTC2633: http://www.linear.com/docs/39529
>> LTC2635: http://www.linear.com/docs/28754
>>
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>
> Reviewed-by: Lars-Peter Clausen <lars@metafoo.de>
>
> Thanks for reworking the patch.
>
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.
Thanks,
Jonathan
prev parent reply other threads:[~2017-05-14 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 9:44 [PATCH] iio:ad5064: Add support for ltc2633 and similar devices Mike Looijmans
2017-04-27 5:52 ` Jonathan Cameron
2017-04-27 9:16 ` Lars-Peter Clausen
2017-04-27 17:09 ` Mike Looijmans
2017-05-08 7:26 ` [PATCH v2] " Mike Looijmans
2017-05-10 9:12 ` Lars-Peter Clausen
2017-05-14 15:18 ` 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=9da01a92-e8bd-cadb-86bc-b2ef2e477bf8@kernel.org \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=pmeerw@pmeerw.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