From: Joseph Lo <josephl@nvidia.com>
To: Jon Hunter <jonathanh@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: <linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH V5 2/7] clocksource: tegra: add Tegra210 timer support
Date: Fri, 1 Feb 2019 23:49:17 +0800 [thread overview]
Message-ID: <c33697d8-43a9-654b-503f-e60adbaf289f@nvidia.com> (raw)
In-Reply-To: <ab418999-a45c-bd9c-b9bd-5c382e86d26c@nvidia.com>
On 2/1/19 11:43 PM, Jon Hunter wrote:
>
>
> On 01/02/2019 14:39, Joseph Lo wrote:
>> On 2/1/19 8:44 PM, Jon Hunter wrote:
>>>
>>> On 01/02/2019 03:36, Joseph Lo wrote:
>>>> Add support for the Tegra210 timer that runs at oscillator clock
>>>> (TMR10-TMR13). We need these timers to work as clock event device and to
>>>> replace the ARMv8 architected timer due to it can't survive across the
>>>> power cycle of the CPU core or CPUPORESET signal. So it can't be a
>>>> wake-up
>>>> source when CPU suspends in power down state.
>>>>
>>>> Also convert the original driver to use timer-of API.
>>>
>>> It may have been nice to split this into 2 patches to make it easier to
>>> see what is going on but not a big deal.
>>>
>>>> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
>>>> Cc: Thomas Gleixner <tglx@linutronix.de>
>>>> Cc: linux-kernel@vger.kernel.org
>>>> Signed-off-by: Joseph Lo <josephl@nvidia.com>
>>>> Acked-by: Thierry Reding <treding@nvidia.com>
>>>> ---
snip.
>>>
>> This can't get the timer base address. I think you mean ...
>>
>> +#ifdef CONFIG_ARM
>> +#define TIMER_CPU0 0x50 /* TIMER3 */
>> +#else
>> +#define TIMER_CPU0 0x90 /* TIMER10 */
>> +#endif
>> +#define TIMER_BASE_FOR_CPU(cpu) (TIMER_CPU0 + (cpu) * 8)
>
> Ah I see.
>
>> This doesn't need.
>> +#define TIMER_FOR_CPU(cpu) (TIMER_CPU0 + cpu)
> How come? Don't you still need to know the timer index for a given CPU?
>
Doesn't need. TIMER_BASE_FOR_CPU is enough. Other use cases are well
handled by timer-of API. :)
Thanks,
Joseph
next prev parent reply other threads:[~2019-02-01 15:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190201033621.16814-1-josephl@nvidia.com>
2019-02-01 3:36 ` [PATCH V5 1/7] dt-bindings: timer: add Tegra210 timer Joseph Lo
2019-02-01 3:36 ` [PATCH V5 2/7] clocksource: tegra: add Tegra210 timer support Joseph Lo
2019-02-01 12:44 ` Jon Hunter
2019-02-01 14:39 ` Joseph Lo
2019-02-01 15:43 ` Jon Hunter
2019-02-01 15:49 ` Joseph Lo [this message]
2019-02-01 13:06 ` Dmitry Osipenko
2019-02-01 13:11 ` Dmitry Osipenko
2019-02-01 13:54 ` Jon Hunter
2019-02-01 14:13 ` Joseph Lo
2019-02-01 15:13 ` Dmitry Osipenko
2019-02-01 15:37 ` Joseph Lo
2019-02-01 18:08 ` Dmitry Osipenko
2019-02-01 23:53 ` Joseph Lo
2019-02-02 13:38 ` Dmitry Osipenko
2019-02-02 16:07 ` Joseph Lo
2019-02-02 13:30 ` Dmitry Osipenko
2019-02-02 16:04 ` Joseph Lo
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=c33697d8-43a9-654b-503f-e60adbaf289f@nvidia.com \
--to=josephl@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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).