From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
zdevai@gmail.com
Subject: Re: [PATCH] staging:iio:proof of concept in kernel interface.
Date: Mon, 17 Oct 2011 15:05:31 +0100 [thread overview]
Message-ID: <4E9C362B.3080502@cam.ac.uk> (raw)
In-Reply-To: <20111017135508.GE27266@opensource.wolfsonmicro.com>
On 10/17/11 14:55, Mark Brown wrote:
> On Mon, Oct 17, 2011 at 02:03:53PM +0100, Jonathan Cameron wrote:
>> On 10/17/11 13:48, Mark Brown wrote:
>
>>>> 0...4
>>>> 1...5
>>>> AUXA....AUXD
>>>> TEMP_EXT1...TEMP_EXT5 (all of which are just normal adc channels that some
>>>> designer decided would be used only for connecting analog temperature sensors.)
>
>>> None of those look at all unreasonable
>
>> Fair enough though the temp one is at least stupid, but why should
>> we match them?
>
> So that the engineer sitting there with the schematics can figure out
> how to tell software about the board hookup with minimal pain.
Fine, I'll code it up and we'll see what works for the cases we have.
>
>> Ok, so we could add to every channel a magic matching field called
>> datasheet_name? To my mind its silly overhead, but if there is a
>> consensus on it then fine. Note however that any remotely general
>> purpose userspace will not read these values even if we make
>> them available.
>
> That depends, if the userspace is really general purpose I'd expect it'd
> be exposing this information to let the user point and click (or
> whatever) through the channels. Otherwise they'll be scratching their
> heads wondering what channel 0 on this particular system actually is.
>
True enough, though ultimately it would be nice if it is easy enough to
work out that they can put sticky labels on the wires... Lets call these
channel_label and keep them optional for now. If nothing else I don't
really fancy retrofitting our 50+ existing drivers with them all in
one go.
Jonathan
next prev parent reply other threads:[~2011-10-17 14:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 11:43 [PATCH RFC] IIO: Proof of concept in kernel interface Jonathan Cameron
2011-10-11 11:43 ` [PATCH] staging:iio:proof " Jonathan Cameron
2011-10-13 14:32 ` Mark Brown
2011-10-13 14:46 ` Jonathan Cameron
2011-10-13 20:44 ` Mark Brown
2011-10-14 15:59 ` Jonathan Cameron
2011-10-14 19:33 ` Mark Brown
2011-10-16 18:45 ` Linus Walleij
2011-10-17 9:39 ` Mark Brown
2011-10-17 9:44 ` Jonathan Cameron
2011-10-17 9:43 ` Jonathan Cameron
2011-10-17 10:19 ` Mark Brown
2011-10-17 10:32 ` Jonathan Cameron
2011-10-17 10:46 ` Mark Brown
2011-10-17 11:13 ` Jonathan Cameron
2011-10-17 11:18 ` Mark Brown
2011-10-17 11:32 ` Jonathan Cameron
2011-10-17 12:08 ` Mark Brown
2011-10-17 12:31 ` Jonathan Cameron
2011-10-17 12:48 ` Mark Brown
2011-10-17 13:03 ` Jonathan Cameron
2011-10-17 13:55 ` Mark Brown
2011-10-17 14:05 ` Jonathan Cameron [this message]
2011-10-17 13:55 ` Linus Walleij
2011-10-17 14:01 ` Jonathan Cameron
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=4E9C362B.3080502@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zdevai@gmail.com \
/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).