All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "jjinfo@nudt.edu.cn" <jjinfo@nudt.edu.cn>
Cc: alsa-devel@alsa-project.org
Subject: Re: Problem on wm8974 alsa driver
Date: Sun, 20 Jun 2010 14:27:44 +0100	[thread overview]
Message-ID: <20100620132744.GC2405@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <MPTMAFLHXLTAAHZYLDISCAXRPPTF.jjinfo@nudt.edu.cn>

On Sun, Jun 20, 2010 at 01:48:03AM +0800, jjinfo@nudt.edu.cn wrote:

> By now, we can confirm that the digital signal has arrived the wm8974
> DAI interface.  As per wm8974 manual, it is required to set some 8974
> registers(such as enabling DAC, MONOOUT,etc) so as to get analogue
> signal.

> However, the codec driver (wm8974.c) does not provide any routine to
> set those necessary registers. My question is, where and how are these

What makes you say that the driver has no support for these things?  The
driver provides automatic power management and application control for
audio routing and gains.  This control should be fairly complete.  For
example, the DAC power is controlled by line 221:

	SND_SOC_DAPM_DAC("DAC", "HiFi Playback", WM8974_POWER3, 0, 0),

This will be enabled when a playback is active and the DAC is connected
to an output.

> outpu-related registers of audio codec chip  got correctly set up? Are
> they set up by aplay via calling alsa library APIs?  Must we provide
> additional help functions to do such initialization?

aplay only deals with streaming PCM data to the CODEC.  You should use
an application such as alsamixer or amixer to configure the CODEC into
the desired state at runtime.  

           reply	other threads:[~2010-06-20 13:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <MPTMAFLHXLTAAHZYLDISCAXRPPTF.jjinfo@nudt.edu.cn>]

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=20100620132744.GC2405@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jjinfo@nudt.edu.cn \
    /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.