public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <ml@stefan-roese.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Correct location for ADC/DAC drivers
Date: Fri, 4 May 2007 10:54:05 +0200	[thread overview]
Message-ID: <200705041054.05650.ml@stefan-roese.de> (raw)
In-Reply-To: <20070504082434.GA22585@pengutronix.de>

On Friday 04 May 2007 10:24, Robert Schwebel wrote:
> On Tue, May 01, 2007 at 02:35:44PM +0200, Stefan Roese wrote:
> > I'm in the stage of integrating some ADC and DAC drivers for the AMCC
> > 405EZ PPC and looking for the correct location to place these drivers
> > in the Linux source tree. The drivers are basically character-drivers,
> > so my first thought is to put them in "drivers/char/adc/foo.c" or
> > "drivers/char/adc_foo.c". Is this a good solution?
> >
> > Any suggestions welcome (could be that I missed an already existing
> > example).
> >
> > BTW: I am aware of the hwmon subsystem, but I don't think it fits my
> > needs in this case.
>
> Could you elaborate the requirements a bit more? ADC is not ADC, because
> slow i2c ADCs which measure a temperature every five minutes have other
> requirements than multi-megabyte-per-second-dma-driven ADCs.

The hardware (PPC405EZ) actually implements an high speed, dma capable, ADC 
controller with 10-bit resolution and up to 4MHz sample rate. The current 
driver doesn't support all these features though (dma is not supported right 
now for example). Could be that this will be added in future releases. It 
would be good though, to have the driver located at the "correct" place in 
the kernel tree right away.

Best regards,
Stefan

  reply	other threads:[~2007-05-04  8:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 12:35 Correct location for ADC/DAC drivers 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 [this message]
2007-05-04 18:21     ` Robin Getz
2007-05-04 20:52       ` Robert Schwebel
2007-05-04 22:16         ` Robin Getz
     [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
2007-05-06 13:20         ` Paul Sokolovsky
2007-05-06 16:01         ` Robert Schwebel
2007-05-06 19:33           ` Robin Getz
2007-05-06 20:20         ` Guennadi Liakhovetski

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=200705041054.05650.ml@stefan-roese.de \
    --to=ml@stefan-roese.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=r.schwebel@pengutronix.de \
    /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