From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Brian Austin <brian.austin@cirrus.com>
Cc: alsa-devel@alsa-project.org, vinod.koul@linux.intel.com,
joe@nucleusys.com, ramesh.babu@intel.com, lrg@ti.com
Subject: Re: [PATCH v6] ASoC:Add support for cs42l73 codec
Date: Wed, 9 Nov 2011 23:43:19 +0000 [thread overview]
Message-ID: <20111109234318.GB5010@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1320854713-8261-1-git-send-email-brian.austin@cirrus.com>
On Wed, Nov 09, 2011 at 10:05:13AM -0600, Brian Austin wrote:
> Signed-off-by:Brian Austin <brian.austin@cirrus.com>
> Signed-off-by:Georgi Vlaev <joe@nucleusys.com>
>
> This patch adds support for Cirrus Logic CS42L73
> low power stereo codec
Changelogs and signoffs are supposed to go in the other order.
> +static const char * const charge_pump_freq_text[] = {
> + "0", "1", "2", "3", "4",
> + "5", "6", "7", "8", "9",
> + "10", "11", "12", "13", "14", "15" };
> +static const struct soc_enum charge_pump_enum =
> + SOC_ENUM_SINGLE(CS42L73_CPFCHC, 4,
> + ARRAY_SIZE(charge_pump_freq_text), charge_pump_freq_text);
Is there no meaningful text you can use here? I'd expect there must be
as I've no idea how anyone should figure out what to set here, but if
not then making it an enum isn't really worthwhile, just use SOC_SINGLE.
> +static int cs42l73_probe(struct snd_soc_codec *codec)
> +{
> + int ret;
> + unsigned int devid = 0;
> + struct cs42l73_private *cs42l73 = snd_soc_codec_get_drvdata(codec);
> +
> + ret = snd_soc_codec_set_cache_io(codec, 8, 8, SND_SOC_I2C);
It'd be better to move this to using SND_SOC_REGMAP and pushing the
cache down into the register map API with the basic device presence
verification done in the I2C probe but that's not essential yet.
> + if (ret != 0) {
> + printk(KERN_ERR "%s: can't add i2c driver\n", __func__);
pr_err().
next prev parent reply other threads:[~2011-11-09 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 16:05 [PATCH v6] ASoC:Add support for cs42l73 codec Brian Austin
2011-11-09 23:43 ` Mark Brown [this message]
2011-11-09 23:43 ` Mark Brown
2011-11-10 0:20 ` Austin, Brian
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=20111109234318.GB5010@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=joe@nucleusys.com \
--cc=lrg@ti.com \
--cc=ramesh.babu@intel.com \
--cc=vinod.koul@linux.intel.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.