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: [PATCH v6] clk: mediatek: Export CPU mux clocks for CPU frequency control
Date: Mon, 1 Feb 2016 12:46:39 +0100	[thread overview]
Message-ID: <56AF459F.2050808@gmail.com> (raw)
In-Reply-To: <CAGS+omBWEVac_in-ZDurf4R5tje3hzJPyr5nsP2Z_v7F8sSCUg@mail.gmail.com>



On 26/01/16 11:23, Daniel Kurtz wrote:
> Hi Michael, Pi-Cheng,
>
> On Thu, Dec 17, 2015 at 1:06 AM, Michael Turquette
> <mturquette@baylibre.com> wrote:
>>
>> On 12/01, Pi-Cheng Chen wrote:
>>> On Mon, Nov 30, 2015 at 11:48 AM, Daniel Kurtz <djkurtz@chromium.org> wrote:
>>>> Hi Pi-Cheng and Michael,
>>>>
>>>> On Mon, Sep 14, 2015 at 7:27 PM, Pi-Cheng Chen <pi-cheng.chen@linaro.org> wrote:
>>>>> From: "pi-cheng.chen" <pi-cheng.chen@linaro.org>
>>>>>
>>>>> This patch adds CPU mux clocks which are used by Mediatek cpufreq driver
>>>>> for intermediate clock source switching.
>>>>
>>>> It looks like this patch was never picked up.
>>>> It is required for MT8173 cpufreq.
>>>>
>>>> What is the plan to get this one merged?
>>>
>>> Hi Dan,
>>> Mike is working on a new CCF feature called "coordinated clock rate changes"
>>> which would help to migrate mt8173-cpufreq driver to generic cpufreq-dt
>>> driver, and I am working with him to port MT8173 clock driver on the new
>>> feature. So I think that's why this patch was not picked since it will
>>> be migrated to new implementation once the new feature's ready.
>>>
>>> @Mike:
>>> Are you plannig to post those patches on the mailing list ?
>>> Or is it fine for you to take this first and then I will refine it for
>>> the new feature later?
>>
>> I plan to post those patches next week.
>
> Were these patches ever posted?
> Or should we consider going ahead and trying to merge this 4-month old
> MTK CPU mux clock patch into v4.5 before it is too late?
>

It's already too late for v4.5. The -rc are mostly bug fixes and new 
features get merged after the official v4.5 release. They will show up 
in v4.6-rc1

  reply	other threads:[~2016-02-01 11:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 11:27 [PATCH v6] clk: mediatek: Export CPU mux clocks for CPU frequency control Pi-Cheng Chen
2015-11-30  3:48 ` Daniel Kurtz
2015-12-01 15:09   ` Pi-Cheng Chen
2015-12-17  9:06     ` Michael Turquette
2016-01-26 10:23       ` Daniel Kurtz
2016-02-01 11:46         ` Matthias Brugger [this message]
2016-02-01 11:48           ` Daniel Kurtz
2016-02-15  3:28       ` Daniel Kurtz
2017-02-12  3:31         ` Daniel Kurtz

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=56AF459F.2050808@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).