From: Dmitry Osipenko <digetx@gmail.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Joseph Lo <josephl@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/10] NVIDIA Tegra clocksource driver improvements
Date: Tue, 4 Jun 2019 18:01:07 +0300 [thread overview]
Message-ID: <93d3f559-d42a-9a3b-50b5-b91471261c34@gmail.com> (raw)
In-Reply-To: <20190604133355.GE29894@pdeschrijver-desktop.Nvidia.com>
04.06.2019 16:33, Peter De Schrijver пишет:
> On Mon, Jun 03, 2019 at 09:59:38PM +0300, Dmitry Osipenko wrote:
>> 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 where
>> appropriate, the newer Tegra210 is getting support for microsecond
>> clocksource and the driver's code is getting much cleaner.
>>
>> The series was extensively tested on Tegra20 and Tegra30.
>>
>> Changelog:
>>
>> v4: In the comment to v3 Peter De Schrijver pointed out that arch-timer
>> isn't affected by DVFS changes and thus it is preferred over tegra-timer
>> on [T114, T210). Added new patch to address that: "Lower clocksource
>> rating for some Tegra's".
>>
>> Daniel Lezcano suggested that it will be worthwhile to rename driver's
>> source file as driver now covers more SoC generations than it initially
>> did. Hence the new "Rename timer-tegra20.c to timer-tegra.c" patch.
>>
>> v3: Fixed compilation on ARM64. Turned out that it doesn't have the
>> delay-timer, thanks to Nicolas Chauvet for the report.
>>
>> Added new "Support COMPILE_TEST universally" patch for better
>> compile-test coverage.
>>
>> v2: Rebased on recent linux-next. Now all of #ifdef's are removed from the
>> code due to the recent patch that generalized persistent clocksource.
>>
>> Couple other minor cosmetic changes.
>
> Series Acked-By: Peter De Schrijver <pdeschrijver@nvidia.com>
>
Thanks!
prev parent reply other threads:[~2019-06-04 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 18:59 [PATCH v4 00/10] NVIDIA Tegra clocksource driver improvements Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 01/10] clocksource/drivers/tegra: Support per-CPU timers on all Tegra's Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 02/10] clocksource/drivers/tegra: Unify timer code Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 03/10] clocksource/drivers/tegra: Reset hardware state on init Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 04/10] clocksource/drivers/tegra: Replace readl/writel with relaxed versions Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 05/10] clocksource/drivers/tegra: Release all IRQ's on request_irq() error Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 06/10] clocksource/drivers/tegra: Minor code clean up Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 07/10] clocksource/drivers/tegra: Use SPDX identifier Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 08/10] clocksource/drivers/tegra: Support COMPILE_TEST universally Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 09/10] clocksource/drivers/tegra: Lower clocksource rating for some Tegra's Dmitry Osipenko
2019-06-03 18:59 ` [PATCH v4 10/10] clocksource/drivers/tegra: Rename timer-tegra20.c to timer-tegra.c Dmitry Osipenko
2019-06-04 13:33 ` [PATCH v4 00/10] NVIDIA Tegra clocksource driver improvements Peter De Schrijver
2019-06-04 15:01 ` Dmitry Osipenko [this message]
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=93d3f559-d42a-9a3b-50b5-b91471261c34@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=pdeschrijver@nvidia.com \
--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).