From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] vexpress: Initialise the sysregs before setting up the clocks
Date: Thu, 01 May 2014 16:14:35 +0100 [thread overview]
Message-ID: <1398957275.3452.69.camel@linaro1.home> (raw)
In-Reply-To: <1398953107-29426-1-git-send-email-catalin.marinas@arm.com>
On Thu, 2014-05-01 at 15:05 +0100, Catalin Marinas wrote:
[...]
> In addition, vexpress_sysreg_init() is changed to a device_initcall()
Not in this patch it isn't ;-)
> as the core_initcall() is no longer
> required.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> Tested-by: Will Deacon <will.deacon@arm.com>
> Acked-by: Will Deacon <will.deacon@arm.com>
> Tested-by: Pawel Moll <pawel.moll@arm.com>
> Acked-by: Pawel Moll <pawel.moll@arm.com>
> Cc: Mike Turquette <mturquette@linaro.org>
> ---
>
> Mike, I'd like to get this in for 3.15 and I'm happy to push it via the arm64
> tree. Are you ok with this? Thanks.
>
> drivers/clk/versatile/clk-vexpress-osc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/versatile/clk-vexpress-osc.c b/drivers/clk/versatile/clk-vexpress-osc.c
> index a535c7bf8574..422391242b39 100644
> --- a/drivers/clk/versatile/clk-vexpress-osc.c
> +++ b/drivers/clk/versatile/clk-vexpress-osc.c
> @@ -100,6 +100,8 @@ void __init vexpress_osc_of_setup(struct device_node *node)
> struct clk *clk;
> u32 range[2];
>
> + vexpress_sysreg_of_early_init();
> +
> osc = kzalloc(sizeof(*osc), GFP_KERNEL);
> if (!osc)
> return;
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-05-01 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 14:05 [PATCH] vexpress: Initialise the sysregs before setting up the clocks Catalin Marinas
2014-05-01 15:14 ` Jon Medhurst (Tixy) [this message]
2014-05-01 16:07 ` Catalin Marinas
2014-05-01 20:16 ` Sergei Shtylyov
2014-05-01 21:46 ` Catalin Marinas
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=1398957275.3452.69.camel@linaro1.home \
--to=tixy@linaro.org \
--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