From: Jonathan Cameron <jic23@cam.ac.uk>
To: Roland Stigge <stigge@antcom.de>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: Documentation update for outputs / dac
Date: Thu, 13 Jan 2011 11:03:14 +0000 [thread overview]
Message-ID: <4D2EDBF2.4050800@cam.ac.uk> (raw)
In-Reply-To: <4D2DF5C0.6030405@antcom.de>
On 01/12/11 18:41, Roland Stigge wrote:
> Hi,
>
> On 01/12/2011 01:06 PM, Jonathan Cameron wrote:
>> Any chance at all you can get git-send-email to work for you?
>> Saves me the step of pasting the attachment back into the email
>> every time!
>
> Thanks for the hint. Will test with another patch. :-)
>
>>> +What: /sys/bus/iio/devices/deviceX/outY_raw
>>> +KernelVersion: 2.6.37
>>> +Contact: linux-iio@vger.kernel.org
>>> +Description:
>>> + Raw (unscaled, no bias etc.) output voltage for
>>> + channel Y.
>>
>> Get rid of this bit about named output. I'm not sure it makes sense to allow
>> this and I don't think we currently have an examples in tree.
>
> Do you mean we shouldn't document /sys/bus/iio/devices/deviceX/outY_raw
> (which is quite analogous to inY_raw) but
> /sys/bus/iio/devices/deviceX/outY_scale and
> /sys/bus/iio/devices/deviceX/outY&Z_raw?
>
No, the named bit for inputs is todo with inY_supply_raw etc
rather than the scale and compound versions both of which should
indeed be documented. I just mean remove the bit in the description
of outY_raw which refers to 'names'. Basically get rid of
' In special cases where the channel does not
correspond to externally available output one of the named
versions may be used.' as it doesn't apply to outputs. '
Any internal only output would be a somewhat odd beast.
Thanks,
Jonathan
prev parent reply other threads:[~2011-01-13 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 10:40 [PATCH] iio: Documentation update for outputs / dac Roland Stigge
2011-01-12 12:06 ` Jonathan Cameron
2011-01-12 18:41 ` Roland Stigge
2011-01-13 11:03 ` 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=4D2EDBF2.4050800@cam.ac.uk \
--to=jic23@cam.ac.uk \
--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