From: Rob Herring <robh@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: devicetree@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
Rob Herring <robh@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Versatile AB/PB clocksource support
Date: Wed, 28 Jan 2015 11:56:29 -0600 [thread overview]
Message-ID: <1422467792-2065-1-git-send-email-robh@kernel.org> (raw)
The Versatile clocksource driver can also be used on Versatile AB and PB
platforms, not just Versatile Express. This series adds support for
those boards.
I've split this off from the rest of the Versatile DT and
multi-platform support as I'm not going to get it in place for 3.20.
This part is fairly trivial and is ready to go.
Daniel, Can you please take the whole series.
Rob
Rob Herring (3):
dt/bindings: Add binding for Versatile system registers
clocksource: versatile: adapt for Versatile AB and PB boards
dts: versatile: add sysregs node
Documentation/devicetree/bindings/arm/versatile-sysreg.txt | 10 ++++++++++
arch/arm/boot/dts/versatile-ab.dts | 5 +++++
drivers/clocksource/versatile.c | 4 +++-
3 files changed, 18 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/arm/versatile-sysreg.txt
--
2.1.0
next 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 Rob Herring [this message]
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 ` [PATCH 3/3] dts: versatile: add sysregs node Rob Herring
[not found] ` <1422467792-2065-4-git-send-email-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-02-03 13:23 ` 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-1-git-send-email-robh@kernel.org \
--to=robh@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tglx@linutronix.de \
/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).