alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: tim.howe@cirrus.com
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
	paul.handrigan@cirrus.com
Subject: Re: [PATCH v3] ASoC: cs53l30: Add support for Cirrus Logic CS53L30
Date: Fri, 5 Feb 2016 18:37:13 +0000	[thread overview]
Message-ID: <20160205183713.GA4455@sirena.org.uk> (raw)
In-Reply-To: <1453763683-10009-1-git-send-email-tim.howe@cirrus.com>


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

On Mon, Jan 25, 2016 at 05:14:43PM -0600, tim.howe@cirrus.com wrote:
> From: Tim Howe <tim.howe@cirrus.com>

I'd have got to this sooner but there was an unreplied mail from the
0day bot...  anyway, a few fairly minor issues here:

> +	default:
> +		pr_err("Invalid event = 0x%x\n", event);
> +		return -EINVAL;
> +	}

dev_err().

> +	regmap_read(priv->regmap, CS53L30_MCLKCTL, &mclk_ctl);
> +	mclk_ctl &= ~MCLK_DIV;
> +	mclk_ctl |= cs53l30_mclkx_coeffs[mclkx_coeff].mclkdiv;
> +
> +	regmap_write(priv->regmap, CS53L30_MCLKCTL, mclk_ctl);

This is open coding regmap_update_bits(), several other bits of the
driver seem to be doing something similar.

> +		regmap_read(priv->regmap, CS53L30_IS, &reg); /* Clr status */
> +		for (i = 0; i < inter_max_check; i++) {
> +			usleep_range(1000, 1000);
> +			msleep(1);

So we do a usleep_range() for 1ms then a msleep() for 1ms...  why not
just do one or the other for 2ms?  It at least looks weird and needs a
comment.

> +/* CS53L30_ADCDMIC1_CTL1  */
> +#define ADC1B_PDN		(1 << 7)
> +#define ADC1A_PDN		(1 << 6)

These constants really need namespacing - a lot of them have pretty
generic names so look like they might end up colliding with a kernel
header.

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

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



  parent reply	other threads:[~2016-02-05 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  2:14 [PATCH v3] ASoC: cs53l30: Add support for Cirrus Logic CS53L30 kbuild test robot
2016-01-25 23:14 ` tim.howe
2016-01-26  2:14   ` [PATCH] ASoC: cs53l30: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-27 10:09   ` [PATCH v3] ASoC: cs53l30: Add support for Cirrus Logic CS53L30 Charles Keepax
2016-02-05 18:37   ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-14 22:37 me

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=20160205183713.GA4455@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=paul.handrigan@cirrus.com \
    --cc=tim.howe@cirrus.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).