public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: Robin Getz <rgetz@blackfin.uclinux.org>,
	Robert Schwebel <r.schwebel@pengutronix.de>,
	Stefan Roese <ml@stefan-roese.de>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Correct location for ADC/DAC drivers
Date: Sun, 06 May 2007 14:19:59 +0200	[thread overview]
Message-ID: <E1Hkfia-0000cJ-18@be1.lrz> (raw)
In-Reply-To: 8heii-3GM-37@gated-at.bofh.it

Robin Getz <rgetz@blackfin.uclinux.org> wrote:
> On Fri 4 May 2007 16:52, Robert Schwebel pondered:
>> On Fri, May 04, 2007 at 02:21:50PM -0400, Robin Getz wrote:

>> > 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.

[...]

> 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.
-- 
Top 100 things you don't want the sysadmin to say:
76. I have never seen it do *that* before...

Friß, Spammer: BZmk0Kx63V@ld7M4m.7eggert.dyndns.org

       reply	other threads:[~2007-05-06 12:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8fZXU-3EI-11@gated-at.bofh.it>
     [not found] ` <8haHG-6zd-19@gated-at.bofh.it>
     [not found]   ` <8hd2U-1Ca-39@gated-at.bofh.it>
     [not found]     ` <8heii-3GM-37@gated-at.bofh.it>
2007-05-06 12:19       ` Bodo Eggert [this message]
2007-05-06 13:20         ` Correct location for ADC/DAC drivers Paul Sokolovsky
2007-05-06 16:01         ` Robert Schwebel
2007-05-06 19:33           ` Robin Getz
2007-05-06 20:20         ` Guennadi Liakhovetski
2007-05-01 12:35 Stefan Roese
2007-05-01 21:03 ` Guennadi Liakhovetski
2007-05-02 10:25   ` Stefan Roese
2007-05-02 13:35     ` Robert Schwebel
2007-05-02 19:11       ` Russell King
2007-05-04  6:11         ` Stefan Roese
2007-05-04  7:44           ` Russell King
2007-05-04  8:24 ` Robert Schwebel
2007-05-04  8:54   ` Stefan Roese
2007-05-04 18:21     ` Robin Getz
2007-05-04 20:52       ` Robert Schwebel
2007-05-04 22:16         ` Robin Getz

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=E1Hkfia-0000cJ-18@be1.lrz \
    --to=7eggert@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ml@stefan-roese.de \
    --cc=r.schwebel@pengutronix.de \
    --cc=rgetz@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