From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Date: Tue, 6 Feb 2018 09:57:29 +0530 From: Viresh Kumar To: Sricharan R Cc: robh+dt@kernel.org, mark.rutland@arm.com, mturquette@baylibre.com, sboyd@codeaurora.org, linux@armlinux.org.uk, andy.gross@linaro.org, david.brown@linaro.org, rjw@rjwysocki.net, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-pm@vger.kernel.org, robh@kernel.org Subject: Re: [PATCH v6 15/15] dt-bindings: cpufreq: Document operating-points-v2-krait-cpu Message-ID: <20180206042729.GH28462@vireshk-i7> References: <1517890108-8140-1-git-send-email-sricharan@codeaurora.org> <1517890108-8140-16-git-send-email-sricharan@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1517890108-8140-16-git-send-email-sricharan@codeaurora.org> List-ID: 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 > --- > .../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