mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Pavel Machek <pavel@ucw.cz>, Stephen Boyd <sboyd@codeaurora.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / clk: Do not __clk_get passed in clock-references
Date: Mon, 05 Oct 2015 22:54:13 +0200	[thread overview]
Message-ID: <7126718.0ZHn4yyKKA@vostro.rjw.lan> (raw)
In-Reply-To: <4072102.uMAk2BYxyL@diego>

On Thursday, October 01, 2015 09:05:09 PM Heiko Stübner wrote:
> From: Stephen Boyd <sboyd@codeaurora.org>
> 
> Clock references are on a per-user basis now, so they are not supposed
> to be refcounted by itself anymore. Therefore multiple cascaded get and
> put calls will fail.
> 
> When a clock reference gets passed into pm_clk_add_clk we can assume
> that the pm clock handling will take control of the clock reference,
> so after this functions returns the caller should've given up control
> of that handle.
> 
> So remove the additional call to __clk_get() in __pm_clk_add().
> 
> The only current user of pm_clk_add_clk is drivers/clk/shmobile/clk-mstp.c
> which already follows this paradigm by only getting the clock but not
> puting it after passing the reference into pm_clk_add_clk.
> 
> In the error case the caller is expected to clean up the clock, as it
> may very well try to do something different if pm_clk_add_clk() fails.
> 
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> [add commit-message]
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> Hi Rafael, Pavel,
> 
> if that looks acceptable to you, it would be cool if you could ack the
> patch and allow me to put it in front of [0] or alternatively
> provide a stable-branch I could include.

OK

Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>


> [0] https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v4.4-armsoc/drivers
> 
>  drivers/base/power/clock_ops.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/base/power/clock_ops.c b/drivers/base/power/clock_ops.c
> index 652b5a3..6ce7693 100644
> --- a/drivers/base/power/clock_ops.c
> +++ b/drivers/base/power/clock_ops.c
> @@ -93,7 +93,7 @@ static int __pm_clk_add(struct device *dev, const char *con_id,
>  			return -ENOMEM;
>  		}
>  	} else {
> -		if (IS_ERR(clk) || !__clk_get(clk)) {
> +		if (IS_ERR(clk)) {
>  			kfree(ce);
>  			return -ENOENT;
>  		}
> @@ -127,7 +127,9 @@ int pm_clk_add(struct device *dev, const char *con_id)
>   * @clk: Clock pointer
>   *
>   * Add the clock to the list of clocks used for the power management of @dev.
> - * It will increment refcount on clock pointer, use clk_put() on it when done.
> + * The power-management code will take control of the clock reference, so
> + * callers should not call clk_put() on @clk after this function sucessfully
> + * returned.
>   */
>  int pm_clk_add_clk(struct device *dev, struct clk *clk)
>  {
> 


      reply	other threads:[~2015-10-05 20:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 19:05 Heiko Stübner
2015-10-05 20:54 ` Rafael J. Wysocki [this message]

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=7126718.0ZHn4yyKKA@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sboyd@codeaurora.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

all inboxes | Powered by JetHome®