From: Viresh Kumar <viresh.kumar@linaro.org>
To: Hector Yuan <hector.yuan@mediatek.com>
Cc: linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v7] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver
Date: Thu, 10 Sep 2020 10:33:41 +0530 [thread overview]
Message-ID: <20200910050341.pgyieq3q7ijitosn@vireshk-i7> (raw)
In-Reply-To: <1599712262-8819-1-git-send-email-hector.yuan@mediatek.com>
On 10-09-20, 12:31, Hector Yuan wrote:
> The CPUfreq HW present in some Mediatek chipsets offloads the steps necessary for changing the frequency of CPUs.
> The driver implements the cpufreq driver interface for this hardware engine.
>
> This patch depends on the MT6779 DTS patch submitted by Hanks Chen
> https://lkml.org/lkml/2020/8/4/1094
Thanks for hanging there. Looks good to me. I will apply it once Rob
Ack's the binding patch.
--
viresh
next prev parent reply other threads:[~2020-09-10 5:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 4:31 [PATCH v7] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Hector Yuan
2020-09-10 4:31 ` [PATCH v7 1/2] " Hector Yuan
2020-09-10 4:31 ` [PATCH v7 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW Hector Yuan
2020-09-21 2:23 ` Hector Yuan
2020-09-22 20:28 ` Rob Herring
2020-09-23 13:10 ` Hector Yuan
2020-09-24 2:36 ` Hector Yuan
2020-09-25 2:27 ` Hector Yuan
2020-09-25 6:15 ` Viresh Kumar
2020-09-25 7:25 ` Hector Yuan
2020-10-05 2:29 ` Hector Yuan
2020-09-10 5:03 ` Viresh Kumar [this message]
2020-09-10 5:30 ` [PATCH v7] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Hector Yuan
2020-09-10 5:34 ` Viresh Kumar
2020-09-16 11:39 ` Hector Yuan
2020-09-17 2:31 ` Hector Yuan
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=20200910050341.pgyieq3q7ijitosn@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hector.yuan@mediatek.com \
--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=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=wsd_upstream@mediatek.com \
/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).