Thread (5 messages) flat view 5 messages, 5 authors, 2007-05-06

Re: Correct location for ADC/DAC drivers

From: Paul Sokolovsky <hidden>
Date: 2007-05-06 13:20:36
Also in: lkml

Hello Bodo,

Sunday, May 6, 2007, 3:19:59 PM, you wrote:
Robin Getz [off-list ref] wrote:
quoted
On Fri 4 May 2007 16:52, Robert Schwebel pondered:
quoted
On Fri, May 04, 2007 at 02:21:50PM -0400, Robin Getz wrote:
quoted
quoted
quoted
We also have DAC and ADC drivers (up to 16 bits @ 64MS/s, via DMA),
that would be nice to put in the "right" place  - I don't think that
drivers/char is the right place, nor drivers/misc - I also don't think
that /adc is a descriptive place for DAC or mixed signal front ends
(MxFE).
What userspace interface do your drivers have?
Right now, it is a little rudimentary char interface, it needs a little care
to be a bit more general purpose, but it suited needs of what the people who
were using it.
[...]
quoted
I would be interested in having a detailed discussion/random thoughts on
this - what is the best way to expose these types of devices?
Since you ask for random thoughts:
IO of data streams from or to a DAC/ADC is essentially what soundcards do.
I'm wondering if these cards are similar enough to use alsa, and if using
that interface would ease or hinder programming the driver.

        FYI, within handhelds.org kernel project, we also saw the need
for consistent ADC infrastructure, and developed such, based on
classdev concept, on todo to be submitted for review. Our
API/userspace interface however optimized for individual (or
fixed-batch) readings over stream operations, our target usage
are touchscreen, battery, hwmon drivers.




-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help