From: Prashant Gaikwad <pgaikwad@nvidia.com>
To: <mturquette@ti.com>
Cc: <swarren@wwwdotorg.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Prashant Gaikwad <pgaikwad@nvidia.com>
Subject: [PATCH] clk: Fix cached parent ptrs allocation
Date: Wed, 4 Jul 2012 18:45:37 +0530 [thread overview]
Message-ID: <1341407737-1016-1-git-send-email-pgaikwad@nvidia.com> (raw)
Compiler optimizes code someway that even if clk->parents
is not NULL it tries to allocate parents array. Change the
condition so that compiler does not optimize it in wrong
way.
Also, initialize i to num_parents to make sure parent
is searched using parent name if parents is NULL.
Signed-off-by: Prashant Gaikwad <pgaikwad@nvidia.com>
---
Mike,
There could be some other way to fix problem. I have not
debugged it in detail but I think this simple change should do.
drivers/clk/clk.c | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index 026d901..b28f2ae 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -1066,18 +1066,18 @@ static int __clk_set_parent(struct clk *clk, struct clk *parent)
struct clk *old_parent;
unsigned long flags;
int ret = -EINVAL;
- u8 i;
+ u8 i = clk->num_parents;
old_parent = clk->parent;
/* find index of new parent clock using cached parent ptrs */
- if (clk->parents)
+ if (!clk->parents)
+ clk->parents = kzalloc((sizeof(struct clk*) * clk->num_parents),
+ GFP_KERNEL);
+ else
for (i = 0; i < clk->num_parents; i++)
if (clk->parents[i] == parent)
break;
- else
- clk->parents = kzalloc((sizeof(struct clk*) * clk->num_parents),
- GFP_KERNEL);
/*
* find index of new parent clock using string name comparison
--
1.7.4.1
next reply other threads:[~2012-07-04 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 13:15 Prashant Gaikwad [this message]
2012-07-05 1:10 ` Prashant Gaikwad
2012-07-05 16:07 ` Stephen Warren
2012-07-05 17:21 ` Prashant Gaikwad
2012-07-05 18:44 ` Stephen Warren
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=1341407737-1016-1-git-send-email-pgaikwad@nvidia.com \
--to=pgaikwad@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=swarren@wwwdotorg.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®