From: Stanley Chu <stanley.chu@mediatek.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
devicetree@vger.kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v2 2/2] clocksource/drivers/mtk_systimer: Add support for Mediatek SoCs
Date: Wed, 27 Jun 2018 17:50:16 +0800 [thread overview]
Message-ID: <1530093016.17448.35.camel@mtkswgap22> (raw)
In-Reply-To: <2a40ec95-7352-f0c4-b394-d7b689de98ec@linaro.org>
On Wed, 2018-06-27 at 11:39 +0200, Daniel Lezcano wrote:
> On 27/06/2018 09:53, Stanley Chu wrote:
> > This patch adds a new clock event for the timer
> > found on the Mediatek SoCs.
> >
> > The Mediatek System Timer has several 32-bit timers.
> > Only one timer is used by this driver as a clock event
> > supporting oneshot events.
> >
> > The System Timer can be run with two clocks. A 13 MHz system
> > clock and the RTC clock running at 32 KHz. This implementation
> > uses the system clock with no clock source divider.
>
> Recent platforms have the arch_arm_timer and it will be always selected.
>
> What is the benefit of adding this timer ?
>
>
Hi Daniel,
To save power as much as possible, our platform enables
"arch_timer_c3stop" in arch_arm_timer, and thus another always-on timer
is required for tick-broadcasting. System Timer is introduced for above
purpose.
Thanks.
Stanley Chu
next prev parent reply other threads:[~2018-06-27 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 7:53 [PATCH v2 0/2] Add system timer driver for Mediatek SoCs Stanley Chu
[not found] ` <1530086039-3763-1-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-06-27 7:53 ` [PATCH v2 1/2] dt-bindings: Add mtk-systimer bindings Stanley Chu
2018-06-27 8:20 ` Daniel Lezcano
2018-06-28 10:24 ` Stanley Chu
2018-06-27 7:53 ` [PATCH v2 2/2] clocksource/drivers/mtk_systimer: Add support for Mediatek SoCs Stanley Chu
2018-06-27 9:39 ` Daniel Lezcano
2018-06-27 9:50 ` Stanley Chu [this message]
2018-06-27 9:59 ` Daniel Lezcano
2018-06-27 10:01 ` Daniel Lezcano
2018-06-28 10:32 ` Stanley Chu
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=1530093016.17448.35.camel@mtkswgap22 \
--to=stanley.chu@mediatek.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=wsd_upstream@mediatek.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).