Commit 9ca1c5a4 authored by Rajendra Nayak's avatar Rajendra Nayak Committed by Mike Turquette

clk: cache parent clocks only for muxes

caching parent clocks makes sense only when a clock has more
than one parent (mux clocks).
Avoid doing this for every other clock.
Signed-off-by: default avatarRajendra Nayak <rnayak@ti.com>
[mturquette@linaro.org: removed extra parentheses]
Signed-off-by: default avatarMike Turquette <mturquette@linaro.org>
parent f05259a6
...@@ -1235,8 +1235,8 @@ int __clk_init(struct device *dev, struct clk *clk) ...@@ -1235,8 +1235,8 @@ int __clk_init(struct device *dev, struct clk *clk)
* If clk->parents is not NULL we skip this entire block. This allows * If clk->parents is not NULL we skip this entire block. This allows
* for clock drivers to statically initialize clk->parents. * for clock drivers to statically initialize clk->parents.
*/ */
if (clk->num_parents && !clk->parents) { if (clk->num_parents > 1 && !clk->parents) {
clk->parents = kmalloc((sizeof(struct clk*) * clk->num_parents), clk->parents = kzalloc((sizeof(struct clk*) * clk->num_parents),
GFP_KERNEL); GFP_KERNEL);
/* /*
* __clk_lookup returns NULL for parents that have not been * __clk_lookup returns NULL for parents that have not been
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment