From: Mark Rutland <mark.rutland@arm.com>
To: Youngmin Nam <youngmin.nam@samsung.com>
Cc: krzysztof.kozlowski@canonical.com, will@kernel.org,
daniel.lezcano@linaro.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, pullip.cho@samsung.com,
hoony.yu@samsung.com, hajun.sung@samsung.com,
myung-su.cha@samsung.com, kgene@kernel.org
Subject: Re: [PATCH v2 1/2] clocksource/drivers/exynos_mct_v2: introduce Exynos MCT version 2 driver for next Exynos SoC
Date: Tue, 2 Nov 2021 10:28:10 +0000 [thread overview]
Message-ID: <20211102102802.GA16545@C02TD0UTHF1T.local> (raw)
In-Reply-To: <20211102001122.27516-2-youngmin.nam@samsung.com>
On Tue, Nov 02, 2021 at 09:11:21AM +0900, Youngmin Nam wrote:
> Exynos MCT version 2 is composed of 1 FRC and 12 comparators.
> There are no global timer and local timer anymore.
> The 1 of 64bit FRC serves as "up-counter"(not "comparators").
> The 12 comaprators(not "counter") can be used as per-cpu event timer
> so that it can support upto 12 cores.
> And a RTC source can be used as backup clock source.
[...]
> +static int exynos_mct_starting_cpu(unsigned int cpu)
> +{
> + struct mct_clock_event_device *mevt = per_cpu_ptr(&percpu_mct_tick, cpu);
> + struct clock_event_device *evt = &mevt->evt;
> +
> + snprintf(mevt->name, sizeof(mevt->name), "mct_comp%d", cpu);
> +
> + evt->name = mevt->name;
> + evt->cpumask = cpumask_of(cpu);
> + evt->set_next_event = exynos_comp_set_next_event;
> + evt->set_state_periodic = mct_set_state_periodic;
> + evt->set_state_shutdown = mct_set_state_shutdown;
> + evt->set_state_oneshot = mct_set_state_shutdown;
> + evt->set_state_oneshot_stopped = mct_set_state_shutdown;
> + evt->tick_resume = mct_set_state_shutdown;
> + evt->features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT;
> + evt->rating = 500; /* use value higher than ARM arch timer */
Previously Will asked you to try CLOCK_EVT_FEAT_PERCPU here, and to set
the C3STOP flag on the arch timer via the DT when necessary, rather than
trying to override the arch timer like this:
https://lore.kernel.org/r/20211027073458.GA22231@willie-the-truck
There are a bunch of things that depend on the architected timer working
as a clocksource (e.g. vdso, kvm), and it *should* work as a lock
clockevent_device if configured correctly, and it's much more consistent
with *everyone else* to use the arhcitected timer by default.
Please try as Will suggested above, so that this works from day one.
Thanks,
Mark.
next prev parent reply other threads:[~2021-11-02 10:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211101234449epcas2p385cd5133ff8ed3a248649b4134bc0113@epcas2p3.samsung.com>
2021-11-02 0:11 ` [PATCH v2 0/2] Indroduce Exynos Multi Core Timer version 2 Youngmin Nam
[not found] ` <CGME20211101234500epcas2p2d0e5bc54615b635f6694bc1be4c89fb5@epcas2p2.samsung.com>
2021-11-02 0:11 ` [PATCH v2 1/2] clocksource/drivers/exynos_mct_v2: introduce Exynos MCT version 2 driver for next Exynos SoC Youngmin Nam
2021-11-02 10:28 ` Mark Rutland [this message]
2021-11-03 0:09 ` Youngmin Nam
2021-11-03 8:18 ` Krzysztof Kozlowski
2021-11-03 9:24 ` Youngmin Nam
2021-11-03 9:04 ` Krzysztof Kozlowski
2021-11-03 9:57 ` Youngmin Nam
2021-11-03 10:04 ` Mark Rutland
2021-11-04 0:21 ` Youngmin Nam
2021-11-04 9:44 ` Mark Rutland
[not found] ` <CGME20211105001912epcas2p30469b097f7c348f0a59251d03cd0075e@epcas2p3.samsung.com>
2021-11-05 0:46 ` Youngmin Nam
2021-11-05 9:31 ` Will Deacon
[not found] ` <CGME20211101234503epcas2p2502c113c1821ecb85faf959d059f26c6@epcas2p2.samsung.com>
2021-11-02 0:11 ` [PATCH v2 2/2] dt-bindings: timer: samsung,s5e99xx-mct: Document s5e99xx-mct bindings Youngmin Nam
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=20211102102802.GA16545@C02TD0UTHF1T.local \
--to=mark.rutland@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=hajun.sung@samsung.com \
--cc=hoony.yu@samsung.com \
--cc=kgene@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=myung-su.cha@samsung.com \
--cc=pullip.cho@samsung.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=youngmin.nam@samsung.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®