From: ambresh@ti.com (Ambresh K)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch 2/3] clk: skip re-parenting orphan clk
Date: Thu, 2 May 2013 11:55:28 +0530 [thread overview]
Message-ID: <1367475929-32166-3-git-send-email-ambresh@ti.com> (raw)
In-Reply-To: <1367475929-32166-1-git-send-email-ambresh@ti.com>
From: Ambresh K <ambresh@ti.com>
If clk is same as orphan clk than skip the iteration, there
by avoiding unnecessary look-up.
Signed-off-by: Ambresh K <ambresh@ti.com>
---
drivers/clk/clk.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index c187321..f4d2c73 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -1635,6 +1635,10 @@ int __clk_init(struct device *dev, struct clk *clk)
* this clock
*/
hlist_for_each_entry_safe(orphan, tmp2, &clk_orphan_list, child_node) {
+ /* Skip if clk is same as orphan clk */
+ if (!strcmp(clk->name, orphan->name))
+ continue;
+
if (orphan->ops->get_parent) {
i = orphan->ops->get_parent(orphan->hw);
if (i < 0) {
--
1.7.4.1
next prev parent reply other threads:[~2013-05-02 6:25 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 ` Ambresh K [this message]
2013-05-02 10:09 ` [Patch 2/3] clk: skip re-parenting orphan clk 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
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=1367475929-32166-3-git-send-email-ambresh@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).