From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sun9i: clk: Fix compile error caused by "clk: sunxi: Give sunxi_factors_register a registers parameter"
Date: Fri, 12 Dec 2014 16:16:28 +0100 [thread overview]
Message-ID: <548B06CC.70101@redhat.com> (raw)
In-Reply-To: <1418397270-9254-1-git-send-email-hdegoede@redhat.com>
Hi,
On 12-12-14 16:14, Hans de Goede wrote:
> My "clk: sunxi: Give sunxi_factors_register a registers parameter" patch did
> not adjust the sunxi_factors_clock register calls in the new clk-sun9i-core.c
> clock code, causing compilation errors. This fixes this.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Sorry, this one is no good, self-nak.
Note to self, the proper order is: test, then git send-email not the other way around.
Regards,
Hans
> ---
> drivers/clk/sunxi/clk-sun9i-core.c | 27 ++++++++++++++++++++++-----
> 1 file changed, 22 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/clk/sunxi/clk-sun9i-core.c b/drivers/clk/sunxi/clk-sun9i-core.c
> index 3cb9036..3b4495c 100644
> --- a/drivers/clk/sunxi/clk-sun9i-core.c
> +++ b/drivers/clk/sunxi/clk-sun9i-core.c
> @@ -22,6 +22,21 @@
>
> #include "clk-factors.h"
>
> +static clk *sun9i_factors_register(struct device_node *node,
> + const struct factors_data *data,
> + spinlock_t *lock)
> +{
> + void __iomem *reg;
> +
> + reg = of_iomap(node, 0);
> + if (!reg) {
> + pr_err("Could not get registers for factors-clk: %s\n",
> + node->name);
> + return NULL;
> + }
> +
> + sunxi_factors_register(node, data, lock, reg);
> +}
>
> /**
> * sun9i_a80_get_pll4_factors() - calculates n, p, m factors for PLL1
> @@ -89,7 +104,7 @@ static DEFINE_SPINLOCK(sun9i_a80_pll4_lock);
>
> static void __init sun9i_a80_pll4_setup(struct device_node *node)
> {
> - sunxi_factors_register(node, &sun9i_a80_pll4_data, &sun9i_a80_pll4_lock);
> + sun9i_factors_register(node, &sun9i_a80_pll4_data, &sun9i_a80_pll4_lock);
> }
> CLK_OF_DECLARE(sun9i_a80_pll4, "allwinner,sun9i-a80-pll4-clk", sun9i_a80_pll4_setup);
>
> @@ -139,8 +154,10 @@ static DEFINE_SPINLOCK(sun9i_a80_gt_lock);
>
> static void __init sun9i_a80_gt_setup(struct device_node *node)
> {
> - struct clk *gt = sunxi_factors_register(node, &sun9i_a80_gt_data,
> + struct clk *gt = sun9i_factors_register(node, &sun9i_a80_gt_data,
> &sun9i_a80_gt_lock);
> + if (!gt)
> + return;
>
> /* The GT bus clock needs to be always enabled */
> __clk_get(gt);
> @@ -194,7 +211,7 @@ static DEFINE_SPINLOCK(sun9i_a80_ahb_lock);
>
> static void __init sun9i_a80_ahb_setup(struct device_node *node)
> {
> - sunxi_factors_register(node, &sun9i_a80_ahb_data, &sun9i_a80_ahb_lock);
> + sun9i_factors_register(node, &sun9i_a80_ahb_data, &sun9i_a80_ahb_lock);
> }
> CLK_OF_DECLARE(sun9i_a80_ahb, "allwinner,sun9i-a80-ahb-clk", sun9i_a80_ahb_setup);
>
> @@ -210,7 +227,7 @@ static DEFINE_SPINLOCK(sun9i_a80_apb0_lock);
>
> static void __init sun9i_a80_apb0_setup(struct device_node *node)
> {
> - sunxi_factors_register(node, &sun9i_a80_apb0_data, &sun9i_a80_apb0_lock);
> + sun9i_factors_register(node, &sun9i_a80_apb0_data, &sun9i_a80_apb0_lock);
> }
> CLK_OF_DECLARE(sun9i_a80_apb0, "allwinner,sun9i-a80-apb0-clk", sun9i_a80_apb0_setup);
>
> @@ -266,6 +283,6 @@ static DEFINE_SPINLOCK(sun9i_a80_apb1_lock);
>
> static void __init sun9i_a80_apb1_setup(struct device_node *node)
> {
> - sunxi_factors_register(node, &sun9i_a80_apb1_data, &sun9i_a80_apb1_lock);
> + sun9i_factors_register(node, &sun9i_a80_apb1_data, &sun9i_a80_apb1_lock);
> }
> CLK_OF_DECLARE(sun9i_a80_apb1, "allwinner,sun9i-a80-apb1-clk", sun9i_a80_apb1_setup);
>
prev parent reply other threads:[~2014-12-12 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 15:14 [PATCH] sun9i: clk: Fix compile error caused by "clk: sunxi: Give sunxi_factors_register a registers parameter" Hans de Goede
2014-12-12 15:16 ` Hans de Goede [this message]
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=548B06CC.70101@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).