From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rajeev Kumar <rajeev-dlh.kumar@st.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH V4 1/5] sound: asoc: Adding support for STA529 Audio Codec
Date: Mon, 6 Jun 2011 12:55:19 +0100 [thread overview]
Message-ID: <20110606115519.GC8286@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1307339856-30656-2-git-send-email-rajeev-dlh.kumar@st.com>
On Mon, Jun 06, 2011 at 11:27:32AM +0530, Rajeev Kumar wrote:
> This patch adds the support for STA529 audio codec.
> Details of the audio codec can be seen here:
> http://www.st.com/internet/imag_video/product/159187.jsp
As I'm fairly sure I've said before please do try to use subject lines
for your patches which are consistent with the style for the subsystem
you're submitting against.
> +struct sta529 {
> + unsigned int sysclk;
> + enum snd_soc_control_type control_type;
> + void *control_data;
why do you need the control_data here? You also don't need to pass the
control_type if the device is I2C only.
> +static const struct snd_kcontrol_new sta529_new_snd_controls[] = {
> + SOC_ENUM("PWM Select", pwm_src_enum),
> + SOC_ENUM("MODE Select", mode_src_enum),
MODE especially should be configured by _dai_fmt().
> +static int sta529_mute(struct snd_soc_dai *dai, int mute)
> +{
> + struct snd_soc_codec *codec = dai->codec;
> +
> + u8 mute_reg = snd_soc_read(codec, STA529_FFXCFG0) & ~CODEC_MUTE_VAL;
> +
> + if (mute)
> + mute_reg |= CODEC_MUTE_VAL;
> +
> + snd_soc_update_bits(codec, STA529_FFXCFG0, 0x80, 00);
This update completely ignores the check you've made above...
> + /*
> + * store the label for powers down audio subsystem for suspend.This is
> + * used by soc core layer
> + */
You want a space after the period here.
> +static struct snd_soc_dai_driver sta529_dai = {
> + .name = "sta529-audio",
Does the chip have non-audio funtionality?
> + snd_soc_add_controls(codec, sta529_snd_controls,
> + ARRAY_SIZE(sta529_snd_controls));
> +
> + snd_soc_add_controls(codec, sta529_new_snd_controls,
> + ARRAY_SIZE(sta529_new_snd_controls));
Like Lars-Peter said use data based init here.
> +static int sta529_resume(struct snd_soc_codec *codec)
> +{
> + snd_soc_cache_sync(codec);
> + sta529_set_bias_level(codec, SND_SOC_BIAS_STANDBY);
> + sta529_set_bias_level(codec, codec->dapm.suspend_bias_level);
The second set_bias_level() should be redundant - we'll always have been
shut down by the core before we get to suspending.
> +static int __init sta529_modinit(void)
> +{
> + int ret = 0;
> +
> + ret = i2c_add_driver(&sta529_i2c_driver);
> + if (ret != 0)
> + printk(KERN_ERR "Failed to reg sta529 I2C driver: %d\n", ret);
Error out if we can't load; ignoring the error only makes sense if we
have multiple bus types and another might have succeeded.
next prev parent reply other threads:[~2011-06-06 11:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 5:57 [PATCH V4 0/5] Adding ASoC drivers for SPEAr13XX platform Rajeev Kumar
2011-06-06 5:57 ` [PATCH V4 1/5] sound: asoc: Adding support for STA529 Audio Codec Rajeev Kumar
2011-06-06 5:57 ` [PATCH V4 2/5] sound: asoc: Adding support for SPEAr13XX ASoC platform driver Rajeev Kumar
2011-06-06 5:57 ` [PATCH V4 3/5] sound: asoc: Adding support for SPEAr13XX ASoC machine driver Rajeev Kumar
2011-06-06 5:57 ` [PATCH V4 4/5] sound: asoc: Adding Kconfig and Makefile to support SPEAr13XX ASoC driver Rajeev Kumar
2011-06-06 5:57 ` [PATCH V4 5/5] sound: asoc: Adding support for SPEAr13XX in soc Rajeev Kumar
2011-06-07 14:17 ` [PATCH V4 4/5] sound: asoc: Adding Kconfig and Makefile to support SPEAr13XX ASoC driver Mark Brown
2011-06-07 14:16 ` [PATCH V4 3/5] sound: asoc: Adding support for SPEAr13XX ASoC machine driver Mark Brown
2011-06-07 14:12 ` [PATCH V4 2/5] sound: asoc: Adding support for SPEAr13XX ASoC platform driver Mark Brown
2011-06-08 9:05 ` Liam Girdwood
2011-06-06 6:23 ` [PATCH V4 1/5] sound: asoc: Adding support for STA529 Audio Codec Lars-Peter Clausen
2011-06-06 7:08 ` rajeev
2011-06-06 7:35 ` Lars-Peter Clausen
2011-06-06 10:19 ` rajeev
2011-06-07 7:06 ` Lars-Peter Clausen
2011-06-06 11:55 ` Mark Brown [this message]
2011-06-07 6:08 ` rajeev
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=20110606115519.GC8286@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=rajeev-dlh.kumar@st.com \
--cc=tiwai@suse.de \
/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.