[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180206042729.GH28462@vireshk-i7>
Date: Tue, 6 Feb 2018 09:57:29 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Sricharan R <sricharan@...eaurora.org>
Cc: robh+dt@...nel.org, mark.rutland@....com, mturquette@...libre.com,
sboyd@...eaurora.org, linux@...linux.org.uk, andy.gross@...aro.org,
david.brown@...aro.org, rjw@...ysocki.net,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
linux-pm@...r.kernel.org, robh@...nel.org
Subject: Re: [PATCH v6 15/15] dt-bindings: cpufreq: Document
operating-points-v2-krait-cpu
On 06-02-18, 09:38, Sricharan R wrote:
> In Certain QCOM SoCs like ipq8064, apq8064, msm8960, msm8974
> that has KRAIT processors the voltage/current value of each OPP
> varies based on the silicon variant in use.
> operating-points-v2-krait-cpu specifies the phandle to nvmem efuse cells
> and the operating-points-v2 table for each opp. The qcom-cpufreq driver
> reads the efuse value from the SoC to provide the required information
> that is used to determine the voltage and current value for each OPP of
> operating-points-v2 table when it is parsed by the OPP framework.
>
> Signed-off-by: Sricharan R <sricharan@...eaurora.org>
> ---
> .../devicetree/bindings/cpufreq/krait-cpufreq.txt | 363 +++++++++++++++++++++
> 1 file changed, 363 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/cpufreq/krait-cpufreq.txt
You can add my Ack if Rob also finds everything to be fine here.
Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
--
viresh
Powered by blists - more mailing lists