mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Cosmin-Gabriel Samoila <cosmin.samoila@nxp.com>
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, wakasugi.jb@om.asahi-kasei.co.jp,
	shengjiu.wang@nxp.com, daniel.baluta@nxp.com,
	mihai.serban@gmail.com, linux-imx@nxp.com,
	Mihai Serban <mihai.serban@nxp.com>
Subject: Re: [PATCH] ASoC: codecs: Add support for AK4458 DAC driver
Date: Wed, 31 Jan 2018 17:03:30 +0000	[thread overview]
Message-ID: <20180131170330.GB7763@sirena.org.uk> (raw)
In-Reply-To: <1517404809-25250-1-git-send-email-cosmin.samoila@nxp.com>

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

On Wed, Jan 31, 2018 at 03:20:09PM +0200, Cosmin-Gabriel Samoila wrote:

This looks pretty good overall, I've got some issues below but nothing
too major:

> +static int ak4458_i2c_remove(struct i2c_client *i2c)
> +{
> +	ak4458_remove(&i2c->dev);
> +	pm_runtime_disable(&i2c->dev);

It's weird that the runtime PM handling is here and not in the shared
code, and that it only exists in the I2C version.  Why is this?

> +static const struct soc_enum ak4458_dac_enum[] = {
> +/*0*/	SOC_ENUM_SINGLE(AK4458_01_CONTROL2, 1,
> +			ARRAY_SIZE(ak4458_dem_select_texts),
> +			ak4458_dem_select_texts),
> +/*1*/	SOC_ENUM_SINGLE(AK4458_0A_CONTROL6, 0,

The fact that you need these comments is why these arrays are a bad idea
- just use individually named variables as other drivers do.

> +static const struct snd_kcontrol_new ak4458_snd_controls[] = {
> +	SOC_SINGLE_TLV("AK4458 L1ch Digital Volume",
> +		       AK4458_03_LCHATT, 0/*shift*/, 0xFF/*max value*/,
> +		       0/*invert*/, latt_tlv),
> +	SOC_SINGLE_TLV("AK4458 R1ch Digital Volume",
> +		       AK4458_04_RCHATT, 0, 0xFF, 0, ratt_tlv),

It'd be more idiomatic to combine these into stereo pairs than have them
as single channel controls.

> +static const char * const ak4458_dac_select_texts[] = { "OFF", "ON" };

This looks like the users should be switch controls - what's the goal
here?

> +	rstn = snd_soc_read(codec, AK4458_00_CONTROL1);
> +	rstn &= ~AK4458_RSTN_MASK;
> +
> +	if (bit)
> +		rstn |= AK4458_RSTN;
> +
> +	snd_soc_write(codec, AK4458_00_CONTROL1, rstn);

This looks like an open coded snd_soc_update_bits()?

> +static int ak4458_hw_params(struct snd_pcm_substream *substream,
> +			    struct snd_pcm_hw_params *params,
> +			    struct snd_soc_dai *dai)
> +{
> +	struct snd_soc_codec *codec = dai->codec;
> +	struct ak4458_priv *ak4458 = snd_soc_codec_get_drvdata(codec);
> +	u8 format;
> +	int pcm_width = max(params_physical_width(params), ak4458->slot_width);
> +
> +#ifdef AK4458_ACKS_USE_MANUAL_MODE
> +	u8 dfs1, dfs2;
> +#endif

What's this and why is it a compile time option?

> +	case 32:
> +		if (ak4458->fmt == SND_SOC_DAIFMT_I2S)
> +			format |= AK4458_DIF_32BIT_I2S;
> +		else if (ak4458->fmt == SND_SOC_DAIFMT_LEFT_J)
> +			format |= AK4458_DIF_32BIT_MSB;
> +		else if (ak4458->fmt == SND_SOC_DAIFMT_RIGHT_J)
> +			format |= AK4458_DIF_32BIT_LSB;
> +		else if (ak4458->fmt == SND_SOC_DAIFMT_DSP_B)
> +			format |= AK4458_DIF_32BIT_MSB;
> +		else
> +			return -EINVAL;

This should be a switch statement.

> +	switch (fmt & SND_SOC_DAIFMT_FORMAT_MASK) {
> +	case SND_SOC_DAIFMT_I2S:
> +	case SND_SOC_DAIFMT_LEFT_J:
> +	case SND_SOC_DAIFMT_RIGHT_J:
> +		ak4458->fmt = fmt & SND_SOC_DAIFMT_FORMAT_MASK;
> +		break;
> +	case SND_SOC_DAIFMT_DSP_B:
> +		ak4458->fmt = fmt & SND_SOC_DAIFMT_FORMAT_MASK;
> +		break;

All these cases seem to be the same?

> +static int ak4458_trigger(struct snd_pcm_substream *substream, int cmd,
> +			  struct snd_soc_dai *codec_dai)
> +{
> +	int ret = 0;
> +
> +	dev_dbg(codec_dai->dev, "%s(%d)\n", __func__, __LINE__);
> +	return ret;
> +}

Remove empty functions.

> +	ak4458->mute_gpio = of_get_named_gpio(np, "ak4458,mute_gpio", 0);
> +	if (gpio_is_valid(ak4458->mute_gpio)) {

Given that this is new code it'd be better to use GPIO descriptors, this
will also allow support for non-DT systems - use devm_gpiod_get() and
the matching APIs.

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

  reply	other threads:[~2018-01-31 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 13:20 Cosmin-Gabriel Samoila
2018-01-31 17:03 ` Mark Brown [this message]
2018-02-09 10:22   ` Cosmin Samoila
2018-02-09 15:47     ` Mark Brown
2018-02-13  9:22   ` Cosmin Samoila
2018-02-13 11:55     ` Mark Brown
2018-02-05  6:08 ` Rob Herring
2018-02-12 12:47 ` Fabio Estevam

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=20180131170330.GB7763@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cosmin.samoila@nxp.com \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.serban@gmail.com \
    --cc=mihai.serban@nxp.com \
    --cc=shengjiu.wang@nxp.com \
    --cc=wakasugi.jb@om.asahi-kasei.co.jp \
    /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®