From: Grant Grundler <grundler@parisc-linux.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Joel Soete <soete.joel@scarlet.be>,
"James.Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-mips <linux-mips@linux-mips.org>,
ralf <ralf@linux-mips.org>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] mips: Add dma_mmap_coherent()
Date: Tue, 26 Aug 2008 15:01:18 -0600 [thread overview]
Message-ID: <20080826210118.GA26235@colo.lackof.org> (raw)
In-Reply-To: <s5hej4blrx7.wl%tiwai@suse.de>
On Tue, Aug 26, 2008 at 05:25:24PM +0200, Takashi Iwai wrote:
...
> Now updated my git tree:
> http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=shortlog;h=topic/dma-fix
> I'll post each patch again if preferred.
+#ifdef CONFIG_SND_COHERENT_DMA
#define SNDRV_DMA_TYPE_DEV_SG 3 /* generic device SG-buffer */
+#else
+#define SNDRV_DMA_TYPE_DEV_SG SNDRV_DMA_TYPE_DEV /* no SG-buf support */
+#endif
Hi Takashi,
I had to look at a previous patch to figure out CONFIG_SND_COHERENT_DMA
is an arch dependent flag:
+config SND_COHERENT_DMA
+ def_bool y
+ depends on !PPC32 || !NOT_COHERENT_CACHE
+ depends on !ARM
+ depends on !MIPS
+ depends on !PARISC
In general, I don't expect this to be a compile time option.
I'm wondering if extending the DMA API to provide an
interface for user space to also be DMA coherent.
Maybe something to talk about at Linux Plumbers Conf
or kernel summit...
> Do you guys see any pending issues? I'd love to merge these patches
> into the upstream for 2.6.28.
SPARC/SPARC64 usually falls into the same category as parisc/mips.
>
> To get things clear -- I don't intend to fix the problem of mmap on
> every non-coherent platform perfectly (yet). Instead, this patch
> series is intended to fix the current behavior, at least, for the
> sound drivers not to crash unconditionally. It provides a (minimal)
> way to mmap the pages taken via dma_alloc_coherent().
*nod* that's reasonable.
thanks,
grant
>
>
> Thanks,
>
> Takashi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-08-26 21:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 12:04 [PATCH] mips: Add dma_mmap_coherent() Joel Soete
2008-08-22 12:17 ` Takashi Iwai
2008-08-23 19:39 ` Joel Soete
2008-08-26 15:25 ` Takashi Iwai
2008-08-26 21:01 ` Grant Grundler [this message]
2008-08-27 5:42 ` Takashi Iwai
2008-08-27 10:38 ` Ralf Baechle
2008-08-27 14:06 ` James Bottomley
[not found] <s5hk5eezcfe.wl%tiwai@suse.de>
2008-08-20 16:27 ` James Bottomley
2008-08-20 16:53 ` Takashi Iwai
2008-08-20 17:58 ` James Bottomley
2008-08-21 10:19 ` Takashi Iwai
2008-08-21 13:55 ` James Bottomley
2008-08-21 16:01 ` Takashi Iwai
2008-08-21 16:03 ` Takashi Iwai
2008-08-21 21:41 ` Thomas Bogendoerfer
2008-08-22 6:07 ` Takashi Iwai
2008-08-22 9:41 ` Thomas Bogendoerfer
2008-08-22 10:23 ` Takashi Iwai
2008-08-22 14:36 ` Thomas Bogendoerfer
2008-08-22 14:47 ` Takashi Iwai
2008-08-21 10:20 ` Ralf Baechle
2008-08-21 10:25 ` Takashi Iwai
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=20080826210118.GA26235@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=soete.joel@scarlet.be \
--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