From: Rich Felker <dalias@libc.org>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sh@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH v8 0/2] J-Core timer support
Date: Sun, 09 Oct 2016 05:34:22 +0000 [thread overview]
Message-ID: <cover.1475990489.git.dalias@libc.org> (raw)
Resubmitted with the (incorrect) workaround for rcu_sched stalls
removed, since the problem was found in the interrupt controller
driver; a separate patch will be submitted for it.
Rich Felker (2):
of: add J-Core timer bindings
clocksource: add J-Core timer/clocksource driver
.../devicetree/bindings/timer/jcore,pit.txt | 24 +++
drivers/clocksource/Kconfig | 10 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/jcore-pit.c | 231 +++++++++++++++++++++
include/linux/cpuhotplug.h | 1 +
5 files changed, 267 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt
create mode 100644 drivers/clocksource/jcore-pit.c
--
2.10.0
next reply other threads:[~2016-10-09 5:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 5:34 Rich Felker [this message]
[not found] ` <cover.1475990489.git.dalias-8zAoT0mYgF4@public.gmane.org>
2016-10-09 5:34 ` [PATCH v8 1/2] of: add J-Core timer bindings Rich Felker
2016-10-09 5:34 ` [PATCH v8 2/2] clocksource: add J-Core timer/clocksource driver Rich Felker
2016-10-11 18:18 ` Daniel Lezcano
2016-10-11 20:28 ` Rich Felker
2016-10-12 9:27 ` Daniel Lezcano
2016-10-12 17:02 ` Rich Felker
2016-10-12 21:31 ` Daniel Lezcano
2016-10-13 5:04 ` Rich Felker
2016-10-13 19:25 ` Rich Felker
[not found] ` <20161013192542.GW19318-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2016-10-13 19:48 ` Rich Felker
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=cover.1475990489.git.dalias@libc.org \
--to=dalias@libc.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paulmck@linux.vnet.ibm.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).