From: Mark Brown <broonie@sirena.org.uk>
To: Daniel Gl??ckner <dg@emlix.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [patch 2/2] alsa: s6105 IP camera machine specific ASoC code
Date: Thu, 26 Mar 2009 14:26:40 +0000 [thread overview]
Message-ID: <20090326142640.GE3771@sirena.org.uk> (raw)
In-Reply-To: <1238074574-24734-2-git-send-email-dg@emlix.com>
On Thu, Mar 26, 2009 at 02:36:14PM +0100, Daniel Gl??ckner wrote:
> This patch adds machine specific code for the audio part of the Stretch
> s6105 IP camera reference design.
This looks mostly good, though some of the comments on the platform
support affect this driver too. You should also check for current ASoC
APIs.
> + /* set the codec system clock */
> + ret = snd_soc_dai_set_sysclk(codec_dai, 0, S6105_CODEC_CLOCK,
> + SND_SOC_CLOCK_OUT);
Are you sure you're applying the correct configuration to the correct
DAI here - S6105_CODEC_CLOCK is a CPU define, not a CODEC define?
> +static int snd_soc_dapm_set_endpoint(struct snd_soc_codec *codec, char *name,
> + int status)
> +{
> + if (status)
> + return snd_soc_dapm_enable_pin(codec, name);
> + else
> + return snd_soc_dapm_disable_pin(codec, name);
> +}
This shouldn't be in a driver!
> + snd_soc_dapm_set_endpoint(codec, "Audio Out Differential", !val);
> + snd_soc_dapm_set_endpoint(codec, "Audio Out Stereo", val);
> + snd_soc_dapm_sync(codec);
Hrm. Given the fact that you can't have the stereo and differential
outputs enabled simultaneously is it not safer to first disable the
active output, then sync, then enable the new output?
next prev parent reply other threads:[~2009-03-26 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 13:36 [patch 1/2] alsa: ASoC driver for s6000 I2S interface Daniel Glöckner
2009-03-26 13:36 ` [patch 2/2] alsa: s6105 IP camera machine specific ASoC code Daniel Glöckner
2009-03-26 14:26 ` Mark Brown [this message]
2009-03-27 16:33 ` Daniel Glöckner
2009-03-27 16:39 ` Mark Brown
2009-03-26 14:15 ` [patch 1/2] alsa: ASoC driver for s6000 I2S interface Mark Brown
2009-03-27 16:09 ` Daniel Glöckner
2009-03-27 16:20 ` Mark Brown
2009-03-27 16:49 ` Daniel Glöckner
2009-03-27 16:56 ` 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=20090326142640.GE3771@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=dg@emlix.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.