mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Michael Stecklein <m-stecklein@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Andrew F . Davis" <afd@ti.com>
Subject: Re: [PATCH v3 2/2] ASoC: add support for TAS6424 digital amplifier
Date: Wed, 19 Jul 2017 12:08:42 +0100	[thread overview]
Message-ID: <20170719110842.lb2f5cqawnkenhsb@sirena.org.uk> (raw)
In-Reply-To: <1500405604-23511-3-git-send-email-m-stecklein@ti.com>

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

On Tue, Jul 18, 2017 at 02:20:04PM -0500, Michael Stecklein wrote:

> +	if (!tx_mask) {
> +		dev_err(codec->dev, "tdm mask must not be 0\n");
> +		return -EINVAL;
> +	}

Setting the mask to 0 is used when turning off TDM.

> +	if ((reg & TAS6424_WARN_VDD_UV) && !(tas6424->last_warn & TAS6424_WARN_VDD_UV))
> +		dev_warn(dev, "experienced a VDD under voltage condition\n");
> +
> +	if ((reg & TAS6424_WARN_VDD_POR) && !(tas6424->last_warn & TAS6424_WARN_VDD_POR))
> +		dev_warn(dev, "experienced a VDD POR condition\n");

These look like they are errors rather than warnings and should be
critical prints like the other errors.

> +	/* Store current warn value so we can detect any changes next time */
> +	tas6424->last_warn = reg;

It would be better to clear these at some point, perhaps after a delay.
Especially with thermal issues they could come and go over device
operation.

> +static int tas6424_codec_probe(struct snd_soc_codec *codec)
> +{
> +	struct tas6424_data *tas6424 = snd_soc_codec_get_drvdata(codec);
> +	int ret;
> +
> +	tas6424->codec = codec;
> +
> +	ret = regulator_bulk_enable(ARRAY_SIZE(tas6424->supplies),
> +				    tas6424->supplies);
> +	if (ret != 0) {
> +		dev_err(codec->dev, "failed to enable supplies: %d\n", ret);
> +		return ret;
> +	}

This init stuff should be in either the main I2C probe, DAPM or bias
level management.  The CODEC probe should be very minimal.

> +	if (event & SND_SOC_DAPM_POST_PMU) {

> +	} else if (event & SND_SOC_DAPM_PRE_PMD) {

You're trying to write a switch statement here.

> +	switch (level) {
> +	case SND_SOC_BIAS_ON:
> +	case SND_SOC_BIAS_PREPARE:
> +		msleep(500);
> +		break;

You need a 500ms sleep in all these cases?  That's a lot of sleeping.

> +	case SND_SOC_BIAS_STANDBY:
> +		ret = snd_soc_update_bits(codec, TAS6424_CH_STATE_CTRL_REG,
> +					  0xff, TAS6424_CH1_STATE_MUTE | TAS6424_CH2_STATE_MUTE |
> +					  TAS6424_CH3_STATE_MUTE | TAS6424_CH4_STATE_MUTE);
> +
> +		if (ret < 0) {
> +			dev_err(codec->dev, "error resuming device: %d\n", ret);
> +			return ret;
> +		}
> +		break;
> +	case SND_SOC_BIAS_OFF:
> +		ret = snd_soc_update_bits(codec, TAS6424_CH_STATE_CTRL_REG,
> +					  0xff, TAS6424_CH1_STATE_HIZ | TAS6424_CH2_STATE_HIZ |
> +					  TAS6424_CH3_STATE_HIZ | TAS6424_CH4_STATE_HIZ);
> +
> +		if (ret < 0) {
> +			dev_err(codec->dev, "error suspending device: %d\n", ret);
> +			return ret;
> +		}

These mutes seem very random disassociated from anything else?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-07-19 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 19:20 [PATCH v3 0/2] Add support for TI " Michael Stecklein
2017-07-18 19:20 ` [PATCH v3 1/2] dt-bindings: sound: add bindings for TAS6424 Michael Stecklein
2017-07-24 18:58   ` Rob Herring
2017-07-18 19:20 ` [PATCH v3 2/2] ASoC: add support for TAS6424 digital amplifier Michael Stecklein
2017-07-19 11:08   ` Mark Brown [this message]
2017-07-26 17:44     ` Michael Stecklein
2017-07-27 16:41       ` 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=20170719110842.lb2f5cqawnkenhsb@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=afd@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-stecklein@ti.com \
    --cc=mark.rutland@arm.com \
    --cc=perex@perex.cz \
    --cc=robh+dt@kernel.org \
    --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

all inboxes | Powered by JetHome®