From: Chris Brandt <chris.brandt@renesas.com>
To: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Chris Brandt <chris.brandt@renesas.com>
Subject: [PATCH 0/3] ARM: dts: add ostm support for r7s72100
Date: Thu, 12 Jan 2017 14:01:05 -0500 [thread overview]
Message-ID: <20170112190108.2856-1-chris.brandt@renesas.com> (raw)
This patch set enables the use of the newly created driver
renesas-ostm.c for the r7s72100 SoC.
This patch set depends on the acceptance of:
[PATCH 1/2] dt-bindings: document renesas-ostm timer
[PATCH 2/2] clocksource: Add renesas-ostm timer driver
Chris Brandt (3):
ARM: dts: r7s72100: add ostm clock to device tree
ARM: dts: r7s72100: add ostm to device tree
ARM: dts: rskrza1: add ostm DT support
arch/arm/boot/dts/r7s72100-rskrza1.dts | 4 ++++
arch/arm/boot/dts/r7s72100.dtsi | 21 +++++++++++++++++++++
include/dt-bindings/clock/r7s72100-clock.h | 4 ++++
3 files changed, 29 insertions(+)
--
2.10.1
next reply other threads:[~2017-01-12 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 19:01 Chris Brandt [this message]
2017-01-12 19:01 ` [PATCH 1/3] ARM: dts: r7s72100: add ostm clock to device tree Chris Brandt
[not found] ` <20170112190108.2856-2-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-01-13 8:38 ` Geert Uytterhoeven
2017-01-12 19:01 ` [PATCH 2/3] ARM: dts: r7s72100: add ostm " Chris Brandt
2017-01-12 19:01 ` [PATCH 3/3] ARM: dts: rskrza1: add ostm DT support Chris Brandt
2017-01-13 8:40 ` Geert Uytterhoeven
2017-01-13 14:50 ` Chris Brandt
[not found] ` <20170112190108.2856-4-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-01-13 9:08 ` Sergei Shtylyov
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=20170112190108.2856-1-chris.brandt@renesas.com \
--to=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--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).