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,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
wsd_upstream@mediatek.com
Subject: Re: [PATCH v10] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver
Date: Mon, 24 May 2021 14:48:45 +0530 [thread overview]
Message-ID: <20210524091845.wlikxun3x2qou7zs@vireshk-i7> (raw)
In-Reply-To: <1609222629-2979-1-git-send-email-hector.yuan@mediatek.com>
On 29-12-20, 14:17, 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 MT6779 DTS patchset[1] submitted by Hanks Chen.
>
> >From v8 to v9, there are three more modifications.
> 1. Based on patchset[2], align binding with scmi for performance domain.
> 2. Add the CPUFREQ fast switch function support and define DVFS latency.
> 3. Based on patchser[3], add energy model API parameter for mW.
Hi Hector,
You can refresh this series based on the patch from Sudeep:
https://lore.kernel.org/linux-devicetree/20210517155458.1016707-1-sudeep.holla@arm.com/
--
viresh
next prev parent reply other threads:[~2021-05-24 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 6:17 [PATCH v10] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Hector Yuan
2020-12-29 6:17 ` [PATCH v10 1/2] cpufreq: mediatek-hw: Add support for CPUFREQ HW Hector Yuan
2020-12-29 6:17 ` [PATCH v10 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW Hector Yuan
2021-01-11 20:23 ` Rob Herring
[not found] ` <49f4400f-c803-f044-4974-f4e8703876e7@gmail.com>
2021-03-12 11:57 ` [PATCH v10] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Hector Yuan
2021-05-24 9:18 ` Viresh Kumar [this message]
2021-05-28 7:27 ` 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=20210524091845.wlikxun3x2qou7zs@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=matthias.bgg@gmail.com \
--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).