[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190410032608.fqxahvys6rysvayy@vireshk-i7>
Date: Wed, 10 Apr 2019 08:56:08 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Yangtao Li <tiny.windzz@...il.com>
Cc: vireshk@...nel.org, nm@...com, sboyd@...nel.org,
robh+dt@...nel.org, mark.rutland@....com,
maxime.ripard@...tlin.com, wens@...e.org, rjw@...ysocki.net,
davem@...emloft.net, mchehab+samsung@...nel.org,
gregkh@...uxfoundation.org, nicolas.ferre@...rochip.com,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: cpufreq: Document
operating-points-v2-sunxi-cpu
On 09-04-19, 13:25, Yangtao Li wrote:
> Allwinner Process Voltage Scaling Tables defines the voltage and
> frequency value based on the speedbin blown in the efuse combination.
> The sunxi-cpufreq-nvmem driver reads the efuse value from the SoC to
> provide the OPP framework with required information.
> This is used to determine the voltage and frequency value for each
> OPP of operating-points-v2 table when it is parsed by the OPP framework.
>
> The "operating-points-v2-sunxi-cpu" DT extends the "operating-points-v2"
> with following parameters:
> - nvmem-cells (NVMEM area containig the speedbin information)
> - opp-microvolt-<name>: voltage in micro Volts.
> At runtime, the platform can pick a <name> and matching
> opp-microvolt-<name> property
>
> Signed-off-by: Yangtao Li <tiny.windzz@...il.com>
> ---
> .../bindings/opp/sunxi-nvmem-cpufreq.txt | 166 ++++++++++++++++++
> 1 file changed, 166 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/opp/sunxi-nvmem-cpufreq.txt
LGTM.
--
viresh
Powered by blists - more mailing lists