Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Xiubo Li <Li.Xiubo@freescale.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
	lgirdwood@gmail.com, timur@tabi.org
Subject: Re: [PATCH 1/4] ASoC: esai: fix buggy of 'ret' type definition.
Date: Thu, 3 Apr 2014 18:50:59 +0800	[thread overview]
Message-ID: <20140403105057.GA32081@MrMyself> (raw)
In-Reply-To: <1396516257-25354-2-git-send-email-Li.Xiubo@freescale.com>

Hi Xiubo,

Could you please add some comments to describe where the bug is? If these
cause function break on Vybrid or LS1, you should tell people what the
root cause exactly is.

On Thu, Apr 03, 2014 at 05:10:54PM +0800, Xiubo Li wrote:
> Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> ---
>  sound/soc/fsl/fsl_esai.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/sound/soc/fsl/fsl_esai.c b/sound/soc/fsl/fsl_esai.c
> index 912104f..8efc89e 100644
> --- a/sound/soc/fsl/fsl_esai.c
> +++ b/sound/soc/fsl/fsl_esai.c
> @@ -209,8 +209,9 @@ static int fsl_esai_set_dai_sysclk(struct snd_soc_dai *dai, int clk_id,
>  	struct clk *clksrc = esai_priv->extalclk;
>  	bool tx = clk_id <= ESAI_HCKT_EXTAL;
>  	bool in = dir == SND_SOC_CLOCK_IN;
> -	u32 ret, ratio, ecr = 0;
> +	u32 ratio, ecr = 0;
>  	unsigned long clk_rate;
> +	int ret;

Using 'u32' instead of 'int' is just an expediency but not a crucial one.
This doesn't make a lot of sense to me.

>  
>  	/* sck_div can be only bypassed if ETO/ERO=0 and SNC_SOC_CLOCK_OUT */
>  	esai_priv->sck_div[tx] = true;
> @@ -432,8 +433,8 @@ static int fsl_esai_set_dai_fmt(struct snd_soc_dai *dai, unsigned int fmt)
>  static int fsl_esai_startup(struct snd_pcm_substream *substream,
>  			    struct snd_soc_dai *dai)
>  {
> -	int ret;
>  	struct fsl_esai *esai_priv = snd_soc_dai_get_drvdata(dai);
> +	int ret;

This looks fine.

Nicolin

>  
>  	/*
>  	 * Some platforms might use the same bit to gate all three or two of
> @@ -491,7 +492,8 @@ static int fsl_esai_hw_params(struct snd_pcm_substream *substream,
>  	bool tx = substream->stream == SNDRV_PCM_STREAM_PLAYBACK;
>  	u32 width = snd_pcm_format_width(params_format(params));
>  	u32 channels = params_channels(params);
> -	u32 bclk, mask, val, ret;
> +	u32 bclk, mask, val;
> +	int ret;
>  
>  	bclk = params_rate(params) * esai_priv->slot_width * 2;
>  
> -- 
> 1.8.4
> 
> 

  reply	other threads:[~2014-04-03 11:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  9:10 [PATCH 0/4] Add ESAI & SPDIF Vybird and LS1+ support Xiubo Li
2014-04-03  9:10 ` [PATCH 1/4] ASoC: esai: fix buggy of 'ret' type definition Xiubo Li
2014-04-03 10:50   ` Nicolin Chen [this message]
2014-04-03  9:10 ` [PATCH 2/4] ASoC: esai: Add Vybird and LS1+ compatibles support Xiubo Li
2014-04-03 11:19   ` Nicolin Chen
2014-04-04  0:46     ` Li.Xiubo
2014-04-03  9:10 ` [PATCH 3/4] ASoC: spdif: Sort the header files alphabetically Xiubo Li
2014-04-03 11:21   ` Nicolin Chen
2014-04-03  9:10 ` [PATCH 4/4] ASoC: spdif: Add Vybird and LS1+ compatibles support Xiubo Li
2014-04-03 12:45   ` Nicolin Chen
2014-04-04  0:41     ` Li.Xiubo
2014-04-03 14:46   ` Fabio Estevam
2014-04-04  0:40     ` Li.Xiubo

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=20140403105057.GA32081@MrMyself \
    --to=guangyu.chen@freescale.com \
    --cc=Li.Xiubo@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=timur@tabi.org \
    /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