From: vijayakannan.ayyathurai@intel.com
To: daniel.lezcano@linaro.org, tglx@linutronix.de,
robh+dt@kernel.org, catalin.marinas@arm.com, will@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
andriy.shevchenko@linux.intel.com, mgross@linux.intel.com,
wan.ahmad.zainie.wan.mohamad@intel.com,
lakshmi.bai.raja.subramanian@intel.com, chen.yong.seow@intel.com,
vijayakannan.ayyathurai@intel.com
Subject: [PATCH v2 0/2] Add drivers for Intel Keem Bay SoC timer block
Date: Wed, 30 Dec 2020 14:25:25 +0800 [thread overview]
Message-ID: <cover.1609306622.git.vijayakannan.ayyathurai@intel.com> (raw)
From: Vijayakannan Ayyathurai <vijayakannan.ayyathurai@intel.com>
Hi,
This patch set adds the driver for Intel Keem Bay SoC timer block, which
contains 32-bit general purpose timers, a 64 bit free running counter.
Patch 1 holds the Device Tree binding documentation and
Patch 2 holds the Device Driver for clocksource and clockevent.
It was tested on the Keem Bay evaluation module board.
Thanks,
Vijay
Changes since v1:
- Add support for KEEMBAY_TIMER to get selected through Kconfig.platforms.
- Add CLOCK_EVT_FEAT_DYNIRQ as part of clockevent feature.
- Avoid overlapping reg regions across 2 device nodes.
- Simplify 2 device nodes as 1 because both are from same IP block.
- Adapt the driver code according to the new simplified devicetree.
Vijayakannan Ayyathurai (2):
dt-bindings: timer: Add bindings for Intel Keem Bay SoC timer
clocksource: Add Intel Keem Bay Timer Support
.../bindings/timer/intel,keembay-timer.yaml | 52 ++++
arch/arm64/Kconfig.platforms | 1 +
drivers/clocksource/Kconfig | 10 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-keembay.c | 225 ++++++++++++++++++
5 files changed, 289 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/intel,keembay-timer.yaml
create mode 100644 drivers/clocksource/timer-keembay.c
base-commit: 5c8fe583cce542aa0b84adc939ce85293de36e5e
prerequisite-patch-id: bbb340c3a34059ea6960e8b96f5ad3bf0b4ae7b0
prerequisite-patch-id: b71b548284a57a38ce96d9bb523eadfccabd6e02
--
2.17.1
next reply other threads:[~2020-12-30 6:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 6:25 vijayakannan.ayyathurai [this message]
2020-12-30 6:25 ` [PATCH v2 1/2] dt-bindings: timer: Add bindings for Intel Keem Bay SoC timer vijayakannan.ayyathurai
2020-12-31 15:34 ` Rob Herring
2021-01-01 16:12 ` Ayyathurai, Vijayakannan
2020-12-30 6:25 ` [PATCH v2 2/2] clocksource: Add Intel Keem Bay Timer Support vijayakannan.ayyathurai
2021-01-18 15:56 ` Daniel Lezcano
2021-01-19 2:56 ` Ayyathurai, Vijayakannan
2021-01-19 8:50 ` andriy.shevchenko
2021-01-20 19:18 ` Ayyathurai, Vijayakannan
2021-01-13 10:54 ` [PATCH v2 0/2] Add drivers for Intel Keem Bay SoC timer block Ayyathurai, Vijayakannan
2021-01-18 15:34 ` Daniel Lezcano
2021-01-19 1:55 ` Ayyathurai, Vijayakannan
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.1609306622.git.vijayakannan.ayyathurai@intel.com \
--to=vijayakannan.ayyathurai@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=chen.yong.seow@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lakshmi.bai.raja.subramanian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=wan.ahmad.zainie.wan.mohamad@intel.com \
--cc=will@kernel.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).