From: Dmitry Osipenko <digetx@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Joseph Lo <josephl@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/7] NVIDIA Tegra clocksource improvements and clean up
Date: Thu, 25 Apr 2019 02:14:37 +0300 [thread overview]
Message-ID: <20190424231444.20876-1-digetx@gmail.com> (raw)
Hello,
This series primarily unifies the driver code across all Tegra SoC
generations. In a result the clocksources are allocated per-CPU on
older Tegra's and have a higher rating than the arch-timer, the newer
Tegra210 is getting support for microsecond clocksource and delay-timer
and the driver's code is getting much cleaner. Note that arch-timer usage
is discouraged on all Tegra's due to the time jitter caused by the CPU
frequency scaling.
Dmitry Osipenko (7):
clocksource/drivers/tegra: Support per-CPU timers on all Tegra's
clocksource/drivers/tegra: Unify timer code
clocksource/drivers/tegra: Reset hardware state on init
clocksource/drivers/tegra: Replace readl/writel with relaxed versions
clocksource/drivers/tegra: Release all IRQ's on request_irq() error
clocksource/drivers/tegra: Minor code clean up
clocksource/drivers/tegra: Use SPDX identifier
drivers/clocksource/timer-tegra20.c | 287 +++++++++++++---------------
1 file changed, 136 insertions(+), 151 deletions(-)
--
2.21.0
next reply other threads:[~2019-04-24 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 23:14 Dmitry Osipenko [this message]
2019-04-24 23:14 ` [PATCH v1 1/7] clocksource/drivers/tegra: Support per-CPU timers on all Tegra's Dmitry Osipenko
2019-04-24 23:14 ` [PATCH v1 2/7] clocksource/drivers/tegra: Unify timer code Dmitry Osipenko
2019-04-24 23:14 ` [PATCH v1 3/7] clocksource/drivers/tegra: Reset hardware state on init Dmitry Osipenko
2019-04-24 23:14 ` [PATCH v1 4/7] clocksource/drivers/tegra: Replace readl/writel with relaxed versions Dmitry Osipenko
2019-04-24 23:14 ` [PATCH v1 5/7] clocksource/drivers/tegra: Release all IRQ's on request_irq() error Dmitry Osipenko
2019-04-24 23:14 ` [PATCH v1 6/7] clocksource/drivers/tegra: Minor code clean up Dmitry Osipenko
2019-04-24 23:14 ` [PATCH v1 7/7] clocksource/drivers/tegra: Use SPDX identifier Dmitry Osipenko
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=20190424231444.20876-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=josephl@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).