Re: [PATCH] clk: clk_register: Correctly initialize enable_count

2016-02-11 Thread Rhyland Klein
On 2/11/2016 4:32 PM, Michael Turquette wrote: > Quoting Rhyland Klein (2016-02-10 10:34:16) >> On 2/9/2016 9:56 PM, Emilio López wrote: >>> Hi, >>> >>> El 09/02/16 a las 19:48, Rhyland Klein escribió: When clocks are registered, they could be enabled already in hardware. As of now, the e

Re: [PATCH] clk: clk_register: Correctly initialize enable_count

2016-02-11 Thread Michael Turquette
Quoting Rhyland Klein (2016-02-10 10:34:16) > On 2/9/2016 9:56 PM, Emilio López wrote: > > Hi, > > > > El 09/02/16 a las 19:48, Rhyland Klein escribió: > >> When clocks are registered, they could be enabled already in > >> hardware. As of now, the enable count will start at 0. When this > >> happe

Re: [PATCH] clk: clk_register: Correctly initialize enable_count

2016-02-10 Thread Rhyland Klein
On 2/9/2016 9:56 PM, Emilio López wrote: > Hi, > > El 09/02/16 a las 19:48, Rhyland Klein escribió: >> When clocks are registered, they could be enabled already in >> hardware. As of now, the enable count will start at 0. When this >> happens, it means a clock is enabled and the framework doesn't

Re: [PATCH] clk: clk_register: Correctly initialize enable_count

2016-02-09 Thread Emilio López
Hi, El 09/02/16 a las 19:48, Rhyland Klein escribió: > When clocks are registered, they could be enabled already in > hardware. As of now, the enable count will start at 0. When this > happens, it means a clock is enabled and the framework doesn't know > that, so it will always report it as disabl

[PATCH] clk: clk_register: Correctly initialize enable_count

2016-02-09 Thread Rhyland Klein
When clocks are registered, they could be enabled already in hardware. As of now, the enable count will start at 0. When this happens, it means a clock is enabled and the framework doesn't know that, so it will always report it as disabled. After the first call of clk_enable(), the enable_count wi