From: Eddie Huang <eddie.huang@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mediatek@lists.infradead.org,
Pi-Cheng Chen <pi-cheng.chen@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND PATCH 0/3 v6] Add Mediatek MT8173 cpufreq driver
Date: Thu, 21 Apr 2016 19:37:58 +0800 [thread overview]
Message-ID: <1461238678.20801.11.camel@mtksdaap41> (raw)
In-Reply-To: <5718B244.3020201@gmail.com>
Hi Matthias,
On Thu, 2016-04-21 at 12:58 +0200, Matthias Brugger wrote:
>
> On 21/04/16 12:26, Matthias Brugger wrote:
> >
> >
> > On 02/09/15 19:23, Matthias Brugger wrote:
> >>
> >>
> >> On 02/09/15 08:45, Daniel Kurtz wrote:
> >>> Matthias,
> >>>
> >>> On Fri, Aug 28, 2015 at 10:06 PM, Rafael J. Wysocki
> >>> <rjw@rjwysocki.net> wrote:
> >>>> On Wednesday, August 26, 2015 02:53:39 PM Pi-Cheng Chen wrote:
> >>>>> On Wed, Aug 26, 2015 at 10:16 AM, Viresh Kumar
> >>>>> <viresh.kumar@linaro.org> wrote:
> >>>>>> On 26-08-15, 09:25, Pi-Cheng Chen wrote:
> >>>>>>> The [3/3] is based on Mediatek SoC maintainer tree[1] and the
> >>>>>>> patch which
> >>>>>>> introduce a new clock type[2] consumed by MT8173 cpufreq driver.
> >>>>>>> So it will
> >>>>>>> cause some conflicts if it goes through your tree. I am not sure
> >>>>>>> how this
> >>>>>>> should be handled, but should it be merged through Mediatek SoC
> >>>>>>> maintainer
> >>>>>>> tree?
> >>>>>>
> >>>>>> Just get that applied to MTK tree, it doesn't have any dependency on
> >>>>>> rest of the patches for build/boot. The only thing is that cpufreq
> >>>>>> wouldn't work and it will work as soon as Rafael's and MTK's trees
> >>>>>> are
> >>>>>> merged by Linus.
> >>>>>
> >>>>> Thanks for your explanation.
> >>>>>
> >>>>> @Rafael, Would you please apply [1,2] to your tree?
> >>>>
> >>>> Applied, thanks!
> >>>
> >>> Can you please apply [3] from this set to your dts tree?
> >>>
> >>
> >> I will as soon as v4.3-rc1 shows up.
> >
> > I somehow forgot this patch. Sorry for that.
> > Applied for v4.6-next/dts64 right now.
> >
>
> I just realized that CLK_INFRA_CA53SEL and CLK_APMIXED_MAINPLL are not
> part of the clk driver.
>
> Pi-Cheng, can you check if they got renamed in the meanwhile? Or do we
> need some clock driver patches that enable this clocks for the series?
>
Thanks your notice. Unfortunately, we still have no chance let patch
with these two clock merged. The last version is [1]. This clock patch
will block cpufreq dts [2] and dynamic power dts [3]. Clock maintainer
is working on new architecture [4], hopefully we can send new clock
patch soon. After that, we will send new cpufreq and dynamic power dts.
So please ignore [2] [3] at this moment.
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-September/369737.html
[2] https://lkml.org/lkml/2015/7/9/206
[3]
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-April/423899.html
[4]
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-March/418796.html
Eddie
Thanks
prev parent reply other threads:[~2016-04-21 11:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 9:24 [RESEND PATCH 0/3 v6] Add Mediatek MT8173 cpufreq driver Pi-Cheng Chen
2015-08-17 9:24 ` [RESEND PATCH 1/3 v6] dt-bindings: mediatek: Add MT8173 CPU DVFS clock bindings Pi-Cheng Chen
2015-08-17 9:24 ` [RESEND PATCH 2/3 v6] cpufreq: mediatek: Add MT8173 cpufreq driver Pi-Cheng Chen
[not found] ` <1439803465-19683-3-git-send-email-pi-cheng.chen-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-18 10:09 ` Bartlomiej Zolnierkiewicz
2015-08-18 10:24 ` Viresh Kumar
2015-08-19 2:05 ` [PATCH v7 2/3] " Pi-Cheng Chen
[not found] ` <1439949906-22177-1-git-send-email-pi-cheng.chen-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-19 5:41 ` Viresh Kumar
[not found] ` <1439803465-19683-1-git-send-email-pi-cheng.chen-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-17 9:24 ` [RESEND PATCH 3/3 v6] arm64: dts: mt8173: mt8173-evb: Add mt8173 cpufreq driver support Pi-Cheng Chen
2015-08-25 2:10 ` [RESEND PATCH 0/3 v6] Add Mediatek MT8173 cpufreq driver Pi-Cheng Chen
2015-08-25 23:01 ` Rafael J. Wysocki
2015-08-26 1:25 ` Pi-Cheng Chen
2015-08-26 2:16 ` Viresh Kumar
2015-08-26 6:53 ` Pi-Cheng Chen
2015-08-28 14:06 ` Rafael J. Wysocki
2015-09-02 6:45 ` Daniel Kurtz
2015-09-02 17:23 ` Matthias Brugger
2016-04-21 10:26 ` Matthias Brugger
2016-04-21 10:58 ` Matthias Brugger
2016-04-21 11:37 ` Eddie Huang [this message]
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=1461238678.20801.11.camel@mtksdaap41 \
--to=eddie.huang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=pi-cheng.chen@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
/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).