Linux IIO development
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@antcom.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Greg KH <greg@kroah.com>,
	devel@driverdev.osuosl.org, linux-iio@vger.kernel.org,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>
Subject: Re: Linux driver for MAX517/518/519
Date: Mon, 10 Jan 2011 10:27:19 +0100	[thread overview]
Message-ID: <4D2AD0F7.3020607@antcom.de> (raw)
In-Reply-To: <4D2A373B.6060901@cam.ac.uk>

Hi,

On 01/09/2011 11:31 PM, Jonathan Cameron wrote:
> Pretty clean and nice driver so it was an easy review and should
> be trivial to fix up for a merge.

Thank you for your review - I will include the suggested changes in the
next update.

> I don't think we have previously had a device that
> allows setting multiple inputs together.
> Two options come to mind that will generalize more
> than your _both.
>=20
> output1&2_raw
>=20
> output_raw (suppress the index hence indicating that it sets both).
>=20
> What do you think is the clearest approach?
> Which ever we pick it will also need proper documentation.  Whilst we
> are here, please can you explain your use case?  From a datasheet
> read I think the first channel is latched after the value byte is passe=
d
> then the second only after it's value has been passed over?

It's actually latched after the _complete_ transmission. See datasheet p.=
9:

"The data is transferred to the DAC=E2=80=99s output
latch during the STOP condition following the transmis-
sion. This allows both DACs of the MAX518/MAX519 to
be updated simultaneously."

I will also document this in the driver to make it clearer.

That's also why I'm constructing the I2C transfer in this nonstandard
way. Datasheet doesn't claim to support smbus, so I will change to the
_ic2_ (non _smbus_) interface.

bye,
  Roland

  reply	other threads:[~2011-01-10  9:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D21A2AA.6080006@antcom.de>
     [not found] ` <20110103222834.GA11277@kroah.com>
2011-01-09 14:29   ` Linux driver for MAX517/518/519 Roland Stigge
2011-01-09 22:31     ` Jonathan Cameron
2011-01-10  9:27       ` Roland Stigge [this message]
2011-01-10 11:02         ` Jonathan Cameron
2011-01-11 16:20       ` Roland Stigge
2011-01-11 19:34         ` Jonathan Cameron
2011-01-12  9:44           ` Roland Stigge
2011-01-12 11:20             ` Jonathan Cameron
2011-01-12 15:34               ` Greg KH
2011-01-12 15:44                 ` Jonathan Cameron
2011-01-12 15:43                   ` Greg KH
2011-01-09 18:09   ` Roland Stigge
2011-01-09 20:55     ` J.I. Cameron
2011-01-09 21:05       ` J.I. Cameron
2011-01-09 21:33         ` Roland Stigge

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=4D2AD0F7.3020607@antcom.de \
    --to=stigge@antcom.de \
    --cc=Michael.Hennerich@analog.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=jic23@cam.ac.uk \
    --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