[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190726080417.ohsgedbtyxbxfyj7@vireshk-i7>
Date: Fri, 26 Jul 2019 13:34:17 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Niklas Cassel <niklas.cassel@...aro.org>
Cc: Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Stephen Boyd <sboyd@...nel.org>,
Andy Gross <agross@...nel.org>, Ilia Lin <ilia.lin@...nel.org>,
linux-arm-msm@...r.kernel.org, jorge.ramirez-ortiz@...aro.org,
bjorn.andersson@...aro.org, ulf.hansson@...aro.org,
Sricharan R <sricharan@...eaurora.org>,
Rob Herring <robh@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 02/14] dt-bindings: cpufreq: Re-organise kryo cpufreq
to use it for other nvmem based qcom socs
$subject of this and few more binding patches updated to:
"dt-bindings: opp: XXX"
On 25-07-19, 12:41, Niklas Cassel wrote:
> From: Sricharan R <sricharan@...eaurora.org>
>
> The kryo cpufreq driver reads the nvmem cell and uses that data to
> populate the opps. There are other qcom cpufreq socs like krait which
> does similar thing. Except for the interpretation of the read data,
> rest of the driver is same for both the cases. So pull the common things
> out for reuse.
>
> Signed-off-by: Sricharan R <sricharan@...eaurora.org>
> [niklas.cassel@...aro.org: split dt-binding into a separate patch and
> do not rename the compatible string.]
> Signed-off-by: Niklas Cassel <niklas.cassel@...aro.org>
> Reviewed-by: Ilia Lin <ilia.lin@...nel.org>
> Reviewed-by: Rob Herring <robh@...nel.org>
> ---
> Changes since V1:
> -Picked up tags.
--
viresh
Powered by blists - more mailing lists