From: Ralf Baechle <ralf@linux-mips.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-mips@linux-mips.org, alsa-devel@alsa-project.org,
greg@kroah.com, Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
tiansm@lemote.com, jiankemeng@gmail.com
Subject: Re: ALSA on MIPS platform
Date: Wed, 8 Aug 2007 12:58:52 +0100 [thread overview]
Message-ID: <20070808115852.GA6700@linux-mips.org> (raw)
In-Reply-To: <s5hlkcnmbll.wl%tiwai@suse.de>
On Tue, Aug 07, 2007 at 08:41:10PM +0200, Takashi Iwai wrote:
> > It's ALSA that is doing funny things here so there is no point in fixing
> > the arch code to work for ALSA.
>
> Yep, but OTOH, the arch code doesn't provide a proper standard way to
> mmap the pages allocated via dma_alloc_coherent(). That's the missing
> piece, especially on mips and sparc. ARM has already one.
>
> My wish is implementing dma_mmap_coherent() on all architectures, so
> that the driver can use it safely without messy ifdefs.
Adding dma_mmap_coherent has been proposed in 2004 but the discussion for
some reason went nowhere because it apparently isn't implementable on
PARISC due to cache synonyms - on MIPS we'd solve those issues where they
exist by using uncached or writethrough mappings, as apropriate.
Ralf
next prev parent reply other threads:[~2007-08-08 11:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 7:56 ALSA on MIPS platform Songmao Tian
2007-08-02 14:56 ` Atsushi Nemoto
2007-08-03 13:50 ` Songmao Tian
2007-08-03 13:59 ` Takashi Iwai
2007-08-03 15:57 ` Songmao Tian
2007-08-06 12:17 ` Takashi Iwai
2007-08-07 5:53 ` Dajie Tan
2007-08-07 6:18 ` Dajie Tan
2007-08-07 14:01 ` Atsushi Nemoto
2007-08-07 17:54 ` Ralf Baechle
2007-08-07 18:41 ` Takashi Iwai
2007-08-08 11:58 ` Ralf Baechle [this message]
2007-08-08 12:40 ` Maciej W. Rozycki
2007-08-08 12:57 ` Takashi Iwai
2007-08-09 1:24 ` Songmao Tian
2007-08-08 0:40 ` Songmao Tian
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=20070808115852.GA6700@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alsa-devel@alsa-project.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=greg@kroah.com \
--cc=jiankemeng@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=tiansm@lemote.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).