From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] iio: core: introduce IIO_CHAN_INFO_SIGNED
Date: Mon, 7 Mar 2016 21:09:32 +0100 [thread overview]
Message-ID: <56DDDFFC.5010100@metafoo.de> (raw)
In-Reply-To: <1457360997-29179-2-git-send-email-ludovic.desroches@atmel.com>
On 03/07/2016 03:29 PM, Ludovic Desroches wrote:
> The same channel can be used to perform a signed or an unsigned
> conversion. Add a new infomask element to be able to select the type of
> conversion wanted: a raw one or a signed raw one.
If this is the difference between offset binary and two's complement then it
makes no sense to expose this at this level. Both are the same number just
in a different representation and converting between them is cheap. A few
magnitudes cheaper than reading the result over sysfs. So, if your device
supports both, just pick one.
For the buffered interface it may make sense to expose this, since the per
sample overhead is a lot lower. But still doing the conversion should be
cheap enough that it does not really matter. Before this is implemented I'd
like to see hard performance numbers that this actually makes a difference.
- Lars
next prev parent reply other threads:[~2016-03-07 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 14:29 [PATCH v2 0/2] iio: add support for signed conversions Ludovic Desroches
2016-03-07 14:29 ` [PATCH v2 1/2] iio: core: introduce IIO_CHAN_INFO_SIGNED Ludovic Desroches
2016-03-07 20:09 ` Lars-Peter Clausen [this message]
2016-03-09 21:04 ` Jonathan Cameron
2016-03-10 13:23 ` Ludovic Desroches
2016-03-07 14:29 ` [PATCH v2 2/2] iio:adc:at91-sama5d2: add support for signed conversion Ludovic Desroches
2016-03-07 20:04 ` 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=56DDDFFC.5010100@metafoo.de \
--to=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).