alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ola Lilja <ola.o.lilja@stericsson.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 10/11] ASoC: codecs: Add AB8500 codec-driver
Date: Tue, 8 May 2012 19:27:52 +0100	[thread overview]
Message-ID: <20120508182751.GJ15893@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1336485450-27405-1-git-send-email-ola.o.lilja@stericsson.com>


[-- Attachment #1.1: Type: text/plain, Size: 4350 bytes --]

On Tue, May 08, 2012 at 03:57:30PM +0200, Ola Lilja wrote:

> +static void show_regulator_status(struct snd_soc_dapm_context *dapm)
> +{
> +	struct device *dev = dapm->dev;
> +
> +	dev_dbg(dev, "%s: Regulator-status:\n", __func__);
> +	dev_dbg(dev, "%s:     V-AUD: %s\n", __func__,
> +		(snd_soc_dapm_get_regulator_status(dapm, "V-AUD") > 0) ?
> +			"On" : "Off");

So, you were adding this just for debug...  Let's not do that.  There's
already diagnostic infrastructure in the regulator API and at the DAPM
level too.  If we need this sort of stuff it's probably not device
specific so we should probably improve the core if it's not easy enough
to figure out what's going on already.

> +static void show_clock_status(struct snd_soc_dapm_context *dapm)
> +{
> +	struct device *dev = dapm->dev;

Similarly here (though the clock API diagnostics are probably a bit
weaker).

> +	SND_SOC_DAPM_ADC("ADC", "ab8500_0c", SND_SOC_NOPM, 0, 0),
> +
> +	SND_SOC_DAPM_DAC("DAC", "ab8500_0p", SND_SOC_NOPM, 0, 0),

Please convert all these to use DAPM to hook up the streams to their
audio interfaces rather than having a stream attached to the widget.

> +	/* LineIn */
> +	{"LINL Mute", NULL, "LineIn Left"},
> +	{"LINR Enable", NULL, "LineIn Right"},
> +
> +	{"LINL Enable", NULL, "LINL Mute"},
> +	{"LINR Enable", NULL, "LineIn Right"},

This looks *really* odd, especially with the lack of symmetry.

> +	{"Mic 1a or 1b Select", "Mic 1a", "MIC1A V-AMICx Enable"},
> +	{"Mic 1a or 1b Select", "Mic 1b", "MIC1B V-AMICx Enable"},

This also looks very odd...  is this the micbias stuff again?

> +static int mclk_input_control_get(struct snd_kcontrol *kcontrol,
> +				struct snd_ctl_elem_value *ucontrol)
> +{
> +	struct snd_soc_codec *codec = snd_kcontrol_chip(kcontrol);
> +	struct ab8500_codec_drvdata *drvdata = dev_get_drvdata(codec->dev);
> +
> +	ucontrol->value.enumerated.item[0] = drvdata->mclk_sel;
> +
> +	return 0;
> +}

Same as last time this should be configured by the machine driver.

> +static struct snd_kcontrol_new ab8500_ctrls[] = {
> +	/* Charge pump */
> +	SOC_ENUM("Charge Pump High Threshold For Low Voltage",
> +		soc_enum_envdeththre),
> +	SOC_ENUM("Charge Pump Low Threshold For Low Voltage",
> +		soc_enum_envdetlthre),
> +	SOC_ENUM("Charge Pump Envelope Detection", soc_enum_envdetcpen),
> +	SOC_ENUM("Charge Pump Envelope Detection Decay Time",
> +		soc_enum_envdettime),

Again, why is this all exposed to userspace?

> +	/* Mic 1, Mic 2, LineIn */
> +	SOC_DOUBLE_R_TLV("Mic Master Gain",
> +		AB8500_ADDIGGAIN3, AB8500_ADDIGGAIN4,
> +		0, AB8500_ADDIGGAINX_ADXGAIN_MAX, 1, adx_dig_gain_tlv),

All volume controls should be "...Volume".

> +	SOC_ENUM("Digital Interface 0 Bit-clock Switch", soc_enum_fsbitclk0),
> +	SOC_ENUM("Digital Interface 1 Bit-clock Switch", soc_enum_fsbitclk1),

Hrm?

> +	/* Digital interface - Burst FIFO */
> +	SOC_ENUM("Digital Interface 0 FIFO Enable Switch", soc_enum_if0fifoen),

If this is a "...Switch" it shouldn't be an enum.

> +	/* Attach regulators to AMic DAPM-paths */
> +	dev_dbg(codec->dev, "%s: Mic 1a regulator: %s\n", __func__,
> +		amic_micbias_str(amics->mic1a_micbias));
> +	route = &ab8500_dapm_routes_mic1a_vamicx[amics->mic1a_micbias];
> +	status = snd_soc_dapm_add_routes(&codec->dapm, route, 1);
> +	dev_dbg(codec->dev, "%s: Mic 1b regulator: %s\n", __func__,
> +		amic_micbias_str(amics->mic1b_micbias));
> +	route = &ab8500_dapm_routes_mic1b_vamicx[amics->mic1b_micbias];
> +	status |= snd_soc_dapm_add_routes(&codec->dapm, route, 1);
> +	dev_dbg(codec->dev, "%s: Mic 2 regulator: %s\n", __func__,
> +		amic_micbias_str(amics->mic2_micbias));
> +	route = &ab8500_dapm_routes_mic2_vamicx[amics->mic2_micbias];
> +	status |= snd_soc_dapm_add_routes(&codec->dapm, route, 1);

This is fairly impenetrable and would usually be done in hte machine
driver.  Machines might not use the chip biases for some or all of the
mics but it looks like this code assumes they do.

> +int ab8500_audio_setup_if1(struct snd_soc_codec *codec,
> +			unsigned int fmt,
> +			unsigned int wl,
> +			unsigned int delay)

Why is this not static?

> +static int ab8500_codec_pcm_hw_params(struct snd_pcm_substream *substream,
> +		struct snd_pcm_hw_params *hw_params, struct snd_soc_dai *dai)
> +{
> +	dev_dbg(dai->codec->dev, "%s Enter.\n", __func__);
> +
> +	return 0;

Remove empty functions.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-05-08 18:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 13:57 [PATCH 10/11] ASoC: codecs: Add AB8500 codec-driver Ola Lilja
2012-05-08 18:27 ` Mark Brown [this message]
2012-05-09  7:48   ` Ola Lilja
2012-05-09  8:33     ` Mark Brown
2012-05-09  9:09       ` Ola Lilja
2012-05-09 10:51         ` Mark Brown
2012-05-23  7:04   ` Ola Lilja
2012-05-23 17:40     ` Mark Brown
2012-05-24  6:21       ` Ola Lilja
2012-05-24 10:33         ` 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=20120508182751.GJ15893@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linus.walleij@linaro.org \
    --cc=lrg@ti.com \
    --cc=ola.o.lilja@stericsson.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;
as well as URLs for NNTP newsgroup(s).