From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: dmaengine: Correct Makefile when sound is built as module
Date: Tue, 09 Oct 2012 11:07:11 +0200 [thread overview]
Message-ID: <5073E93F.7090507@ti.com> (raw)
In-Reply-To: <20121009065836.GT8237@opensource.wolfsonmicro.com>
On 10/09/2012 08:58 AM, Mark Brown wrote:
> On Mon, Oct 01, 2012 at 12:29:26PM +0300, Peter Ujfalusi wrote:
>
>> soc-dmaengine-pcm library need to be part of the snd-soc-core in order to
>> be able to compile ASoC as modules when dmaengine is enabled on the platform.
>
> I also meant to ask... what's the actual issue here?
When we build sound as modules for OMAP which has been converted to dmaengine:
ERROR: "snd_hwparams_to_dma_slave_config" [sound/soc/omap/snd-soc-omap.ko]
undefined!
ERROR: "snd_dmaengine_pcm_pointer" [sound/soc/omap/snd-soc-omap.ko] undefined!
ERROR: "snd_dmaengine_pcm_open" [sound/soc/omap/snd-soc-omap.ko] undefined!
ERROR: "snd_dmaengine_pcm_close" [sound/soc/omap/snd-soc-omap.ko] undefined!
ERROR: "snd_dmaengine_pcm_get_chan" [sound/soc/omap/snd-soc-omap.ko] undefined!
ERROR: "snd_dmaengine_pcm_trigger" [sound/soc/omap/snd-soc-omap.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
--
Péter
next prev parent reply other threads:[~2012-10-09 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 9:29 [PATCH] ASoC: dmaengine: Correct Makefile when sound is built as module Peter Ujfalusi
2012-10-08 11:50 ` Péter Ujfalusi
2012-10-09 4:15 ` Mark Brown
2012-10-09 6:57 ` Mark Brown
2012-10-09 6:58 ` Mark Brown
2012-10-09 9:07 ` Péter Ujfalusi [this message]
2012-10-09 9:08 ` Mark Brown
2012-10-09 13:16 ` Péter Ujfalusi
2012-10-10 1:48 ` Mark Brown
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=5073E93F.7090507@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--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 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.