From: Takashi Iwai <tiwai@suse.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Stephen Warren <swarren@nvidia.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lrg@ti.com" <lrg@ti.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: snd_dmaengine: add common api for pcm_mmap
Date: Thu, 28 Jun 2012 16:03:25 +0200 [thread overview]
Message-ID: <s5hbok3zg7m.wl%tiwai@suse.de> (raw)
In-Reply-To: <4FEC51BB.2040504@metafoo.de>
At Thu, 28 Jun 2012 14:44:43 +0200,
Lars-Peter Clausen wrote:
>
> On 06/28/2012 01:56 PM, Laxman Dewangan wrote:
> > On Thursday 28 June 2012 04:21 PM, Mark Brown wrote:
> >> * PGP Signed by an unknown key
> >>
> >> On Thu, Jun 28, 2012 at 12:31:26PM +0530, Laxman Dewangan wrote:
> >>> The pcm mmap for the substream dma buffer is done using the
> >>> dma_mmap_writecombine().
> >>> Some of the chip sound driver like Spear, Tegra, Davinci,
> >>> ep93xx,snd_imx, snd_mxs, NUC900, OMAP, Samsung are doing this
> >>> mapping locally.
> >>> Add api in the snd dmaengine driver so that different client of
> >>> snd dmaengine can use this rather than implementing locally.
> >> OK, but I'd expect this to come along with one or more patches
> >> converting at least some of the users to the new API...
> >
> > This is effort towards moving the Tegra pcm driver for dmangine based dma
> > driver inplace of legacy dma driver for Tegra which have private API.
> >
> > Currently, following 4 pcm driver can use this API directly keeping that
> > they already using the generic snd dmaengine pcm driver.
> > ep93xx,
> > spear,
> > fsl,
> > mxs.
> > And Tegra will be next.
> >
> > Other driver which can use this API are davinci, OMAP, samsung but because
> > they are not using the snd_dmaengine_pcm driver's api as of now so not be
> > very much useful for them.
>
> Btw. all these drivers basically use the same code for buffer preallocation.
> Since how the buffer is mmaped is related to how it is allocated it might be
> worth to factor this out at the same time as well.
Hrm. Do you mean hacking more on sound/core/memalloc.c, or sanitize
all these stuff? Adding dma_alloc_writecombine() variant is easy, but
at the same time, I also would like to rip off this ugly thing.
Takashi
next prev parent reply other threads:[~2012-06-28 14:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 7:01 Laxman Dewangan
2012-06-28 10:51 ` Mark Brown
2012-06-28 11:56 ` Laxman Dewangan
2012-06-28 12:02 ` Mark Brown
2012-06-28 12:07 ` Laxman Dewangan
2012-06-28 12:44 ` Lars-Peter Clausen
2012-06-28 14:03 ` Takashi Iwai [this message]
2012-06-28 11:09 ` Lars-Peter Clausen
2012-06-28 12:15 ` Takashi Iwai
2012-06-28 12:18 ` [alsa-devel] " Mark Brown
2012-06-28 12:30 ` Lars-Peter Clausen
2012-06-28 12:28 ` Mark Brown
2012-06-28 12:35 ` Laxman Dewangan
2012-06-28 12:57 ` Takashi Iwai
2012-06-28 13:04 ` Laxman Dewangan
2012-06-28 13:28 ` Takashi Iwai
2012-06-28 13:36 ` Laxman Dewangan
2012-06-28 13:51 ` Takashi Iwai
2012-06-28 14:00 ` Laxman Dewangan
2012-06-28 14:10 ` Takashi Iwai
2012-06-29 16:42 ` Lars-Peter Clausen
2012-07-02 12:50 ` Marek Szyprowski
2012-06-28 12:32 ` Clemens Ladisch
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=s5hbok3zg7m.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=swarren@nvidia.com \
/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
all inboxes | Powered by JetHome®