[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191017023308.se5odhmg2hru4vji@vireshk-i7>
Date: Thu, 17 Oct 2019 08:03:08 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Dmitry Osipenko <digetx@...il.com>
Cc: Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Peter De Schrijver <pdeschrijver@...dia.com>,
Prashant Gaikwad <pgaikwad@...dia.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Rob Herring <robh+dt@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Peter Geis <pgwipeout@...il.com>,
Nicolas Chauvet <kwizart@...il.com>,
Marcel Ziswiler <marcel.ziswiler@...adex.com>,
linux-pm@...r.kernel.org, linux-tegra@...r.kernel.org,
devicetree@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 12/17] ARM: dts: tegra30: Add CPU Operating
Performance Points
On 16-10-19, 00:16, Dmitry Osipenko wrote:
> Operating Point are specified per HW version. The OPP voltages are kept
> in a separate DTSI file because some boards may not define CPU regulator
> in their device-tree if voltage scaling isn't necessary for them.
>
> Signed-off-by: Dmitry Osipenko <digetx@...il.com>
> ---
> .../boot/dts/tegra30-cpu-opp-microvolt.dtsi | 801 +++++++++++
> arch/arm/boot/dts/tegra30-cpu-opp.dtsi | 1202 +++++++++++++++++
> 2 files changed, 2003 insertions(+)
> create mode 100644 arch/arm/boot/dts/tegra30-cpu-opp-microvolt.dtsi
> create mode 100644 arch/arm/boot/dts/tegra30-cpu-opp.dtsi
Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
--
viresh
Powered by blists - more mailing lists