[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4c28b51-ecd5-649b-e8fa-e5ce1bbb3139@arm.com>
Date: Wed, 23 May 2018 14:54:41 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Ilia Lin <ilialin@...eaurora.org>, vireshk@...nel.org, nm@...com,
sboyd@...nel.org, robh@...nel.org, mark.rutland@....com,
rjw@...ysocki.net, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Sudeep Holla <sudeep.holla@....com>
Subject: Re: [PATCH v11 0/2] Kryo CPU scaling driver
On 23/05/18 13:38, Ilia Lin wrote:
> [v11]
> * Addressed comment from Russel about device_node reference
> * Addressed comment from Sudeep about the late_initcall
> * Transformed init into probe to take care of deferals
>
> [v10]
> * Split the series into domains
> * Addressed comments from Viresh and Sudeep about logical CPU numbering.
>
> The qcom-cpufreq-kryo driver is aimed to support different SOC versions.
> The driver reads eFuse information and chooses the required OPP subset
> by passing the OPP supported-hw parameter.
>
> The series depends on the series from Viresh:
> https://patchwork.kernel.org/patch/10418139/
>
> The previous spin was here:
> https://patchwork.kernel.org/patch/10420809/
>
IIUC, this depends on "CPU scaling support for msm8996" [1] for
the functionality though the change is independent ?
--
Regards,
Sudeep
[1] https://www.spinics.net/lists/arm-kernel/msg654978.html
Powered by blists - more mailing lists