From: Claudiu Beznea <claudiu.beznea@microchip.com>
To: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<ludovic.desroches@microchip.com>, <daniel.lezcano@linaro.org>,
<tglx@linutronix.de>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: [PATCH v2 0/2] add Microchip PIT64B timer
Date: Mon, 4 Nov 2019 17:10:02 +0200 [thread overview]
Message-ID: <1572880204-4514-1-git-send-email-claudiu.beznea@microchip.com> (raw)
Hi,
This series adds driver for Microchip PIT64B timer.
Timer could be used in continuous or oneshot mode. It has 2x32 bit registers
to emulate a 64 bit timer. The timer's period could be configured via LSB_PR
and MSB_PR registers. The current timer's value could be checked via TLSB and
TMSB registers. When (TMSB << 32) | TLSB value reach the (MSB_PR << 32) | LSB_PR
interrupt is raised. If in contiuous mode the TLSB and TMSB resets and restart
counting.
This drivers uses PIT64B capabilities for clocksource and clockevent.
The first requested PIT64B timer is used for clockevent. The second one is used
for clocksource. Individual PIT64B hardware resources were used for clocksource
and clockevent to be able to support high resolution timers with this PIT64B
implementation.
Thank you,
Claudiu Beznea
Changes in v2:
- remove clock-frequency DT binding and hardcoded it in the driver
- initialize best_pres variable in mchp_pit64b_pres_prepare()
- remove MCHP_PIT64B_DEF_FREQ
- get rid of patches 3-5 from v1 [1] since there is no entry in MAINTAINERS file
for this entry. It was removed in commit
44015a8181a5 ("MAINTAINERS: at91: remove the TC entry")
[1] https://lore.kernel.org/lkml/1552580772-8499-1-git-send-email-claudiu.beznea@microchip.com/
Claudiu Beznea (2):
dt-bindings: arm: atmel: add bindings for PIT64B
clocksource/drivers/timer-microchip-pit64b: add Microchip PIT64B
support
.../devicetree/bindings/arm/atmel-sysregs.txt | 6 +
drivers/clocksource/Kconfig | 6 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-microchip-pit64b.c | 462 +++++++++++++++++++++
4 files changed, 475 insertions(+)
create mode 100644 drivers/clocksource/timer-microchip-pit64b.c
--
2.7.4
next reply other threads:[~2019-11-04 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 15:10 Claudiu Beznea [this message]
2019-11-04 15:10 ` [PATCH v2 1/2] dt-bindings: arm: atmel: add bindings for PIT64B Claudiu Beznea
2019-11-05 18:41 ` Rob Herring
2019-11-04 15:10 ` [PATCH v2 2/2] clocksource/drivers/timer-microchip-pit64b: add Microchip PIT64B support Claudiu Beznea
2019-11-04 19:05 ` Thomas Gleixner
2019-11-11 7:30 ` Claudiu.Beznea
2019-11-13 11:12 ` Claudiu.Beznea
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=1572880204-4514-1-git-send-email-claudiu.beznea@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@microchip.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).