From: Mark Brown <broonie@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: tlv320adcx140: Add the tlv320adcx140 codec driver family
Date: Mon, 10 Feb 2020 13:52:52 +0000 [thread overview]
Message-ID: <20200210135252.GK7685@sirena.org.uk> (raw)
In-Reply-To: <20200207194533.29967-2-dmurphy@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]
On Fri, Feb 07, 2020 at 01:45:33PM -0600, Dan Murphy wrote:
> + /* interface format */
> + switch (fmt & SND_SOC_DAIFMT_FORMAT_MASK) {
> + case SND_SOC_DAIFMT_I2S:
> + iface_reg1 |= ADCX140_I2S_MODE_BIT;
> + break;
> + case SND_SOC_DAIFMT_LEFT_J:
> + iface_reg1 |= ADCX140_LEFT_JUST_BIT;
> + break;
> + case SND_SOC_DAIFMT_DSP_A:
> + case SND_SOC_DAIFMT_DSP_B:
> + break;
_DSP_A and _DSP_B are two different format so I'd expect the device to
be configured differently for them, or for only one to be supported.
> +static int adcx140_mute(struct snd_soc_dai *codec_dai, int mute)
> +{
> + struct snd_soc_component *component = codec_dai->component;
> + int config_reg;
> + int mic_enable;
> + int i;
> +
> + /* There is not a single register to mute. Each enabled path has to be
> + * muted individually. Read which path is enabled and mute it.
> + */
> + snd_soc_component_read(component, ADCX140_IN_CH_EN, &mic_enable);
> + if (!mic_enable)
> + return 0;
You could also just offer this control to userspace, it's not
*essential* to have this operation though it can help with glitching
during stream startup.
> +
> + for (i = 0; i < ADCX140_MAX_CHANNELS; i++) {
> + config_reg = ADCX140_CH8_CFG2 - (5 * i);
> + if (!(mic_enable & BIT(i)))
> + continue;
> +
> + if (mute)
> + snd_soc_component_write(component, config_reg, 0);
> + }
How does the unmute work?
> + internal_reg = device_property_present(adcx140->dev,
> + "ti,use-internal-areg");
> +
> + if (internal_reg)
> + sleep_cfg_val |= ADCX140_AREG_INTERNAL;
Does this actually need a specific property or could you support the
regulator API and then use regulator_get_optional() to figure out if an
external AVDD is attached?
> +static int adcx140_codec_probe(struct snd_soc_component *component)
> +{
> + struct adcx140_priv *adcx140 = snd_soc_component_get_drvdata(component);
> +
> + return adc5410_init(adcx140);
> +}
Does the separate init function buy us anything?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-10 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 19:45 [PATCH 1/2] dt-bindings: sound: Add TLV320ADCx140 dt bindings Dan Murphy
2020-02-07 19:45 ` [PATCH 2/2] ASoC: tlv320adcx140: Add the tlv320adcx140 codec driver family Dan Murphy
2020-02-10 13:52 ` Mark Brown [this message]
2020-02-11 16:24 ` Dan Murphy
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=20200210135252.GK7685@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dmurphy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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).