linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Nobin Mathew" <nobin.mathew@gmail.com>
To: dinesh <dinesh.dua@coraltele.com>,
	"Nobin Mathew" <nobin.mathew@gmail.com>,
	"Grant Likely" <grant.likely@secretlab.ca>,
	linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
	liam.girdwood@wolfsonmicro.com
Subject: Re: [alsa-devel] WRITING AN SOC DRIVER WITHOUT DMA
Date: Thu, 17 Jul 2008 16:56:52 +0530	[thread overview]
Message-ID: <8d6898730807170426wac4719cv7cd925cfcd91aa68@mail.gmail.com> (raw)
In-Reply-To: <20080717105614.GC15333@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 949 bytes --]

Hi Dinesh,

If that is your requirement then go and see the actual code
sound/arm/aaci.c. They are not using DMA. It is programmed IO.


Thanks
Nobin Mathew

On 7/17/08, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>
> On Thu, Jul 17, 2008 at 11:33:31AM +0530, dinesh wrote:
>
> > What i want is that i have a buffer in driver code which is also handled
> > by some other application i want that this buffer data is to be used for
> > capture and playback  stream fills data to another buffer which i can
> > passover to my other application.
>
> Depending on what exactly you're doing here you may find that this is
> best implemented in user space with an ALSA plugin rather than doing it
> as part of a driver.  If you do want to do this in kernel space then the
> parts of an ASoC driver which transfer audio data are just the same as
> those for any other ALSA driver so things like sound/arm/aaci.c may
> provide useful examples.
>

[-- Attachment #2: Type: text/html, Size: 1374 bytes --]

  reply	other threads:[~2008-07-17 11:26 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-12  8:39 [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Grant Likely
2008-07-12  8:39 ` [PATCH v2 2/3] ALSA SoC: Add mpc5200-psc I2S driver Grant Likely
2008-07-14 12:10   ` [alsa-devel] " Mark Brown
2008-07-12  8:39 ` [PATCH v2 3/3] ALSA SoC: Add Texas Instruments TLV320AIC26 codec driver Grant Likely
2008-07-12 18:10   ` [alsa-devel] " Mark Brown
2008-07-12 18:14     ` Grant Likely
2008-07-14 11:45   ` Mark Brown
2008-07-18  6:29     ` Grant Likely
2008-07-18 10:39       ` Mark Brown
2008-07-15  7:57   ` dinesh
2008-07-15 10:33     ` Mark Brown
2008-07-15 12:38       ` dinesh
2008-07-15 12:46         ` Mark Brown
2008-07-16  9:05   ` WRITING AN SOC DRIVER WITHOUT DMA dinesh
2008-07-16 10:07     ` [alsa-devel] " Nobin Mathew
2008-07-16 10:13       ` dinesh
2008-07-17  6:03         ` dinesh
2008-07-17 10:56           ` Mark Brown
2008-07-17 11:26             ` Nobin Mathew [this message]
2008-07-17 12:05               ` Jon Smirl
2008-07-17 16:02   ` [PATCH v2 3/3] ALSA SoC: Add Texas Instruments TLV320AIC26 codec driver Timur Tabi
2008-07-14 13:49 ` [alsa-devel] [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Mark Brown
2008-07-14 14:13   ` Jon Smirl
2008-07-14 15:05     ` Mark Brown
2008-07-14 16:14       ` Timur Tabi
2008-07-14 16:27         ` Grant Likely
2008-07-14 16:53         ` Mark Brown
2008-07-14 17:21           ` Grant Likely
2008-07-14 18:36             ` Mark Brown
2008-07-14 18:40               ` Timur Tabi
2008-07-14 18:49                 ` Mark Brown
2008-07-14 18:53                   ` Timur Tabi
2008-07-14 22:28                 ` Grant Likely
2008-07-14 23:45                 ` Jon Smirl
2008-07-15 10:13                   ` Mark Brown
2008-07-15 13:08                     ` Jon Smirl
2008-07-15 14:04                       ` Mark Brown
2008-07-14 15:51     ` Timur Tabi
2008-07-14 17:06   ` Grant Likely
2008-07-14 17:16     ` Mark Brown
2008-07-14 17:22       ` Grant Likely
2008-07-18  7:17       ` Grant Likely
2008-07-18 10:00         ` Mark Brown
2008-07-18 14:59         ` Timur Tabi
2008-07-14 14:16 ` Anton Vorontsov
2008-07-14 17:11   ` Grant Likely

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=8d6898730807170426wac4719cv7cd925cfcd91aa68@mail.gmail.com \
    --to=nobin.mathew@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dinesh.dua@coraltele.com \
    --cc=grant.likely@secretlab.ca \
    --cc=liam.girdwood@wolfsonmicro.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).