devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@stlinux.com,
	mturquette@linaro.org, devicetree@vger.kernel.org,
	geert@linux-m68k.org
Subject: Re: [PATCH v6 3/4] clk: Provide always-on clock support
Date: Tue, 7 Apr 2015 22:02:57 -0700	[thread overview]
Message-ID: <20150408050257.GA31970@codeaurora.org> (raw)
In-Reply-To: <1428432239-4114-4-git-send-email-lee.jones@linaro.org>

On 04/07, Lee Jones wrote:
> Lots of platforms contain clocks which if turned off would prove fatal.
> The only way to recover from these catastrophic failures is to restart
> the board(s).  Now, when a clock provider is registered with the
> framework it is possible for a list of always-on clocks to be supplied
> which must be kept ungated.  Each clock mentioned in the newly
> introduced 'clock-always-on' will be clk_prepare_enable()d where the
> normal references will be taken.  This will prevent the common clk
> framework from attempting to gate them during the clk_disable_unused()
> and disable_clock() procedures.
> 
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> ---
>  drivers/clk/clk-conf.c | 43 ++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 42 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/clk-conf.c b/drivers/clk/clk-conf.c
> index aad4796..a07aced 100644
> --- a/drivers/clk/clk-conf.c
> +++ b/drivers/clk/clk-conf.c
> @@ -116,6 +116,43 @@ static int __set_clk_rates(struct device_node *node, bool clk_supplier)
>  	return 0;
>  }
>  
> +static int __set_clk_always_on(struct device_node *node, bool clk_supplier)
> +{
> +	struct of_phandle_args clkspec;
> +	struct clk *clk;
> +	struct property	*prop;
> +	const __be32 *cur;
> +	uint32_t index;

u32 please

> +	int ret;
> +
> +	if (!clk_supplier)
> +		return 0;
> +
> +	of_property_for_each_u32(node, "clock-always-on", prop, cur, index) {
> +		clkspec.np = node;
> +		clkspec.args_count = 1;
> +		clkspec.args[0] = index;
> +
> +		clk = of_clk_get_from_provider(&clkspec);
> +		if (IS_ERR(clk)) {
> +			pr_err("clk: couldn't get clock %u for %s\n",
> +				index, node->full_name);
> +			return PTR_ERR(clk);
> +		}
> +
> +		ret = clk_prepare_enable(clk);
> +		if (ret) {
> +			pr_err("Failed to enable clock %u for %s: %d\n",
> +			       index, node->full_name, ret);
> +			return ret;
> +		}

I guess we don't have a clk_put() here because we want to keep the
refcount high forever? We should at least put a comment here
explaining why we left out clk_put() if so.

> +
> +		pr_debug("Setting clock as always-on %pC\n", clk);
> +	}
> +
> +	return 0;
> +}
> +
>  /**
>   * of_clk_set_defaults() - parse and set assigned clocks configuration
>   * @node: device node to apply clock settings for

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-04-08  5:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 18:43 [PATCH v6 0/4] clk: Provide support for always-on clocks Lee Jones
2015-04-07 18:43 ` [PATCH v6 1/4] ARM: sti: stih407-family: Supply defines for CLOCKGEN A0 Lee Jones
2015-04-07 18:43 ` [PATCH v6 2/4] ARM: sti: stih410-clocks: Identify critical clocks as always-on Lee Jones
     [not found] ` <1428432239-4114-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-04-07 18:43   ` [PATCH v6 3/4] clk: Provide always-on clock support Lee Jones
2015-04-08  5:02     ` Stephen Boyd [this message]
2015-04-07 18:43 ` [PATCH v6 4/4] clk: dt: Introduce binding for " Lee Jones
2015-04-07 19:17   ` Maxime Ripard
2015-04-08  8:14     ` Lee Jones
2015-04-08  9:43       ` Maxime Ripard
2015-04-08 10:38         ` Lee Jones
2015-04-08 15:57           ` Maxime Ripard
2015-04-08 17:23             ` Lee Jones
2015-04-22  9:34               ` Maxime Ripard
2015-04-29 14:17                 ` Lee Jones
2015-04-29 14:33                   ` Geert Uytterhoeven
2015-04-29 15:11                     ` Lee Jones
2015-04-29 20:27                       ` Maxime Ripard
2015-04-29 14:51                   ` Sascha Hauer
2015-04-29 16:07                     ` Lee Jones
2015-04-29 23:05                       ` Michael Turquette
2015-05-04 13:31                         ` Maxime Ripard
2015-04-29 20:23                   ` Maxime Ripard
2015-04-30  9:57                     ` Lee Jones
2015-05-01  5:34                       ` Sascha Hauer
2015-05-01  6:44                         ` Lee Jones
2015-05-07 21:20                           ` Maxime Ripard
2015-05-08  7:22                             ` Lee Jones
2015-05-15 14:12                               ` Maxime Ripard
2015-04-07 20:32   ` Rob Herring
     [not found]   ` <1428432239-4114-5-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-04-08  5:25     ` Stephen Boyd
2015-04-08  5:28 ` [PATCH v6 0/4] clk: Provide support for always-on clocks Stephen Boyd

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=20150408050257.GA31970@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.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;
as well as URLs for NNTP newsgroup(s).