linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@baylibre.com (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] clk: mediatek: Export CPU mux clocks for CPU frequency control
Date: Thu, 17 Dec 2015 01:06:28 -0800	[thread overview]
Message-ID: <20151217090628.GA317@quark.deferred.io> (raw)
In-Reply-To: <CALx668XVnhhLJWs7RBxvaX=SU=S9=wFVT9HMDP2edqiH4Jio4A@mail.gmail.com>

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.

Thanks,
Mike

> 
> Best Regards,
> Pi-Cheng
> 
> >
> > -Dan
> >
> >>
> >> Signed-off-by: Pi-Cheng Chen <pi-cheng.chen@linaro.org>
> >> ---
> >> Changes in v6:
> >> - Relace __clk_get_num_parents with clk_hw_get_num_parents to reflect
> >>   API change
> >>
> >> Changes in v5:
> >> - Replace __initdata with __initconst to fix compiling error
> >>
> >> Changes in v4:
> >> - Fix some minor issues for v3
> >> - Rebase to the patch that adds 13mhz clock for MT8173[1]
> >>
> >> Changes in v3:
> >> - Rebase to 4.2-rc1
> >> - Fix some issues of v2
> >>
> >> Changes in v2:
> >> - Remove use of .determine_rate callback
> >> ---
> >>  drivers/clk/mediatek/Makefile          |   2 +-
> >>  drivers/clk/mediatek/clk-cpumux.c      | 127 +++++++++++++++++++++++++++++++++
> >>  drivers/clk/mediatek/clk-cpumux.h      |  22 ++++++
> >>  drivers/clk/mediatek/clk-mt8173.c      |  23 ++++++
> >>  include/dt-bindings/clock/mt8173-clk.h |   4 +-
> >>  5 files changed, 176 insertions(+), 2 deletions(-)
> >>  create mode 100644 drivers/clk/mediatek/clk-cpumux.c
> >>  create mode 100644 drivers/clk/mediatek/clk-cpumux.h
> >
> > [snip]

  reply	other threads:[~2015-12-17  9:06 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 [this message]
2016-01-26 10:23       ` Daniel Kurtz
2016-02-01 11:46         ` Matthias Brugger
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=20151217090628.GA317@quark.deferred.io \
    --to=mturquette@baylibre.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).