From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] clocksource: Conexant CX92755 timers support
Date: Wed, 21 Jan 2015 08:36:27 +0200 [thread overview]
Message-ID: <cover.1421821466.git.baruch@tkos.co.il> (raw)
This short series adds support for the Conexant CX92755 SoC timers. This SoC is
part of the Conexant Digicolor series of SoCs.
v3:
* Split into a separate clocksource series
v2:
http://article.gmane.org/gmane.linux.kernel/1861850
http://article.gmane.org/gmane.linux.kernel/1861853
* Change the timer dt binding, so that the 'reg' property points to the
first "Agent Communication" register. This should improve the chance of
reusing this binding for other SoCs in this series.
* Add the CONTROL() and COUNT() macros to the timer driver to make the code
clearer.
* Move arch/arm Kconfig changes from the clocksource driver patch to the
base arch support patch to reduce dependency between them
v1:
http://article.gmane.org/gmane.linux.kernel/1855028
http://article.gmane.org/gmane.linux.kernel/1855025
Baruch Siach (2):
clocksource: devicetree: document Conexant Digicolor timer binding
clocksource: driver for Conexant Digicolor SoC timer
.../devicetree/bindings/timer/digicolor-timer.txt | 18 +++
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-digicolor.c | 164 +++++++++++++++++++++
3 files changed, 183 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/digicolor-timer.txt
create mode 100644 drivers/clocksource/timer-digicolor.c
--
2.1.4
next reply other threads:[~2015-01-21 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 6:36 Baruch Siach [this message]
2015-01-21 6:36 ` [PATCH v3 1/2] clocksource: devicetree: document Conexant Digicolor timer binding Baruch Siach
2015-01-22 12:23 ` Daniel Lezcano
2015-01-21 6:36 ` [PATCH v3 2/2] clocksource: driver for Conexant Digicolor SoC timer Baruch Siach
2015-01-22 12:54 ` Daniel Lezcano
2015-01-25 14:46 ` Baruch Siach
2015-01-25 15:03 ` Daniel Lezcano
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.1421821466.git.baruch@tkos.co.il \
--to=baruch@tkos.co.il \
--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).