linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/11] clk: Implement clk_set_rate
Date: Tue, 13 Sep 2011 12:03:28 -0700	[thread overview]
Message-ID: <4E6FA900.7050101@codeaurora.org> (raw)
In-Reply-To: <1314191759-16941-2-git-send-email-broonie@opensource.wolfsonmicro.com>

On 08/24/11 06:15, Mark Brown wrote:
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index ad90a90..3a4d70e 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -21,6 +21,8 @@ struct clk {
>  	unsigned int		enable_count;
>  	unsigned int		prepare_count;
>  	struct clk		*parent;
> +	struct hlist_head	children;
> +	struct hlist_node	child_node;

Shouldn't these hlist nodes be initialized in clk_register() via
INIT_HLIST_*()? I guess it's not explicitly needed because kzalloc is
used, but perhaps it is better to be explicit should the kzalloc change
to a kmalloc.

> @@ -213,16 +266,25 @@ struct clk *clk_register(struct clk_hw_ops *ops, struct clk_hw *hw,
>  	clk->hw = hw;
>  	hw->clk = clk;
>  
> -	/* Query the hardware for parent and initial rate */
> +	/* Query the hardware for parent and initial rate. We may alter
> +	 * the clock topology, making this clock available from the parent's
> +	 * children list. So, we need to protect against concurrent
> +	 * accesses through set_rate
> +	 */
> +	mutex_lock(&prepare_lock);
>  
> -	if (clk->ops->get_parent)
> -		/* We don't to lock against prepare/enable here, as
> -		 * the clock is not yet accessible from anywhere */
> +	if (clk->ops->get_parent) {
>  		clk->parent = clk->ops->get_parent(clk->hw);
> +		if (clk->parent)
> +			hlist_add_head(&clk->child_node,
> +					&clk->parent->children);
> +	}
>  
>  	if (clk->ops->recalc_rate)
>  		clk->rate = clk->ops->recalc_rate(clk->hw);
>  
> +	mutex_unlock(&prepare_lock);
> +
>  
>  	return clk;
>  }
-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  parent reply	other threads:[~2011-09-13 19:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 13:13 [PATCH 0/11] generic struct clk patches Mark Brown
2011-08-24 13:15 ` [PATCH 01/11] clk: Add a generic clock infrastructure Mark Brown
2011-08-24 13:15   ` [PATCH 02/11] clk: Implement clk_set_rate Mark Brown
2011-08-26  8:53     ` Sascha Hauer
2011-08-26  8:55       ` Mark Brown
2011-08-26  8:58         ` Sascha Hauer
2011-08-26  9:01           ` Mark Brown
2011-08-26 23:45     ` Turquette, Mike
2011-09-13 19:03     ` Stephen Boyd [this message]
2011-08-24 13:15   ` [PATCH 03/11] clk: Add fixed-rate clock Mark Brown
2011-08-24 13:15   ` [PATCH 04/11] clk: Add simple gated clock Mark Brown
2011-08-25 13:17     ` Jamie Iles
2011-09-13 19:03     ` Stephen Boyd
2011-08-24 13:15   ` [PATCH 05/11] clk: Prototype and document clk_register() Mark Brown
2011-09-13 19:03     ` Stephen Boyd
2011-08-24 13:15   ` [PATCH 06/11] clk: Provide a dummy clk_unregister() Mark Brown
2011-08-25 11:12     ` Jamie Iles
2011-08-24 13:15   ` [PATCH 07/11] clk: Constify struct clk_hw_ops Mark Brown
2011-08-24 13:15   ` [PATCH 08/11] clk: Avoid clock name collisions Mark Brown
2011-09-13 19:03     ` Stephen Boyd
2011-08-24 13:15   ` [PATCH 09/11] clk: Add Kconfig option to build all generic clk drivers Mark Brown
2011-08-24 13:15   ` [PATCH 10/11] clk: Add initial WM831x clock driver Mark Brown
2011-08-24 13:15   ` [PATCH 11/11] x86: Enable generic clk API on x86 Mark Brown
2011-09-13 19:03   ` [PATCH 01/11] clk: Add a generic clock infrastructure Stephen Boyd
     [not found]   ` <1314191759-16941-1-git-send-email-broonie@opensource.wolfsonmicro.com >
2011-09-14  2:22     ` Saravana Kannan
2011-09-14  9:41       ` Mark Brown

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=4E6FA900.7050101@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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).