From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
"Girdwood, Liam" <lrg@ti.com>,
linux-next@vger.kernel.org
Subject: ASoC on today's linux-next: dma_alloc_writecombine() failing at least on OMAP platforms
Date: Thu, 27 Sep 2012 15:16:45 +0300 [thread overview]
Message-ID: <506443AD.1060201@ti.com> (raw)
Hello,
I tried today's linux-next on OMAP platform and audio is not probing because
dma_alloc_writecombine() fails to get the area.
My linux-next from two days ago works OK and I don't see anything directly
connected to OMAP which can cause this failure.
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.
Thanks,
Péter
next reply other threads:[~2012-09-27 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 12:16 Peter Ujfalusi [this message]
2012-09-27 12:59 ` ASoC on today's linux-next: dma_alloc_writecombine() failing at least on OMAP platforms Mark Brown
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=506443AD.1060201@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-next@vger.kernel.org \
--cc=lrg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox