From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>
Subject: Re: [IIO] Cleanup userspace
Date: Sat, 04 Sep 2010 18:26:16 +0100 [thread overview]
Message-ID: <4C828138.6060406@cam.ac.uk> (raw)
In-Reply-To: <4C77D52A.6090606@cam.ac.uk>
On 08/27/10 16:09, Jonathan Cameron wrote:
> ...
>>>
>>> Agreed. These ought to be in there and will be needed
>>>
>>>> To be compatible with future extensions we could have:
>>>> |- /sys/bus/iio/ii0/buffer0/scan_elements/
>>>> |- accel_x:en (0 or 1)
>>>> |- accel_x:type (i.e. s14/16, see *)
>>>> |- accel_x:index
>>>>
>>>
>>>> * s14/16 means signed 14 bits, stored in 16 bits, right aligned. If
>>>> it's left aligned we can just modify the scale attribute and give the
>>>> 16 bit interpretation in <channel>:raw.
>>> That is quite a neat way of doing it though I'm not sure 'type' is the
>>> ideal name. My immediate thought is that type would be 'acceleration'!
>>> We definitely want this on list. We'd also want to drop the precision
>>> attribute as that will just confuse things.
>>
>> I'm open for any other name.
> Lets see if anyone else has a suggestion...
actually, having thought about it a bit more (and as no one else chipped in)
I'm happy to go with type as you suggested. It's a nice clear interface.
It should be obvious to anyone looking at the value that it is about the size
of the element (even if they don't immediately follow the /16 bit).
Perhaps we should run this past lkml to see if anyone has a suggestion?
Manuel, it's your idea so you get to write the email ;)
prev parent reply other threads:[~2010-09-04 17:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 8:57 [IIO] Cleanup userspace Manuel Stahl
[not found] ` <4C77AC01.3090204@cam.ac.uk>
[not found] ` <4C77B68B.4060805@iis.fraunhofer.de>
2010-08-27 14:24 ` Jonathan Cameron
2010-08-27 14:31 ` Manuel Stahl
2010-08-27 15:09 ` Jonathan Cameron
2010-08-30 10:55 ` [PATCH 1/2] staging:iio rename ring attributes Manuel Stahl
2010-08-30 12:28 ` Jonathan Cameron
2010-08-30 10:55 ` [PATCH 2/2] staging:iio move scan_elements into ring buffer Manuel Stahl
2010-08-30 12:58 ` Jonathan Cameron
2010-08-30 13:37 ` Manuel Stahl
2010-08-30 14:09 ` Jonathan Cameron
[not found] ` <4C7BD886.3060109@cam.ac.uk>
2010-08-30 16:31 ` Manuel Stahl
2010-08-30 16:48 ` Jonathan Cameron
2010-08-30 14:03 ` [PATCH 1/3] staging:iio update documentation Manuel Stahl
2010-08-30 14:23 ` Jonathan Cameron
2010-08-30 14:24 ` Manuel Stahl
2010-08-30 14:49 ` Jonathan Cameron
2010-08-30 14:03 ` [PATCH 2/3] staging:iio sync drivers with current ABI Manuel Stahl
2010-08-30 14:44 ` Jonathan Cameron
2010-08-30 15:00 ` Manuel Stahl
2010-08-30 15:42 ` Jonathan Cameron
2010-08-30 15:48 ` Manuel Stahl
2010-08-30 16:07 ` Jonathan Cameron
2010-08-30 16:28 ` Manuel Stahl
2010-08-30 16:43 ` Jonathan Cameron
2010-08-30 14:03 ` [PATCH 3/3] staging:iio:hmc5843 change ABI to comply with documentation Manuel Stahl
2010-08-30 14:58 ` Jonathan Cameron
2010-08-31 12:16 ` Datta, Shubhrajyoti
2010-09-04 17:26 ` 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=4C828138.6060406@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
--cc=uclinux-dist-devel@blackfin.uclinux.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