Re: [PATCH RE-SEND] clk: tegra: Don't enable already enabled PLLs

2019-04-14 Thread Dmitry Osipenko
04.03.2019 16:42, Dmitry Osipenko пишет: > 04.03.2019 11:18, Peter De Schrijver пишет: >> On Wed, Feb 27, 2019 at 06:15:04PM +0300, Dmitry Osipenko wrote: >>> 24.02.2019 18:32, Dmitry Osipenko пишет: Initially Common Clock Framework isn't aware of the clock-enable status, this results in

Re: [PATCH RE-SEND] clk: tegra: Don't enable already enabled PLLs

2019-03-04 Thread Dmitry Osipenko
04.03.2019 11:18, Peter De Schrijver пишет: > On Wed, Feb 27, 2019 at 06:15:04PM +0300, Dmitry Osipenko wrote: >> 24.02.2019 18:32, Dmitry Osipenko пишет: >>> Initially Common Clock Framework isn't aware of the clock-enable status, >>> this results in enabling of clocks that were enabled by bootloa

Re: [PATCH RE-SEND] clk: tegra: Don't enable already enabled PLLs

2019-03-04 Thread Peter De Schrijver
On Wed, Feb 27, 2019 at 06:15:04PM +0300, Dmitry Osipenko wrote: > 24.02.2019 18:32, Dmitry Osipenko пишет: > > Initially Common Clock Framework isn't aware of the clock-enable status, > > this results in enabling of clocks that were enabled by bootloader. This > > is not a big deal for a regular c

Re: [PATCH RE-SEND] clk: tegra: Don't enable already enabled PLLs

2019-02-27 Thread Dmitry Osipenko
24.02.2019 18:32, Dmitry Osipenko пишет: > Initially Common Clock Framework isn't aware of the clock-enable status, > this results in enabling of clocks that were enabled by bootloader. This > is not a big deal for a regular clock-gates, but for PLL's it may have > some unpleasant consequences. Thu

[PATCH RE-SEND] clk: tegra: Don't enable already enabled PLLs

2019-02-24 Thread Dmitry Osipenko
Initially Common Clock Framework isn't aware of the clock-enable status, this results in enabling of clocks that were enabled by bootloader. This is not a big deal for a regular clock-gates, but for PLL's it may have some unpleasant consequences. Thus re-enabling PLLX (the main CPU parent clock) ma