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: Add system timer driver for Mediatek SoCs
Date: Mon, 25 Jun 2018 17:07:11 +0800 [thread overview]
Message-ID: <1529917631.17448.22.camel@mtkswgap22> (raw)
In-Reply-To: <dd36b094-b11c-e6ef-a0fc-b039785e74f2@linaro.org>
On Mon, 2018-06-25 at 09:34 +0200, Daniel Lezcano wrote:
> On 25/06/2018 09:09, Stanley Chu wrote:
> > This patch adds a new driver for system timer on the Mediatek SoCs.
>
> Please elaborate why we need yet another timer.
>
> Is this timer present on all Mediatek platform ? Does it always co-exist
> with the existing one ?
>
>
>
>
Hi Daniel,
This new "system timer" only exists on recent Mediatek platforms,
for example, MT6765. We will upstream driver first, and then update
device tree on MT6765 later.
System timer is designed and optimized as a SoC timer for
tick-broadcasting. Besides timer IP has simpler register manipulation
and friendly low-power design.
There is no plan to remove existed "General Purpose Timer" now.
Thanks.
Stanley Chu
next prev parent reply other threads:[~2018-06-25 9:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 7:09 Add system timer driver for Mediatek SoCs Stanley Chu
2018-06-25 7:10 ` [PATCH 1/2] dt-bindings: Add mtk-systimer bindings Stanley Chu
2018-06-25 21:53 ` Daniel Lezcano
2018-06-26 6:36 ` Stanley Chu
2018-06-25 7:10 ` [PATCH 2/2] clocksource/drivers/mtk_systimer: Add support for Mediatek SoCs Stanley Chu
2018-06-26 7:41 ` Daniel Lezcano
2018-06-26 9:52 ` Stanley Chu
2018-06-25 7:34 ` Add system timer driver " Daniel Lezcano
2018-06-25 9:07 ` Stanley Chu [this message]
2018-06-26 7:31 ` Daniel Lezcano
2018-06-26 8:03 ` 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=1529917631.17448.22.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).