From: Jonathan Cameron <jic23@cam.ac.uk>
To: Roland Stigge <stigge@antcom.de>
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 11:02:05 +0000 [thread overview]
Message-ID: <4D2AE72D.9050000@cam.ac.uk> (raw)
In-Reply-To: <4D2AD0F7.3020607@antcom.de>
On 01/10/11 09:27, Roland Stigge wrote:
> Hi,
>=20
> 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.
>=20
> Thank you for your review - I will include the suggested changes in t=
he
> next update.
>=20
>> 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.
>>
>> output1&2_raw
>>
>> output_raw (suppress the index hence indicating that it sets both).
>>
>> What do you think is the clearest approach?
>> Which ever we pick it will also need proper documentation. Whilst w=
e
>> 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 pa=
ssed
>> then the second only after it's value has been passed over?
>=20
> It's actually latched after the _complete_ transmission. See datashee=
t p.9:
>=20
> "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."
Ah, I missed that bit of text. I guess the label (DAC0 INPUT LATCH set=
to full scale)
on figure 8b is just confusing then. Now you mention it, there is anoth=
er
label at the stop condition saying the outputs change at the end. I'm n=
ot entirely
sure why they differentiate between DAC input latching and DAC output l=
atching.
Surely people only care about the output. Ah well, the delights of dat=
asheet
interpretation.
Thanks for clearing that up!=20
>=20
> I will also document this in the driver to make it clearer.
Thanks,
>=20
> 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 th=
e
> _ic2_ (non _smbus_) interface.
Good idea. If anyone really needs to get it to work on an smbus only ad=
apter
we can put this back in, but until then readability is more important.
>=20
> bye,
> Roland
>=20
next prev parent reply other threads:[~2011-01-10 11:01 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
2011-01-10 11:02 ` Jonathan Cameron [this message]
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=4D2AE72D.9050000@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=linux-iio@vger.kernel.org \
--cc=stigge@antcom.de \
/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