On Fri, Nov 20, 2015 at 02:17:51PM +0800, Shengjiu Wang wrote:

> diff --git a/Documentation/devicetree/bindings/sound/fsl,esai.txt 
> b/Documentation/devicetree/bindings/sound/fsl,esai.txt
> index d3b6b5f..f1d5351 100644
> --- a/Documentation/devicetree/bindings/sound/fsl,esai.txt
> +++ b/Documentation/devicetree/bindings/sound/fsl,esai.txt
> @@ -27,6 +27,8 @@ Required properties:
>                         derive HCK, SCK and FS.
>       "fsys"            The system clock derived from ahb clock used to
>                         derive HCK, SCK and FS.
> +     "spba"            The spba clock is needed when two spba master port
> +                       is used.

I was expecting a little bit more detail like:

+       "spba"          The spba clock is required when ESAI is placed as
                        a bus slave of the Shared Peripheral Bus and when
                        two or more bus masters (CPU, DMA or DSP) try to
                        access it. This property is optional depending on
                        the SoC design.

> diff --git a/sound/soc/fsl/fsl_esai.c b/sound/soc/fsl/fsl_esai.c
> index 504e731..8749f53 100644
> --- a/sound/soc/fsl/fsl_esai.c
> +++ b/sound/soc/fsl/fsl_esai.c
> @@ -54,6 +54,7 @@ struct fsl_esai {
>       struct clk *coreclk;
>       struct clk *extalclk;
>       struct clk *fsysclk;
> +     struct clk *spbaclk;

Please add one entry in the comment above for the new clock.

> @@ -819,6 +826,11 @@ static int fsl_esai_probe(struct platform_device *pdev)
>               dev_warn(&pdev->dev, "failed to get fsys clock: %ld\n",
>                               PTR_ERR(esai_priv->fsysclk));
>  
> +     esai_priv->spbaclk = devm_clk_get(&pdev->dev, "spba");
> +     if (IS_ERR(esai_priv->spbaclk))
> +             dev_warn(&pdev->dev, "Cannot get spba clock: %ld\n",

It'd be better to write the warning following the previous one:
+               dev_warn(&pdev->dev, "failed to get spba clock: %ld\n",
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to