From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Grant Grundler <grundler@parisc-linux.org>,
Joel Soete <soete.joel@scarlet.be>,
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: Wed, 27 Aug 2008 09:06:46 -0500 [thread overview]
Message-ID: <1219846006.3292.3.camel@localhost.localdomain> (raw)
In-Reply-To: <s5h4p57hv4h.wl%tiwai@suse.de>
On Wed, 2008-08-27 at 07:42 +0200, Takashi Iwai wrote:
> At Tue, 26 Aug 2008 15:01:18 -0600,
> Grant Grundler wrote:
> >
> > 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.
>
> Right now it has to be a compile-time option because
> - dma_mmap_coherent() isn't implemented in every architecture (thus
> fails to build), and
> - pages allocated via dma_mmap_coherent() aren't always suitable for
> SG-mapping.
This is trivially fixable by the usual methods, so, as Grant says, we
should employ them rather than non-standard ways of doing this
Basically, you're asking to extend the DMA API, so this should be taken
to linux-arch. That way, it might also give visibility to the graphics
people and we can negotiate over a unified API.
James
next prev parent reply other threads:[~2008-08-27 14:07 UTC|newest]
Thread overview: 28+ 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:04 ` 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
2008-08-27 5:42 ` Takashi Iwai
2008-08-27 10:38 ` Ralf Baechle
2008-08-27 14:06 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 13:21 Takashi Iwai
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 6:07 ` Takashi Iwai
2008-08-22 9:41 ` Thomas Bogendoerfer
2008-08-22 10:23 ` Takashi Iwai
2008-08-22 10:23 ` Takashi Iwai
2008-08-22 14:36 ` Thomas Bogendoerfer
2008-08-22 14:47 ` Takashi Iwai
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=1219846006.3292.3.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=grundler@parisc-linux.org \
--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 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.