From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marco Sinigaglia <marco.sinigaglia@csr.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA SoC on Android problems
Date: Fri, 24 Jun 2011 13:34:14 +0100 [thread overview]
Message-ID: <20110624123413.GA19804@sirena.org.uk> (raw)
In-Reply-To: <4E035DCA.9010409@csr.com>
On Thu, Jun 23, 2011 at 04:37:46PM +0100, Marco Sinigaglia wrote:
> I am quite sure that the kernel does not find/setup the WM9714.
> Assuming that is the kernel that has to configure it, do I have to setup
> something?
> I can see that, on linux-2.6.35/sound/soc/codecs/wm9713.c, the
> wm9713_soc_probe function is not call. Nevertheless, the smdk_wm9713.c
> does run the smdk_init without errors.
You need to write a machine driver for your board and you need to
ensure that all the ASoC devices are registered on your system.
Defining DEBUG at the top of soc-core.c will make ASoC much more verbose
about the probe process.
prev parent reply other threads:[~2011-06-24 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 15:37 ALSA SoC on Android problems Marco Sinigaglia
2011-06-24 12:34 ` Mark Brown [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=20110624123413.GA19804@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=marco.sinigaglia@csr.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