From: Alessandro Rubini <rubini@gnudd.com>
To: jic23@jic23.retrosnub.co.uk
Cc: Carsten.Frank@haw-hamburg.de, linux-iio@vger.kernel.org
Subject: Re: driver interface for usb spectrometer (like OceanOptics)
Date: Tue, 26 Feb 2013 23:48:05 +0100 [thread overview]
Message-ID: <20130226224805.GA5448@mail.gnudd.com> (raw)
In-Reply-To: <512CDF35.8070204@jic23.retrosnub.co.uk>
>> I did look up the IIO API and userspace ABI and I do not see a good fit.
>> However,
>> 1. I may be wrong
> My gut feeling is that there 'ought to be a better option'.
FWIW I tend to agree. IIO is designed for input devices that feature
small sample sizes with individual timestamps and relatively few
configuration parameters. I don't think it's wise to continuosly add
new data types.
There already is a framework that covers every possible input device,
and even output. It's called char driver.
> [...]
> If you handled this in IIO I think you'd have to have a matched chunk
> of userspace code that knows rather a lot about the sensor. Normally
> we'd do a our best to avoid this and as such I suspect that
> these devices really deserve a more specific home.
Exactly. It's great to treat all accelerometers alike, and all
magnetometers alike. That's the kind of device you have in modern
cell phones and supporting all chip vendors with the same interface
is definitely useful. In this case, I see the thing as a custom char
device, where the application knows what it gets.
/alessandro
prev parent reply other threads:[~2013-02-26 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 9:07 driver interface for usb spectrometer (like OceanOptics) Carsten Frank
2013-02-25 10:08 ` Lars-Peter Clausen
2013-02-26 10:36 ` Carsten Frank
2013-02-26 16:13 ` Jonathan Cameron
2013-02-26 22:48 ` Alessandro Rubini [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=20130226224805.GA5448@mail.gnudd.com \
--to=rubini@gnudd.com \
--cc=Carsten.Frank@haw-hamburg.de \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=linux-iio@vger.kernel.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