clk: drop the initial core->parents look-ups from __clk_core_init()

The core->parents is a cache to save expensive clock parent look-ups.
It will be filled as needed later.  We do not have to do it here.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Vladimir Zapolskiy <vz@mleia.com>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>

diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index c2e993db0cfde208ba0cc84eac3498ca065e0828..98c68e99d5f654ba41a7e648cd4be72debfc2fb3 100644 (file)
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -2347,17 +2347,6 @@ static int __clk_core_init(struct clk_core *core)
                                "%s: invalid NULL in %s's .parent_names\n",
                                __func__, core->name);
 
-       /*
-        * clk_core_lookup returns NULL for parents that have not been
-        * clk_init'd; thus any access to clk->parents[] must check
-        * for a NULL pointer.  We can always perform lazy lookups for
-        * missing parents later on.
-        */
-       if (core->parents)
-               for (i = 0; i < core->num_parents; i++)
-                       core->parents[i] =
-                               clk_core_lookup(core->parent_names[i]);
-
        core->parent = __clk_init_parent(core);
 
        /*