linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 0/3 v6] Add Mediatek MT8173 cpufreq driver
Date: Thu, 21 Apr 2016 12:58:12 +0200	[thread overview]
Message-ID: <5718B244.3020201@gmail.com> (raw)
In-Reply-To: <5718AAF0.3010606@gmail.com>



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?

Regards,
Matthias

  reply	other threads:[~2016-04-21 10:58 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
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
2015-08-19  5:41         ` Viresh Kumar
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 [this message]
2016-04-21 11:37                     ` Eddie Huang

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=5718B244.3020201@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).