All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Andre <marc.andre@netline.ch>
To: Lars-Peter Clausen <lars@metafoo.de>, jic23@kernel.org
Cc: knaack.h@gmx.de, pmeerw@pmeerw.net, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: Add support for LTC26xx I2C DAC
Date: Mon, 12 Oct 2015 14:53:51 +0200	[thread overview]
Message-ID: <561BAD5F.7040209@netline.ch> (raw)
In-Reply-To: <561B8AE1.9040408@metafoo.de>

On 12.10.2015 12:26, Lars-Peter Clausen wrote:
> On 10/12/2015 10:52 AM, Marc Andre wrote:
>> This driver adds support for the Linear LTC26x6, LTC26x7 and LTC26x9 I2C
>> DAC chips.
> Those look like they are very much register map compatible to what is
> supported by the AD5064 driver.	It makes sense to add support for them there
> instead of having a separate driver.
I see that the interfaces are similar. Not all features of the ADxxxx 
are supported by the LTC26XX. e.g. it doesn't support the different 
power down modes. It also doesn't support the configuration register.
Other features available to AD which are not available to the LTC are 
LDAC by software, RESET and CLEAR commands. Those commands are currently 
not in use by the driver, but in the future, if those commands are used, 
a separation would have to be done to avoid issues with the LTC.

I first also thought that the address / command location is different as 
the AD5064 sends 4 bytes and "AD5064_ADDR(x)" is "((x) << 20)". By 
further reviewing I see that this only applies to SPI connected devices, 
while I2C connected devices have 3 bytes as LTC26xx.

I am quite open. I have the tendency to suggest a separate ltc26xx 
driver, also because it would allow simpler identification of the driver 
and separate evolution. (Someone would need to know that AD4064 is 
compatible to LTC26xx) I also think large drivers containing many 
separations between similar, but not equal devices are more risky to 
break on changes. No one has all those devices available for test. But I 
am a new contributor to the Kernel, thus I am interested to listen to 
the experts... :-)

Marc

  reply	other threads:[~2015-10-12 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  8:52 [PATCH] iio: Add support for LTC26xx I2C DAC Marc Andre
2015-10-12 10:08 ` Peter Meerwald
2015-10-12 10:26 ` Lars-Peter Clausen
2015-10-12 12:53   ` Marc Andre [this message]
2015-10-12 14:09     ` Lars-Peter Clausen
2015-10-12 17:25       ` Jonathan Cameron
2015-10-13  7:09       ` Marc Andre
2015-10-13  9:46         ` Marc Andre
2015-10-13 10:27         ` Lars-Peter Clausen

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=561BAD5F.7040209@netline.ch \
    --to=marc.andre@netline.ch \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --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 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.