From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] dts: versatile: add sysregs node
Date: Wed, 28 Jan 2015 11:56:32 -0600 [thread overview]
Message-ID: <1422467792-2065-4-git-send-email-robh@kernel.org> (raw)
In-Reply-To: <1422467792-2065-1-git-send-email-robh@kernel.org>
The Versatile boards have the same sysregs as other ARM Ltd boards. Add
the nodes in order to enable support for 24MHz counter as sched_clock.
This is a minimal node definition as the existing sub node definition
used on VExpress has some issues raised by Linus W.
Signed-off-by: Rob Herring <robh@kernel.org>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: devicetree at vger.kernel.org
---
arch/arm/boot/dts/versatile-ab.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/versatile-ab.dts b/arch/arm/boot/dts/versatile-ab.dts
index 27d0d9c..01f4019 100644
--- a/arch/arm/boot/dts/versatile-ab.dts
+++ b/arch/arm/boot/dts/versatile-ab.dts
@@ -252,6 +252,11 @@
#size-cells = <1>;
ranges = <0 0x10000000 0x10000>;
+ sysreg at 0 {
+ compatible = "arm,versatile-sysreg", "syscon";
+ reg = <0x00000 0x1000>;
+ };
+
aaci at 4000 {
compatible = "arm,primecell";
reg = <0x4000 0x1000>;
--
2.1.0
next prev parent reply other threads:[~2015-01-28 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 17:56 [PATCH 0/3] Versatile AB/PB clocksource support Rob Herring
2015-01-28 17:56 ` [PATCH 1/3] dt/bindings: Add binding for Versatile system registers Rob Herring
2015-02-03 13:23 ` Linus Walleij
2015-01-28 17:56 ` [PATCH 2/3] clocksource: versatile: adapt for Versatile AB and PB boards Rob Herring
2015-01-29 10:28 ` Liviu Dudau
2015-01-28 17:56 ` Rob Herring [this message]
2015-02-03 13:23 ` [PATCH 3/3] dts: versatile: add sysregs node Linus Walleij
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=1422467792-2065-4-git-send-email-robh@kernel.org \
--to=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).