From: Dmitry Osipenko <email@example.com> To: Thierry Reding <firstname.lastname@example.org> Cc: Daniel Lezcano <email@example.com>, Thomas Gleixner <firstname.lastname@example.org>, Alessandro Zummo <email@example.com>, Alexandre Belloni <firstname.lastname@example.org>, Jonathan Hunter <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH 1/2] clocksource: tegra: Use rating when registering clock source Date: Fri, 14 Jun 2019 17:06:48 +0300 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> 14.06.2019 17:02, Dmitry Osipenko пишет: > 14.06.2019 16:53, Thierry Reding пишет: >> On Fri, Jun 14, 2019 at 04:29:17PM +0300, Dmitry Osipenko wrote: >>> 14.06.2019 16:22, Thierry Reding пишет: >>>> On Fri, Jun 14, 2019 at 03:24:07PM +0300, Dmitry Osipenko wrote: >>>>> 14.06.2019 13:47, Thierry Reding пишет: >>>>>> From: Thierry Reding <email@example.com> >>>>>> >>>>>> The rating is parameterized depending on SoC generation to make sure it >>>>>> takes precedence on implementations where the architected timer can't be >>>>>> used. This rating is already used for the clock event device. Use the >>>>>> same rating for the clock source to be consistent. >>>>>> >>>>>> Signed-off-by: Thierry Reding <firstname.lastname@example.org> >>>>>> --- >>>>>> drivers/clocksource/timer-tegra.c | 2 +- >>>>>> 1 file changed, 1 insertion(+), 1 deletion(-) >>>>>> >>>>>> diff --git a/drivers/clocksource/timer-tegra.c b/drivers/clocksource/timer-tegra.c >>>>>> index f6a8eb0d7322..e6608141cccb 100644 >>>>>> --- a/drivers/clocksource/timer-tegra.c >>>>>> +++ b/drivers/clocksource/timer-tegra.c >>>>>> @@ -318,7 +318,7 @@ static int __init tegra_init_timer(struct device_node *np, bool tegra20, >>>>>> sched_clock_register(tegra_read_sched_clock, 32, TIMER_1MHz); >>>>>> >>>>>> ret = clocksource_mmio_init(timer_reg_base + TIMERUS_CNTR_1US, >>>>>> - "timer_us", TIMER_1MHz, 300, 32, >>>>>> + "timer_us", TIMER_1MHz, rating, 32, >>>>>> clocksource_mmio_readl_up); >>>>>> if (ret) >>>>>> pr_err("failed to register clocksource: %d\n", ret); >>>>>> >>>>> >>>>> Looks good. Although, could you please clarify whether arch-timer stops on T210 when CPU >>>>> enters deepest (powerdown) idle state? I'm starting to lose track a bit already. Because >>>>> if arch-timer stops in the deepest idle state, then it's a bit odd that Joseph didn't add >>>>> the clocksource for T210 in the first place and v5.1 probably shouldn't work well because >>>>> of that already. >>>> >>>> Yes, the architected timer doesn't work across an SC7 (which is what the >>>> deepest idle state is called on Tegra210) transition, hence why we can't >>>> use it as a suspend clocksource. I actually sent out a patch to do that, >>>> earlier. >>>> >>>> And yes, it's entirely possible that v5.1 doesn't work in this regard, >>>> but we're not noticing that because we don't have suspend/resume support >>>> for Tegra210 anyway. There are a couple of missing pieces that we need >>>> in order to make it work. >>>> >>>> This change in particular is only going to affect the CPU idle state >>>> (CC7). Since the architected timer doesn't survive that either, we need >>>> the Tegra timer to be preferred over the architected timer for normal >>>> operation. >>>> >>>> All of these issues go away on Tegra186 and later, where the architected >>>> timer is in an always-on partition and has a PLL that remains on during >>>> SC7 (and CC7). >>> >>> Thank you very much for the clarification. But then what about the >>> sched_clock? I suppose sched_clock will suffer on T210 as well and it's >>> a bit trickier case because apparently arch-timer always wins since it >>> has a higher precision. I guess the best solution will be to just bail >>> out from arch-timer's driver probe in a case of T210. >>> >>> if (of_machine_is_compatible("nvidia,tegra210")) >>> return 0. >> >> I don't think there's any issue with the scheduler clock on Tegra210. >> Before the CPU can be turned off, all tasks scheduled on that CPU have >> to be migrated to another CPU, right? Conversely, before any tasks can >> be scheduled on a CPU that CPU needs to be brought online, at which >> point the architected timer should work fine again. > > Is SC7 a CPU-idle state that cpuidle driver may enter or it's a > system-wide suspend state? It's still not clear to me. > Ah, looks like I see now. So CC7 (CPU idle state) also affects the arch-timer (like SC7) and hence scheduler clock will be stopped while it shouldn't, which doesn't sound good.
next prev parent reply index Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-14 10:47 Thierry Reding 2019-06-14 10:47 ` [PATCH 2/2] rtc: tegra: Implement suspend " Thierry Reding 2019-06-14 12:01 ` Dmitry Osipenko 2019-06-14 13:41 ` Thierry Reding 2019-06-14 13:49 ` Dmitry Osipenko 2019-06-14 14:14 ` Thierry Reding 2019-06-14 16:41 ` Dmitry Osipenko 2019-06-17 10:20 ` Thierry Reding 2019-06-17 13:29 ` Dmitry Osipenko 2019-06-14 12:35 ` Dmitry Osipenko 2019-06-14 13:42 ` Thierry Reding 2019-06-14 12:24 ` [PATCH 1/2] clocksource: tegra: Use rating when registering " Dmitry Osipenko 2019-06-14 13:22 ` Thierry Reding 2019-06-14 13:29 ` Dmitry Osipenko 2019-06-14 13:53 ` Thierry Reding 2019-06-14 14:02 ` Dmitry Osipenko 2019-06-14 14:06 ` Dmitry Osipenko [this message] 2019-06-14 15:37 ` Thierry Reding 2019-06-14 17:00 ` Dmitry Osipenko 2019-06-17 10:52 ` Thierry Reding 2019-06-14 14:55 ` Thierry Reding
Reply instructions: You may reply publically 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Linux-RTC Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-rtc/0 linux-rtc/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-rtc linux-rtc/ https://lore.kernel.org/linux-rtc \ firstname.lastname@example.org public-inbox-index linux-rtc Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-rtc AGPL code for this site: git clone https://public-inbox.org/public-inbox.git