From: ambresh@ti.com (Ambresh K)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch 3/3] clk: Avoid re-parenting orphan clk's having invalid parent index.
Date: Tue, 4 Jun 2013 12:46:32 +0530 [thread overview]
Message-ID: <51AD9450.5090107@ti.com> (raw)
In-Reply-To: <20130529071809.6058.24017@quantum>
On Wednesday 29 May 2013 12:48 PM, Mike Turquette wrote:
> Quoting Ambresh K (2013-05-01 23:25:29)
>> From: Ambresh K <ambresh@ti.com>
>>
>> Add orhan clk nodes having invalid parent index to list and use
>> the list to skip re-parenting orphan clk having invalid parents.
>>
>> Signed-off-by: Ambresh K <ambresh@ti.com>
>> ---
>> drivers/clk/clk.c | 21 +++++++++++++++++++--
>> 1 files changed, 19 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
>> index f4d2c73..54d2aa3 100644
>> --- a/drivers/clk/clk.c
>> +++ b/drivers/clk/clk.c
>> @@ -32,6 +32,7 @@ static int enable_refcnt;
>>
>> static HLIST_HEAD(clk_root_list);
>> static HLIST_HEAD(clk_orphan_list);
>> +static HLIST_HEAD(clk_orphan_invalid_parent);
>
> Why not re-use the clk_orphan_list? Having an invalid value programmed
> into the hardware for selecting a parent essetially orphans a clock
> from a software point of view. Is there a specific need for the new
> list?
Sorry for not being descriptive in commit message.
a) Avoids unnecessary re-parenting cycle for orphan clock's with invalid parent for every clock
b) With patch [1/3], after a clk with invalid parent was encountered, for every clk registered thereafter seeing following logs.
<Snippet>
[ 0.000000] __clk_init: orphan clk(gpu_core_gclk_mux) invalid parent
[ 0.000000] __clk_init: orphan clk(gpu_core_gclk_mux) invalid parent
[ 0.000000] __clk_init: orphan clk(gpu_core_gclk_mux) invalid parent
[ 0.000000] __clk_init: orphan clk(gpu_core_gclk_mux) invalid parent
[ 0.000000] __clk_init: orphan clk(gpu_core_gclk_mux) invalid parent
[ 0.000000] __clk_init: orphan clk(gpu_core_gclk_mux) invalid parent
[ 0.000000] __clk_init: orphan clk(gpu_core_gclk_mux) invalid parent
[ 0.000000] __clk_init: orphan clk(gpu_core_gclk_mux) invalid parent
Please advice, if can be handled better.
Thanks,
Ambresh
>
> Regards,
> Mike
>
>> static LIST_HEAD(clk_notifier_list);
>>
>> /*** locking ***/
>> @@ -1532,8 +1533,8 @@ EXPORT_SYMBOL_GPL(clk_set_parent);
>> */
>> int __clk_init(struct device *dev, struct clk *clk)
>> {
>> - int i, ret = 0;
>> - struct clk *orphan;
>> + int i, ret = 0, skip = 0;
>> + struct clk *orphan, *has_invalid_parent;
>> struct hlist_node *tmp2;
>>
>> if (!clk)
>> @@ -1639,11 +1640,27 @@ int __clk_init(struct device *dev, struct clk *clk)
>> if (!strcmp(clk->name, orphan->name))
>> continue;
>>
>> + /* Skip iteration if orphan has invalid parent */
>> + hlist_for_each_entry(has_invalid_parent,
>> + &clk_orphan_invalid_parent, child_node) {
>> + if (!strcmp(orphan->name, has_invalid_parent->name)) {
>> + skip = 1;
>> + break;
>> + }
>> + }
>> +
>> + if (skip) {
>> + skip = 0;
>> + continue;
>> + }
>> +
>> if (orphan->ops->get_parent) {
>> i = orphan->ops->get_parent(orphan->hw);
>> if (i < 0) {
>> pr_err("%s: orphan clk(%s) invalid parent\n",
>> __func__, orphan->name);
>> + hlist_add_head(&orphan->child_node,
>> + &clk_orphan_invalid_parent);
>> continue;
>> }
>> if (!strcmp(clk->name, orphan->parent_names[i]))
>> --
>> 1.7.4.1
>
next prev parent reply other threads:[~2013-06-04 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 6:25 [Patch 0/3] Fix to clk framework while handling orphan clks Ambresh K
2013-05-02 6:25 ` [Patch 1/3] clk: fix clk_mux_get_parent return's signed value Ambresh K
2013-05-29 7:21 ` Mike Turquette
2013-06-04 6:27 ` Ambresh K
2013-06-04 6:35 ` Mike Turquette
2013-05-02 6:25 ` [Patch 2/3] clk: skip re-parenting orphan clk Ambresh K
2013-05-02 10:09 ` skannan at codeaurora.org
2013-05-02 6:25 ` [Patch 3/3] clk: Avoid re-parenting orphan clk's having invalid parent index Ambresh K
2013-05-29 7:18 ` Mike Turquette
2013-06-04 7:16 ` Ambresh K [this message]
2013-06-11 22:07 ` Mike Turquette
2013-06-13 7:06 ` Ambresh K
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=51AD9450.5090107@ti.com \
--to=ambresh@ti.com \
--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).