All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Neri <ricardo.neri@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Jarkko Nikula <jarkko.nikula@bitmer.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: Re: Build error: undefined reference to `snd_soc_unregister_codec'
Date: Fri, 27 Apr 2012 10:16:47 -0500	[thread overview]
Message-ID: <4F9AB85F.3020107@ti.com> (raw)
In-Reply-To: <20120427132818.GO24211@n2100.arm.linux.org.uk>

Hi Rusell,

On 04/27/2012 08:28 AM, Russell King - ARM Linux wrote:
> When building ALSA as modules:
>
> drivers/built-in.o: In function `omapdss_hdmihw_remove':
> omap_hwspinlock.c:(.text+0x23da8): undefined reference to `snd_soc_unregister_codec'
> drivers/built-in.o: In function `omapdss_hdmihw_probe':
> omap_hwspinlock.c:(.text+0x24248): undefined reference to `snd_soc_register_codec'
>
> (the filename is inaccurate).
>
> This happens because drivers/video/omap2/dss/hdmi.c is built-in and uses
> ASoC services, but ASoC and ALSA are modular.

As you mention, this happens because the ASoC HDMI codec is embeeded in 
the DSS driver. There is a set of patches currently under discussion to 
decouple the ASoC HDMI codec from DSS[1]. This will fix the issue.

BR,
[1]http://www.spinics.net/lists/linux-omap/msg67307.html

Ricardo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2012-04-27 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 13:28 Build error: undefined reference to `snd_soc_unregister_codec' Russell King - ARM Linux
2012-04-27 15:16 ` Ricardo Neri [this message]

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=4F9AB85F.3020107@ti.com \
    --to=ricardo.neri@ti.com \
    --cc=jarkko.nikula@bitmer.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=peter.ujfalusi@ti.com \
    --cc=tomi.valkeinen@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.