From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: clk: remove cpuclk resources overlapping coredivclk registers on Armada XP
Date: Wed, 18 Mar 2015 16:57:33 +0100 [thread overview]
Message-ID: <5509A06D.60206@free-electrons.com> (raw)
In-Reply-To: <1426596814-30758-1-git-send-email-gregory.clement@free-electrons.com>
Hi,
On 17/03/2015 13:53, Gregory CLEMENT wrote:
> From: Nadav Haklai <nadavh@marvell.com>
>
> The resources of the cpuclk node are overlapping the one from
> coredivclk node. It was not noticed until now because the driver did a
> simple of_iomap and not a request_mem_region. This patch fixes it.
unless someone is against it, I will apply it on mvebu/dt tomorrow.
Thanks,
Gregory
>
> [gregory.clement at free-electrons.com: add commit log and port to 4.0-rc]
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> Signed-off-by: Nadav Haklai <nadavh@marvell.com>
> Signed-off-by: Nadav Haklai <nadavh@marvell.com>
> ---
> arch/arm/boot/dts/armada-xp.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/armada-xp.dtsi b/arch/arm/boot/dts/armada-xp.dtsi
> index 82917236a2fb..fdc2e5bdf459 100644
> --- a/arch/arm/boot/dts/armada-xp.dtsi
> +++ b/arch/arm/boot/dts/armada-xp.dtsi
> @@ -149,7 +149,7 @@
> cpuclk: clock-complex at 18700 {
> #clock-cells = <1>;
> compatible = "marvell,armada-xp-cpu-clock";
> - reg = <0x18700 0xA0>, <0x1c054 0x10>;
> + reg = <0x18700 0x24>, <0x1c054 0x10>;
> clocks = <&coreclk 1>;
> };
>
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-03-18 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 12:53 [PATCH] ARM: mvebu: clk: remove cpuclk resources overlapping coredivclk registers on Armada XP Gregory CLEMENT
2015-03-18 15:57 ` Gregory CLEMENT [this message]
2015-03-18 16:02 ` Thomas Petazzoni
2015-03-19 10:12 ` Gregory CLEMENT
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=5509A06D.60206@free-electrons.com \
--to=gregory.clement@free-electrons.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).