All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Stephen Warren <swarren@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lrg@ti.com" <lrg@ti.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: snd_dmaengine: add common api for pcm_mmap
Date: Thu, 28 Jun 2012 19:30:57 +0530	[thread overview]
Message-ID: <4FEC6399.5050505@nvidia.com> (raw)
In-Reply-To: <s5hd34jzgs0.wl%tiwai@suse.de>

On Thursday 28 June 2012 07:21 PM, Takashi Iwai wrote:
> At Thu, 28 Jun 2012 19:06:07 +0530,
> Laxman Dewangan wrote:
>
>>>> Then how about this?
>>>> create new file and header for snd-pcm-writecombine-buffer.c/.h and put
>>>> this in sound/core.
>>>> Select this file compilation through config SND_PCM_WRITECOMBINE_BUFFER
>>>> which will be select this config through sound/soc/xxx/Kconfig if they
>>>> want to use.
>>>> This will provide three apis: new, free and mmap.
>>> Way too much hustles than necessary...
>> Ooh no. :-(  I had taken the idea from snd_dmaengine_pcm driver.
>> Bit I like to hear simple way which solves the purpose.
> As Lars suggested, a simple ifdef should suffice for now.
> With the upcoming generic dma_mmap_writecombine() stuff, it'd be even
> simpler in future.
>
> But, still we need to be careful about this.  As mentioned, there is
> no flag to know the possibility of writecombine mmap beforehand.
> It'd be nice if we have either a compile-time or a run-time flag /
> function to check that.  Then the driver can also expose the mmap
> capability to user-space depending on the flag.

Yaah, this seems really simple. Thanks for suggestion.
If I understand it fully, the new apis will be declare in sound/pcm.h, 
implement it in pcm_native.c and use the config variable
CONFIG_SND_PCM_WRITECOMBINE_BUFFER for ifdef.

This will be selected in required sound/soc driver so they can use it 
like powerpc (for fsl) and ARM arch based soc.

  reply	other threads:[~2012-06-28 14:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  7:01 [PATCH] ASoC: snd_dmaengine: add common api for pcm_mmap Laxman Dewangan
2012-06-28  7:01 ` Laxman Dewangan
2012-06-28 10:51 ` Mark Brown
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
2012-06-28 14:03         ` [alsa-devel] " Takashi Iwai
2012-06-28 11:09 ` Lars-Peter Clausen
2012-06-28 11:09   ` Lars-Peter Clausen
2012-06-28 12:15   ` Takashi Iwai
2012-06-28 12:18     ` Mark Brown
2012-06-28 12:18       ` [alsa-devel] " Mark Brown
2012-06-28 12:30       ` Lars-Peter Clausen
2012-06-28 12:30         ` [alsa-devel] " 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 12:57               ` [alsa-devel] " Takashi Iwai
2012-06-28 13:04               ` Laxman Dewangan
2012-06-28 13:28                 ` Takashi Iwai
2012-06-28 13:28                   ` [alsa-devel] " Takashi Iwai
2012-06-28 13:36                   ` Laxman Dewangan
2012-06-28 13:51                     ` Takashi Iwai
2012-06-28 14:00                       ` Laxman Dewangan [this message]
2012-06-28 14:10                         ` Takashi Iwai
2012-06-29 16:42                       ` Lars-Peter Clausen
2012-06-29 16:42                         ` [alsa-devel] " 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=4FEC6399.5050505@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=m.szyprowski@samsung.com \
    --cc=swarren@nvidia.com \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.