From: Neil Armstrong <narmstrong@baylibre.com>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, daniel.lezcano@linaro.org,
tglx@linutronix.de
Cc: Neil Armstrong <narmstrong@baylibre.com>
Subject: [PATCH 0/2] clocksource: Add support for Oxford Semiconductor RPS Dual Timer
Date: Tue, 31 May 2016 11:49:56 +0200 [thread overview]
Message-ID: <1464688198-9655-1-git-send-email-narmstrong@baylibre.com> (raw)
Adds driver for the Oxford Semiconductor RPS Dual Timer as base of the OX810SE
clock tick event and sched clock source.
This driver was posted with the initial OX810SE platform patchset at :
http://lkml.kernel.org/r/1457005210-18485-5-git-send-email-narmstrong@baylibre.com
and
http://lkml.kernel.org/r/1457005210-18485-6-git-send-email-narmstrong@baylibre.com
But since the SP804 was very similar, I decided to adapt it for OX810SE usage.
For some reasons, the SP804 has a lot of legacy code for non-dt, non-multiarch
platforms and needs a complete rewrite.
For now, this adds a dedicated driver with the same bindings as intended for SP804.
Neil Armstrong (2):
clocksource: Add Oxford Semiconductor RPS Dual Timer
dt-bindings: clocksource: Add Add Oxford Semiconductor RPS Timer
bindings
.../devicetree/bindings/timer/oxsemi,rps-timer.txt | 17 ++
drivers/clocksource/Kconfig | 6 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-oxnas-rps.c | 273 +++++++++++++++++++++
4 files changed, 297 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/oxsemi,rps-timer.txt
create mode 100644 drivers/clocksource/timer-oxnas-rps.c
--
1.9.1
next reply other threads:[~2016-05-31 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 9:49 Neil Armstrong [this message]
2016-05-31 9:49 ` [PATCH 1/2] clocksource: Add Oxford Semiconductor RPS Dual Timer Neil Armstrong
2016-06-01 7:03 ` Thomas Gleixner
2016-06-01 7:58 ` Neil Armstrong
2016-05-31 9:49 ` [PATCH 2/2] dt-bindings: clocksource: Add Add Oxford Semiconductor RPS Timer bindings Neil Armstrong
2016-06-02 23:20 ` Rob Herring
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=1464688198-9655-1-git-send-email-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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).