From: Clemens Ladisch <clemens@ladisch.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
swarren@nvidia.com, linux-kernel@vger.kernel.org,
Laxman Dewangan <ldewangan@nvidia.com>,
lrg@ti.com
Subject: Re: [alsa-devel] [PATCH] ASoC: snd_dmaengine: add common api for pcm_mmap
Date: Thu, 28 Jun 2012 14:32:33 +0200 [thread overview]
Message-ID: <4FEC4EE1.1030001@ladisch.de> (raw)
In-Reply-To: <20120628121816.GB21029@sirena.org.uk>
Mark Brown wrote:
> On Thu, Jun 28, 2012 at 02:15:38PM +0200, Takashi Iwai wrote:
>> So far, only ARM has dma_mmap_writecombine(), thus the build on other
>> arch would fail as is.
>
> Oh, dear - this means we don't actually have a generic API at all. Is
> there any effort being made to make this generally available?
http://lkml.org/lkml/2012/6/15/27:
| Commit 9adc5374 ('common: dma-mapping: introduce mmap method') added a
| generic method for implementing mmap user call to dma_map_ops structure.
|
| This patch converts ARM and PowerPC architectures (the only providers of
| dma_mmap_coherent/dma_mmap_writecombine calls) to use this generic
| dma_map_ops based call and adds a generic cross architecture
| definition for dma_mmap_attrs, dma_mmap_coherent, dma_mmap_writecombine
| functions.
|
| The generic mmap virt_to_page-based fallback implementation is provided for
| architectures which don't provide their own implementation for mmap method.
|
| Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
| Reviewed-by: Kyungmin Park <kyungmin.park@samsung.com>
| ---
| Hello,
| This patch is a continuation of my works on dma-mapping cleanup and
| unification. Previous works (commit 58bca4a8fa ('Merge branch
| 'for-linus' of git://git.linaro.org/people/mszyprowski/linux-dma-mapping')
| has been merged to v3.4-rc2. Now I've focuses on providing implementation
| for all architectures so the drivers and some cross-architecture common
| helpers (like for example videobuf2) can start using this new api.
|
| I'm not 100% sure if the PowerPC changes are correct. The cases of
| dma_iommu_ops and vio_dma_mapping_ops are a bit suspicious for me, but I
| have no way to test and check if my changes works for that hardware.
|
| Best regards
| Marek Szyprowski
| Samsung Poland R&D Center
Regards,
Clemens
prev parent reply other threads:[~2012-06-28 12:32 UTC|newest]
Thread overview: 23+ 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 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 ` [alsa-devel] " Takashi Iwai
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 [this message]
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=4FEC4EE1.1030001@ladisch.de \
--to=clemens@ladisch.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 \
--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 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).