From: Yicong Yang <yangyicong@huawei.com>
To: <mark.rutland@arm.com>, <maz@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <daniel.lezcano@linaro.org>, <tglx@linutronix.de>,
<jonathan.cameron@huawei.com>, <prime.zeng@huawei.com>,
<wanghuiqiang@huawei.com>, <wangwudi@hisilicon.com>,
<guohanjun@huawei.com>, <yangyicong@hisilicon.com>,
<linuxarm@huawei.com>
Subject: [RFC PATCH 0/3] Add HiSilicon system timer driver
Date: Tue, 10 Oct 2023 20:30:30 +0800 [thread overview]
Message-ID: <20231010123033.23258-1-yangyicong@huawei.com> (raw)
From: Yicong Yang <yangyicong@hisilicon.com>
HiSilicon system timer is a memory mapped platform timer compatible with
the arm's generic timer specification. The timer supports both SPI and
LPI interrupt and can be enumerated through ACPI DSDT table. Since the
timer is fully compatible with the spec, it can reuse most codes of the
arm_arch_timer driver. However since the arm_arch_timer driver only
supports GTDT and SPI interrupt, this series support the HiSilicon system
timer by:
- refactor some of the arm_arch_timer codes and export the function to
register a arch memory timer by other drivers
- retrieve the IO memory and interrupt resource through DSDT in a separate
driver, then setup and register the clockevent device reuse the arm_arch_timer
function
Using LPI for the timer is mentioned in BSA Spec section 3.8.1 (DEN0094C 1.0C).
Yicong Yang (3):
clocksource/drivers/arm_arch_timer: Split the function of
__arch_timer_setup()
clocksource/drivers/arm_arch_timer: Extend and export
arch_timer_mem_register()
clocksource/drivers: Add HiSilicon system timer driver
drivers/clocksource/Kconfig | 10 +++
drivers/clocksource/Makefile | 1 +
drivers/clocksource/arm_arch_timer.c | 123 +++++++++++++++------------
drivers/clocksource/timer-hisi-sys.c | 68 +++++++++++++++
include/clocksource/arm_arch_timer.h | 2 +
5 files changed, 148 insertions(+), 56 deletions(-)
create mode 100644 drivers/clocksource/timer-hisi-sys.c
--
2.24.0
next reply other threads:[~2023-10-10 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 12:30 Yicong Yang [this message]
2023-10-10 12:30 ` [RFC PATCH 1/3] clocksource/drivers/arm_arch_timer: Split the function of __arch_timer_setup() Yicong Yang
2023-10-10 12:30 ` [RFC PATCH 2/3] clocksource/drivers/arm_arch_timer: Extend and export arch_timer_mem_register() Yicong Yang
2023-10-10 12:30 ` [RFC PATCH 3/3] clocksource/drivers: Add HiSilicon system timer driver Yicong Yang
2023-10-10 15:43 ` [RFC PATCH 0/3] " Mark Rutland
2023-10-11 2:07 ` Yicong Yang
2023-10-10 16:36 ` Marc Zyngier
2023-10-11 2:10 ` Yicong Yang
2023-10-11 10:38 ` Mark Rutland
2023-10-11 13:10 ` Yicong Yang
2024-01-23 9:35 ` Yicong Yang
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=20231010123033.23258-1-yangyicong@huawei.com \
--to=yangyicong@huawei.com \
--cc=daniel.lezcano@linaro.org \
--cc=guohanjun@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=prime.zeng@huawei.com \
--cc=tglx@linutronix.de \
--cc=wanghuiqiang@huawei.com \
--cc=wangwudi@hisilicon.com \
--cc=yangyicong@hisilicon.com \
/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
all inboxes | Powered by JetHome®