From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: Shengjiu Wang <shengjiu.wang@freescale.com>,
alsa-devel@alsa-project.org, lgirdwood@gmail.com, tiwai@suse.de,
linux-kernel@vger.kernel.org, broonie@kernel.org, timur@tabi.org,
Li.Xiubo@freescale.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [alsa-devel] [PATCH V1] ASoC: fsl_ssi: refine ipg clock usage in this module
Date: Tue, 9 Sep 2014 23:42:12 -0700 [thread overview]
Message-ID: <20140910064211.GA7652@Asurada> (raw)
In-Reply-To: <20140910062118.GA26348@pengutronix.de>
On Wed, Sep 10, 2014 at 08:21:18AM +0200, Markus Pargmann wrote:
> On Tue, Sep 09, 2014 at 11:38:05AM -0700, Nicolin Chen wrote:
> > On Tue, Sep 09, 2014 at 05:18:07PM +0800, Shengjiu Wang wrote:
> > > @@ -1321,7 +1333,11 @@ static int fsl_ssi_probe(struct platform_device *pdev)
> > > return -ENOMEM;
> > > }
> > >
> > > - ssi_private->regs = devm_regmap_init_mmio(&pdev->dev, iomem,
> > > + if (ssi_private->soc->imx)
> > > + ssi_private->regs = devm_regmap_init_mmio_clk(&pdev->dev,
> > > + "ipg", iomem, &fsl_ssi_regconfig);
> > > + else
> > > + ssi_private->regs = devm_regmap_init_mmio(&pdev->dev, iomem,
> >
> > As Markus mentioned, the key point here is to be compatible with those
> > non-clock-name platforms.
> >
> > I think it would be safer to keep the current code while adding an extra
> > clk_disable_unprepare() at the end of probe() as a common routine. And
> > meantime, make sure to have the call for imx only because it seems that
> > the other platforms do not depend on the clock. //a bit guessing here :)
> >
> > Then we can get a patch like:
> > open() {
> > + clk_prepare_enable();
> > ....
> > }
> >
> > close() {
> > ....
> > + clk_disable_unprepare()
> > }
> >
> > probe() {
> > clk_get();
> > clk_prepare_enable();
> > ....
> > if (xxx)
> > - goto err_xx;
> > + return ret;
> > ....
> > + clk_disable_unprepare();
> > return 0;
> > -err_xx:
> > - clk_disable_unprepare()
> > }
> >
> > remove() {
> > ....
> > - clk_disable_unprepare()
> > }
>
> If I remember correctly, there may be AC97 communication with the codec
> before any substream is created. That's why we enable the SSI unit right
> at the beginning for AC97 in fsl_ssi_setup_reg_vals(). So we need to
> check for AC97 before disabling clocks.
Thank you for the input. That's the exact part I couldn't be sure.
And I agree that adding a check for AC97 will be safer while this
may keeps itself removable if being unnecessary.
Thanks
Nicolin
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: Shengjiu Wang <shengjiu.wang@freescale.com>,
timur@tabi.org, alsa-devel@alsa-project.org, tiwai@suse.de,
Li.Xiubo@freescale.com, linux-kernel@vger.kernel.org,
lgirdwood@gmail.com, broonie@kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [alsa-devel] [PATCH V1] ASoC: fsl_ssi: refine ipg clock usage in this module
Date: Tue, 9 Sep 2014 23:42:12 -0700 [thread overview]
Message-ID: <20140910064211.GA7652@Asurada> (raw)
In-Reply-To: <20140910062118.GA26348@pengutronix.de>
On Wed, Sep 10, 2014 at 08:21:18AM +0200, Markus Pargmann wrote:
> On Tue, Sep 09, 2014 at 11:38:05AM -0700, Nicolin Chen wrote:
> > On Tue, Sep 09, 2014 at 05:18:07PM +0800, Shengjiu Wang wrote:
> > > @@ -1321,7 +1333,11 @@ static int fsl_ssi_probe(struct platform_device *pdev)
> > > return -ENOMEM;
> > > }
> > >
> > > - ssi_private->regs = devm_regmap_init_mmio(&pdev->dev, iomem,
> > > + if (ssi_private->soc->imx)
> > > + ssi_private->regs = devm_regmap_init_mmio_clk(&pdev->dev,
> > > + "ipg", iomem, &fsl_ssi_regconfig);
> > > + else
> > > + ssi_private->regs = devm_regmap_init_mmio(&pdev->dev, iomem,
> >
> > As Markus mentioned, the key point here is to be compatible with those
> > non-clock-name platforms.
> >
> > I think it would be safer to keep the current code while adding an extra
> > clk_disable_unprepare() at the end of probe() as a common routine. And
> > meantime, make sure to have the call for imx only because it seems that
> > the other platforms do not depend on the clock. //a bit guessing here :)
> >
> > Then we can get a patch like:
> > open() {
> > + clk_prepare_enable();
> > ....
> > }
> >
> > close() {
> > ....
> > + clk_disable_unprepare()
> > }
> >
> > probe() {
> > clk_get();
> > clk_prepare_enable();
> > ....
> > if (xxx)
> > - goto err_xx;
> > + return ret;
> > ....
> > + clk_disable_unprepare();
> > return 0;
> > -err_xx:
> > - clk_disable_unprepare()
> > }
> >
> > remove() {
> > ....
> > - clk_disable_unprepare()
> > }
>
> If I remember correctly, there may be AC97 communication with the codec
> before any substream is created. That's why we enable the SSI unit right
> at the beginning for AC97 in fsl_ssi_setup_reg_vals(). So we need to
> check for AC97 before disabling clocks.
Thank you for the input. That's the exact part I couldn't be sure.
And I agree that adding a check for AC97 will be safer while this
may keeps itself removable if being unnecessary.
Thanks
Nicolin
next prev parent reply other threads:[~2014-09-10 6:42 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 9:18 [PATCH V1] ASoC: fsl_ssi: refine ipg clock usage in this module Shengjiu Wang
2014-09-09 9:18 ` Shengjiu Wang
2014-09-09 9:18 ` Shengjiu Wang
2014-09-09 9:49 ` [alsa-devel] " Markus Pargmann
2014-09-09 9:49 ` Markus Pargmann
2014-09-09 9:55 ` Li.Xiubo
2014-09-09 9:55 ` Li.Xiubo
2014-09-09 11:27 ` Mark Brown
2014-09-09 11:27 ` Mark Brown
2014-09-09 11:27 ` Mark Brown
2014-09-09 18:03 ` Nicolin Chen
2014-09-09 18:03 ` Nicolin Chen
2014-09-09 18:15 ` Mark Brown
2014-09-09 18:15 ` Mark Brown
2014-09-09 18:15 ` Mark Brown
2014-09-09 18:41 ` Nicolin Chen
2014-09-09 18:41 ` Nicolin Chen
2014-09-09 13:17 ` Timur Tabi
2014-09-09 15:21 ` Mark Brown
2014-09-09 15:21 ` Mark Brown
2014-09-09 15:24 ` Timur Tabi
2014-09-09 15:24 ` Timur Tabi
2014-09-09 15:24 ` Timur Tabi
2014-09-09 18:38 ` Nicolin Chen
2014-09-09 18:38 ` Nicolin Chen
2014-09-09 19:37 ` Timur Tabi
2014-09-09 19:37 ` Timur Tabi
2014-09-09 19:59 ` Nicolin Chen
2014-09-09 19:59 ` Nicolin Chen
2014-09-09 19:59 ` Nicolin Chen
2014-09-09 20:03 ` Timur Tabi
2014-09-09 20:03 ` Timur Tabi
2014-09-09 20:03 ` Timur Tabi
2014-09-09 20:27 ` Nicolin Chen
2014-09-09 20:27 ` Nicolin Chen
2014-09-09 20:37 ` Timur Tabi
2014-09-09 20:37 ` Timur Tabi
2014-09-09 20:37 ` Timur Tabi
2014-09-09 21:09 ` Nicolin Chen
2014-09-09 21:09 ` Nicolin Chen
2014-09-09 21:09 ` Nicolin Chen
2014-09-10 10:01 ` Shengjiu Wang
2014-09-10 10:01 ` Shengjiu Wang
2014-09-10 10:01 ` Shengjiu Wang
2014-09-10 6:21 ` Markus Pargmann
2014-09-10 6:21 ` Markus Pargmann
2014-09-10 6:42 ` Nicolin Chen [this message]
2014-09-10 6:42 ` [alsa-devel] " Nicolin Chen
2014-09-10 10:30 ` Shengjiu Wang
2014-09-10 10:30 ` Shengjiu Wang
2014-09-10 10:30 ` Shengjiu Wang
2014-09-10 10:53 ` Markus Pargmann
2014-09-10 10:53 ` Markus Pargmann
2014-09-10 8:12 ` Shengjiu Wang
2014-09-10 8:12 ` Shengjiu Wang
2014-09-10 8:12 ` Shengjiu Wang
2014-09-10 17:42 ` Nicolin Chen
2014-09-10 17:42 ` Nicolin Chen
2014-09-11 6:36 ` Markus Pargmann
2014-09-11 6:36 ` Markus Pargmann
2014-09-11 6:36 ` Markus Pargmann
2014-09-11 7:07 ` Shengjiu Wang
2014-09-11 7:07 ` Shengjiu Wang
2014-09-11 7:07 ` Shengjiu Wang
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=20140910064211.GA7652@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpa@pengutronix.de \
--cc=shengjiu.wang@freescale.com \
--cc=timur@tabi.org \
--cc=tiwai@suse.de \
/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.