From: Sudeep Holla <sudeep.holla@arm.com>
To: Ilia Lin <ilialin@codeaurora.org>,
vireshk@kernel.org, nm@ti.com, sboyd@kernel.org, robh@kernel.org,
mark.rutland@arm.com, rjw@rjwysocki.net,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v11 0/2] Kryo CPU scaling driver
Date: Wed, 23 May 2018 14:54:41 +0100 [thread overview]
Message-ID: <b4c28b51-ecd5-649b-e8fa-e5ce1bbb3139@arm.com> (raw)
In-Reply-To: <1527079139-3558-1-git-send-email-ilialin@codeaurora.org>
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
next prev parent reply other threads:[~2018-05-23 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 12:38 [PATCH v11 0/2] Kryo CPU scaling driver Ilia Lin
2018-05-23 12:38 ` [PATCH v11 1/2] cpufreq: Add " Ilia Lin
2018-05-23 13:25 ` Sudeep Holla
2018-05-23 17:42 ` ilialin
2018-05-24 4:34 ` Viresh Kumar
2018-05-24 9:37 ` Sudeep Holla
2018-05-24 4:37 ` Viresh Kumar
2018-05-23 12:38 ` [PATCH v11 2/2] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu Ilia Lin
2018-05-23 13:54 ` Sudeep Holla [this message]
[not found] ` <f53d6035-d409-4535-9dd0-03baedc9b4a8@email.android.com>
2018-05-23 15:41 ` [PATCH v11 0/2] Kryo CPU scaling driver Sudeep Holla
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=b4c28b51-ecd5-649b-e8fa-e5ce1bbb3139@arm.com \
--to=sudeep.holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=ilialin@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=vireshk@kernel.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).