From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>,
James Liao <jamesjj.liao@mediatek.com>,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org,
Sascha Hauer <kernel@pengutronix.de>,
Olof Johansson <olof@lixom.net>,
srv_heupstream@mediatek.com,
linux-arm-kernel@lists.infradead.org,
Daniel Kurtz <djkurtz@chromium.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: mediatek: enable MTK_TIMER
Date: Wed, 16 Sep 2015 10:21:31 +0800 [thread overview]
Message-ID: <1442370091.14347.10.camel@mtksdaap41> (raw)
In-Reply-To: <1442369095-1094-1-git-send-email-yingjoe.chen@mediatek.com>
On Wed, 2015-09-16 at 10:04 +0800, Yingjoe Chen wrote:
> Enable MTK_TIMER for MediaTek plaform, which will be used as
> schedule clock.
Sorry, sending this series too early without cover letter and removing
Change-Id. Here's the cover letter:
This is actually v3 of "add GPT timer support for mt8173" series. This
is based on v4.3-rc1 + clockevents-4.4[1] and James's mediatek-clk
tree[2].
Changes compare to previous version[3]:
- the first two mtk_timer related changes are removed because they are
replaced/accepted in clockevents tree.
- Remove 'add 13mhz clock for MT8173' because it is accepted in
mediatek-clk tree.
- Kconfig.platforms path change.
So we only have 2 patches left here.
Matthias, can you take these and help to remove the Change-Id?
Daniel Kurtz (1):
arm64: dts: mt8173: add timer node
Yingjoe Chen (1):
arm64: mediatek: enable MTK_TIMER
[1]
https://git.linaro.org/people/daniel.lezcano/linux.git clockevents/4.4
[2]
http://lists.infradead.org/pipermail/linux-mediatek/2015-August/002069.html
[3]
http://lists.infradead.org/pipermail/linux-mediatek/2015-July/001544.html
next prev parent reply other threads:[~2015-09-16 2:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 2:04 [PATCH 1/2] arm64: mediatek: enable MTK_TIMER Yingjoe Chen
2015-09-16 2:04 ` [PATCH 2/2] arm64: dts: mt8173: add timer node Yingjoe Chen
2015-09-17 13:51 ` Sudeep Holla
[not found] ` <55FAC570.8040307-5wv7dgnIgG8@public.gmane.org>
2015-09-17 14:56 ` Yingjoe Chen
2015-09-17 16:13 ` Sudeep Holla
2015-10-01 14:33 ` Yingjoe Chen
2015-10-01 15:32 ` Sudeep Holla
2015-10-02 14:00 ` Yingjoe Chen
2015-09-17 16:41 ` Mark Rutland
2015-10-01 14:50 ` Yingjoe Chen
2015-09-16 2:21 ` Yingjoe Chen [this message]
2015-09-27 14:00 ` [PATCH 1/2] arm64: mediatek: enable MTK_TIMER Matthias Brugger
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=1442370091.14347.10.camel@mtksdaap41 \
--to=yingjoe.chen@mediatek.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=jamesjj.liao@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=srv_heupstream@mediatek.com \
--cc=tglx@linutronix.de \
/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).