Re: [PATCH v1 11/17] ARM: dts: tegra20: Add CPU Operating Performance Points

2019-10-16 Thread Viresh Kumar
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, like for example > in a case of

Re: [PATCH v1 11/17] ARM: dts: tegra20: Add CPU Operating Performance Points

2019-10-16 Thread Viresh Kumar
On 16-10-19, 16:21, Dmitry Osipenko wrote: > 16.10.2019 08:23, Viresh Kumar пишет: > > 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

Re: [PATCH v1 11/17] ARM: dts: tegra20: Add CPU Operating Performance Points

2019-10-16 Thread Dmitry Osipenko
16.10.2019 08:23, Viresh Kumar пишет: > 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, like

Re: [PATCH v1 11/17] ARM: dts: tegra20: Add CPU Operating Performance Points

2019-10-15 Thread Viresh Kumar
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, like for example > in a case of

[PATCH v1 11/17] ARM: dts: tegra20: Add CPU Operating Performance Points

2019-10-15 Thread Dmitry Osipenko
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, like for example in a case of tegra20-trimslice which is outlet-powered device. Signed-off-by: