All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Shengjiu Wang <shengjiu.wang@freescale.com>
Cc: timur@tabi.org, Li.Xiubo@freescale.com, lgirdwood@gmail.com,
	broonie@kernel.org, perex@perex.cz, tiwai@suse.de,
	alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, mpa@pengutronix.de
Subject: Re: [PATCH V1] ASoC: fsl_ssi: refine ipg clock usage in this module
Date: Tue, 9 Sep 2014 11:38:05 -0700	[thread overview]
Message-ID: <20140909183804.GA6944@Asurada> (raw)
In-Reply-To: <e5a50d8bfde3aea5fcd092118da5aea4072c7e2f.1410254125.git.shengjiu.wang@freescale.com>

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()
}

As long as you make the subject clear as 'Don't enable core/ipg clock
when SSI's idle', I'm sure you can make them within a single patch.

And an alternative way for open() and close() is to put those code into
pm_runtime_resume/suspend() instead (since we might have some internal
code need to be added by using pm_runtime as well), which would make
the further code neater IMO.

Thank you
Nicolin

WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Shengjiu Wang <shengjiu.wang@freescale.com>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com, tiwai@suse.de,
	Li.Xiubo@freescale.com, timur@tabi.org, perex@perex.cz,
	broonie@kernel.org, mpa@pengutronix.de,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V1] ASoC: fsl_ssi: refine ipg clock usage in this module
Date: Tue, 9 Sep 2014 11:38:05 -0700	[thread overview]
Message-ID: <20140909183804.GA6944@Asurada> (raw)
In-Reply-To: <e5a50d8bfde3aea5fcd092118da5aea4072c7e2f.1410254125.git.shengjiu.wang@freescale.com>

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()
}

As long as you make the subject clear as 'Don't enable core/ipg clock
when SSI's idle', I'm sure you can make them within a single patch.

And an alternative way for open() and close() is to put those code into
pm_runtime_resume/suspend() instead (since we might have some internal
code need to be added by using pm_runtime as well), which would make
the further code neater IMO.

Thank you
Nicolin

  parent reply	other threads:[~2014-09-09 18:38 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 [this message]
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     ` [alsa-devel] " Nicolin Chen
2014-09-10  6:42       ` 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=20140909183804.GA6944@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=perex@perex.cz \
    --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.