From: Scott Wood <scottwood@freescale.com>
To: Igal.Liberman <igal.liberman@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, Emilian.Medve@freescale.com
Subject: Re: [PATCH] clk: ppc-corenet: Add support for the FMD clock
Date: Wed, 25 Feb 2015 17:44:11 -0600 [thread overview]
Message-ID: <1424907851.4698.63.camel@freescale.com> (raw)
In-Reply-To: <1421755411-26357-1-git-send-email-igal.liberman@freescale.com>
On Tue, 2015-01-20 at 14:03 +0200, Igal.Liberman wrote:
> +static u8 get_fm_clk_parent(struct clk_hw *hw)
> +{
> + struct ccsr_guts __iomem *guts_regs = NULL;
> + struct device_node *guts;
> + uint32_t reg = 0;
> + int clk_src = 0;
> + int fm_clk_select = -EINVAL;
> + int fm_id = 0;
> +
> + guts = of_find_matching_node(NULL, guts_device_ids);
> + if (!guts) {
> + pr_err("could not find GUTS node\n");
> + return -EINVAL;
> + }
Error message lacks context (here and elsewhere).
Why are you going this on demand rather than in an init function
(specifically, a CLK_OF_DECLARE)? You should not register this clock
handler in the first place if the hardware doesn't exist.
-EINVAL doesn't fit in u8. Neither would the more appropriate -ENODEV.
> + guts_regs = of_iomap(guts, 0);
> + of_node_put(guts);
> + if (!guts_regs) {
> + pr_err("ioremap of GUTS node failed\n");
> + return -EINVAL;
> + }
> +
> + if (!strcmp(__clk_get_name(hw->clk), "fm1-clk"))
> + fm_id = 1;
> +
> + /* The FM clock provider is SoC dependent and it's determened by the
determined
> + * reset configuration word (RCW). We need to map the RCW options to
> + * the order of the providers in the device tree.
> + * This code makes assumptions about the clock provider order:
> + * In the PXXXX family:
> + * 0 - platform clock/2
> + * 1 - PLLx /2
> + * 2 - PLLx /4 (if possible).
> + * In B/T family:
> + * The same order in which the clock providers are described in
> + * the Reference Manual, starting from 0.
This belongs in a device tree binding document and should not
incorporate portions of the reference manual by reference -- what if a
new version of the reference manual changes the order in which clock
providers are described? Or do you mean that the order corresponds to a
register value?
> + *
> + * In a case of only one possible provider, the index is 0.
> + */
> +
> + if (of_device_is_compatible(guts, "fsl,p1023-guts") ||
> + of_device_is_compatible(guts, "fsl,t1040-device-config"))
> + /* P1023 and T1040 have only one optional clock source */
> + fm_clk_select = 0;
> + else if (of_device_is_compatible(guts, "fsl,p2041-device-config") ||
> + of_device_is_compatible(guts, "fsl,p3041-device-config") ||
> + of_device_is_compatible(guts, "fsl,p4080-device-config")) {
> + /* Read RCW*/
/* Read RCW */
> @@ -352,3 +601,4 @@ CLK_OF_DECLARE(qoriq_core_mux_1, "fsl,qoriq-core-mux-1.0", core_mux_init);
> CLK_OF_DECLARE(qoriq_core_mux_2, "fsl,qoriq-core-mux-2.0", core_mux_init);
> CLK_OF_DECLARE(qoriq_pltfrm_pll_1, "fsl,qoriq-platform-pll-1.0", pltfrm_pll_init);
> CLK_OF_DECLARE(qoriq_pltfrm_pll_2, "fsl,qoriq-platform-pll-2.0", pltfrm_pll_init);
> +CLK_OF_DECLARE(qoriq_fm_mux, "fsl,fman-clk-mux", fm_mux_init);
Where is the binding for this node?
-Scott
next prev parent reply other threads:[~2015-02-25 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 12:03 [PATCH] clk: ppc-corenet: Add support for the FMD clock Igal.Liberman
2015-02-25 23:44 ` Scott Wood [this message]
2015-02-27 16:02 ` Kumar Gala
2015-03-05 0:30 ` Scott Wood
2015-04-08 12:00 ` Igal.Liberman
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=1424907851.4698.63.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Emilian.Medve@freescale.com \
--cc=igal.liberman@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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).