From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Girdwood, Liam" <lrg@ti.com>,
linux-next@vger.kernel.org
Subject: Re: ASoC on today's linux-next: dma_alloc_writecombine() failing at least on OMAP platforms
Date: Thu, 27 Sep 2012 13:59:34 +0100 [thread overview]
Message-ID: <20120927125934.GV4428@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <506443AD.1060201@ti.com>
On Thu, Sep 27, 2012 at 03:16:45PM +0300, Peter Ujfalusi wrote:
> Can someone try linux-next on non OMAP platform to see if
> dma_alloc_writecombine() works there?
> Meanwhile I'll try to find the reason why it fails for me.
Do you have CMA enabled? There seems to be some breakage there for me
on Samsung platforms, I saw this affecting all DMA users yesterday along
with some other CMA related issues but didn't analyse it enough to
report it.
next prev parent reply other threads:[~2012-09-27 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 12:16 ASoC on today's linux-next: dma_alloc_writecombine() failing at least on OMAP platforms Peter Ujfalusi
2012-09-27 12:59 ` Mark Brown [this message]
2012-09-27 13:25 ` Peter Ujfalusi
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=20120927125934.GV4428@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
/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.