From: <dinguyen@opensource.altera.com>
To: <sboyd@codeaurora.org>, <mturquette@linaro.org>
Cc: <dinh.linux@gmail.com>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Dinh Nguyen <dinguyen@opensource.altera.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: [PATCH 3/6] clk: keystone: make use of of_clk_parent_fill helper function
Date: Wed, 10 Jun 2015 16:49:22 -0500 [thread overview]
Message-ID: <1433972965-24974-4-git-send-email-dinguyen@opensource.altera.com> (raw)
In-Reply-To: <1433972965-24974-1-git-send-email-dinguyen@opensource.altera.com>
From: Dinh Nguyen <dinguyen@opensource.altera.com>
Use of_clk_parent_fill to fill in the parent clock names' array.
Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>
---
drivers/clk/keystone/pll.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/clk/keystone/pll.c b/drivers/clk/keystone/pll.c
index 0dd8a4b..d885372 100644
--- a/drivers/clk/keystone/pll.c
+++ b/drivers/clk/keystone/pll.c
@@ -293,8 +293,7 @@ static void __init of_pll_mux_clk_init(struct device_node *node)
return;
}
- parents[0] = of_clk_get_parent_name(node, 0);
- parents[1] = of_clk_get_parent_name(node, 1);
+ of_clk_parent_fill(node, parents, 2);
if (!parents[0] || !parents[1]) {
pr_err("%s: missing parent clocks\n", __func__);
return;
--
2.2.1
next prev parent reply other threads:[~2015-06-10 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 21:49 [PATCH 0/6] clk: " dinguyen
2015-06-10 21:49 ` [PATCH 1/6] clk: at91: " dinguyen
2015-06-10 21:49 ` [PATCH 2/6] clk: qoriq: " dinguyen
2015-06-10 21:49 ` dinguyen [this message]
2015-06-10 22:14 ` [PATCH 3/6] clk: keystone: " santosh shilimkar
2015-06-10 21:49 ` [PATCH 4/6] clk: st: " dinguyen
2015-06-11 7:37 ` Gabriel Fernandez
2015-06-10 21:49 ` [PATCH 5/6] clk: sunxi: " dinguyen
2015-06-11 9:06 ` Maxime Ripard
2015-06-11 19:55 ` Dinh Nguyen
2015-06-10 21:49 ` [PATCH 6/6] clk: ti: " dinguyen
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=1433972965-24974-4-git-send-email-dinguyen@opensource.altera.com \
--to=dinguyen@opensource.altera.com \
--cc=dinh.linux@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=ssantosh@kernel.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
Powered by JetHome