From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Xiubo Li-B47053 <Li.Xiubo@freescale.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"timur@tabi.org" <timur@tabi.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"rob@landley.net" <rob@landley.net>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/2] ASoC: fsl_sai: Add clock control for SAI
Date: Fri, 4 Apr 2014 17:28:05 +0800 [thread overview]
Message-ID: <20140404092804.GA2735@MrMyself> (raw)
In-Reply-To: <49295d4f0f0f42c4b9c6de77583b978e@BY2PR03MB505.namprd03.prod.outlook.com>
Hi Xiubo,
On Fri, Apr 04, 2014 at 05:24:39PM +0800, Xiubo Li-B47053 wrote:
> Hi,
>
> I have test this series on my Vybrid-TWR board and it works happily.
You just checked the wrong version. I've sent a mail to let people disregard
this version and a newer v2.
>
> [...]
> > diff --git a/sound/soc/fsl/fsl_sai.c b/sound/soc/fsl/fsl_sai.c
> > index 3847d2a..2d749df 100644
> > --- a/sound/soc/fsl/fsl_sai.c
> > +++ b/sound/soc/fsl/fsl_sai.c
> > @@ -428,5 +428,18 @@ static int fsl_sai_startup(struct snd_pcm_substream
> > *substream,
> > {
> > struct fsl_sai *sai = snd_soc_dai_get_drvdata(cpu_dai);
> > - u32 reg;
> > + struct device *dev = &sai->pdev->dev;
> > + u32 reg, ret;
> > +
>
> I'd prefer:
> + int ret;
Just like last time I said, it would be converted to 'int' any way. There's
no much difference between them.
>
> > + ret = clk_prepare_enable(sai->ipg_clk);
> > + if (ret) {
> > + dev_err(dev, "failed to prepare and enable ipg clock\n");
> > + return ret;
> > + }
> > +
>
> [...]
>
> > @@ -609,5 +630,5 @@ static int fsl_sai_probe(struct platform_device *pdev)
> >
> > sai->regmap = devm_regmap_init_mmio_clk(&pdev->dev,
> > - "sai", base, &fsl_sai_regmap_config);
> > + "ipg", base, &fsl_sai_regmap_config);
> > if (IS_ERR(sai->regmap)) {
> > dev_err(&pdev->dev, "regmap init failed\n");
> > @@ -615,4 +636,16 @@ static int fsl_sai_probe(struct platform_device *pdev)
> > }
> >
> > + sai->ipg_clk = devm_clk_get(&pdev->dev, "ipg");
> > + if (IS_ERR(sai->ipg_clk)) {
> > + dev_err(&pdev->dev, "failed to get ipg clock\n");
> > + return PTR_ERR(sai->ipg_clk);
> > + }
> > +
>
> Since the 'ipg' clock is just intend to be used for registers accessing and
> We are using the regmap_init_mmio_clk(), so we can just drop it here and
> Let the regmap APIs to do the clock options properly.
This 'ipg' clock, which I renamed in v2 to 'bus clock', is not just used
in the way you said but also able to drive bit clock as your own code in
the fsl_sai_set_dai_sysclk_tr(), and as reference manual describes:
52.3.1.3 Bus clock
The bus clock is used by the control and configuration registers and to
generate synchronous interrupts and DMA requests.
Thanks,
Nicolin
>
> Otherwise it look good to me.
>
> After this:
> Acked-by: Xiubo Li <Li.Xiubo@freescale.com>
>
>
>
> Thanks,
>
> Brs,
> Xiubo
>
>
>
>
> > + sai->sai_clk = devm_clk_get(&pdev->dev, "sai");
> > + if (IS_ERR(sai->sai_clk)) {
> > + dev_err(&pdev->dev, "failed to get sai clock\n");
> > + return PTR_ERR(sai->sai_clk);
> > + }
> > +
> > irq = platform_get_irq(pdev, 0);
> > if (irq < 0) {
> > diff --git a/sound/soc/fsl/fsl_sai.h b/sound/soc/fsl/fsl_sai.h
> > index 677670d..cbaf114 100644
> > --- a/sound/soc/fsl/fsl_sai.h
> > +++ b/sound/soc/fsl/fsl_sai.h
> > @@ -127,4 +127,6 @@ struct fsl_sai {
> > struct platform_device *pdev;
> > struct regmap *regmap;
> > + struct clk *ipg_clk;
> > + struct clk *sai_clk;
> >
> > bool big_endian_regs;
> > --
> > 1.8.4
> >
>
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Xiubo Li-B47053 <Li.Xiubo@freescale.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"timur@tabi.org" <timur@tabi.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"rob@landley.net" <rob@landley.net>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: Re: [PATCH 1/2] ASoC: fsl_sai: Add clock control for SAI
Date: Fri, 4 Apr 2014 17:28:05 +0800 [thread overview]
Message-ID: <20140404092804.GA2735@MrMyself> (raw)
In-Reply-To: <49295d4f0f0f42c4b9c6de77583b978e@BY2PR03MB505.namprd03.prod.outlook.com>
Hi Xiubo,
On Fri, Apr 04, 2014 at 05:24:39PM +0800, Xiubo Li-B47053 wrote:
> Hi,
>
> I have test this series on my Vybrid-TWR board and it works happily.
You just checked the wrong version. I've sent a mail to let people disregard
this version and a newer v2.
>
> [...]
> > diff --git a/sound/soc/fsl/fsl_sai.c b/sound/soc/fsl/fsl_sai.c
> > index 3847d2a..2d749df 100644
> > --- a/sound/soc/fsl/fsl_sai.c
> > +++ b/sound/soc/fsl/fsl_sai.c
> > @@ -428,5 +428,18 @@ static int fsl_sai_startup(struct snd_pcm_substream
> > *substream,
> > {
> > struct fsl_sai *sai = snd_soc_dai_get_drvdata(cpu_dai);
> > - u32 reg;
> > + struct device *dev = &sai->pdev->dev;
> > + u32 reg, ret;
> > +
>
> I'd prefer:
> + int ret;
Just like last time I said, it would be converted to 'int' any way. There's
no much difference between them.
>
> > + ret = clk_prepare_enable(sai->ipg_clk);
> > + if (ret) {
> > + dev_err(dev, "failed to prepare and enable ipg clock\n");
> > + return ret;
> > + }
> > +
>
> [...]
>
> > @@ -609,5 +630,5 @@ static int fsl_sai_probe(struct platform_device *pdev)
> >
> > sai->regmap = devm_regmap_init_mmio_clk(&pdev->dev,
> > - "sai", base, &fsl_sai_regmap_config);
> > + "ipg", base, &fsl_sai_regmap_config);
> > if (IS_ERR(sai->regmap)) {
> > dev_err(&pdev->dev, "regmap init failed\n");
> > @@ -615,4 +636,16 @@ static int fsl_sai_probe(struct platform_device *pdev)
> > }
> >
> > + sai->ipg_clk = devm_clk_get(&pdev->dev, "ipg");
> > + if (IS_ERR(sai->ipg_clk)) {
> > + dev_err(&pdev->dev, "failed to get ipg clock\n");
> > + return PTR_ERR(sai->ipg_clk);
> > + }
> > +
>
> Since the 'ipg' clock is just intend to be used for registers accessing and
> We are using the regmap_init_mmio_clk(), so we can just drop it here and
> Let the regmap APIs to do the clock options properly.
This 'ipg' clock, which I renamed in v2 to 'bus clock', is not just used
in the way you said but also able to drive bit clock as your own code in
the fsl_sai_set_dai_sysclk_tr(), and as reference manual describes:
52.3.1.3 Bus clock
The bus clock is used by the control and configuration registers and to
generate synchronous interrupts and DMA requests.
Thanks,
Nicolin
>
> Otherwise it look good to me.
>
> After this:
> Acked-by: Xiubo Li <Li.Xiubo@freescale.com>
>
>
>
> Thanks,
>
> Brs,
> Xiubo
>
>
>
>
> > + sai->sai_clk = devm_clk_get(&pdev->dev, "sai");
> > + if (IS_ERR(sai->sai_clk)) {
> > + dev_err(&pdev->dev, "failed to get sai clock\n");
> > + return PTR_ERR(sai->sai_clk);
> > + }
> > +
> > irq = platform_get_irq(pdev, 0);
> > if (irq < 0) {
> > diff --git a/sound/soc/fsl/fsl_sai.h b/sound/soc/fsl/fsl_sai.h
> > index 677670d..cbaf114 100644
> > --- a/sound/soc/fsl/fsl_sai.h
> > +++ b/sound/soc/fsl/fsl_sai.h
> > @@ -127,4 +127,6 @@ struct fsl_sai {
> > struct platform_device *pdev;
> > struct regmap *regmap;
> > + struct clk *ipg_clk;
> > + struct clk *sai_clk;
> >
> > bool big_endian_regs;
> > --
> > 1.8.4
> >
>
next prev parent reply other threads:[~2014-04-04 9:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 11:52 [PATCH 0/2] Add ipg clock control to sai driver Nicolin Chen
2014-04-01 11:52 ` Nicolin Chen
2014-04-01 11:52 ` Nicolin Chen
2014-04-01 11:52 ` [PATCH 1/2] ASoC: fsl_sai: Add clock control for SAI Nicolin Chen
2014-04-01 11:52 ` Nicolin Chen
2014-04-01 11:52 ` Nicolin Chen
2014-04-04 9:24 ` Li.Xiubo
2014-04-04 9:24 ` Li.Xiubo
2014-04-04 9:28 ` Nicolin Chen [this message]
2014-04-04 9:28 ` Nicolin Chen
2014-04-04 9:43 ` Li.Xiubo
2014-04-04 9:43 ` Li.Xiubo
2014-04-04 9:38 ` Nicolin Chen
2014-04-04 9:38 ` Nicolin Chen
[not found] ` <cover.1396352401.git.Guangyu.Chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-04-01 11:52 ` [PATCH 2/2] ARM: dts: Add ipg clock for sai2 on VF610 platform Nicolin Chen
2014-04-01 11:52 ` Nicolin Chen
2014-04-01 11:52 ` Nicolin Chen
2014-04-02 8:01 ` [PATCH 0/2] Add ipg clock control to sai driver Nicolin Chen
2014-04-02 8:01 ` [alsa-devel] " Nicolin Chen
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=20140404092804.GA2735@MrMyself \
--to=guangyu.chen@freescale.com \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.