Re: [PATCH 3/3] pwm: pxa: Remove clk_enabled field from struct pxa_pwm_chip

2013-04-01 Thread Eric Miao
On Mon, Apr 1, 2013 at 3:32 PM, Axel Lin wrote: > 2013/4/1 Eric Miao : >> On Sun, Mar 31, 2013 at 11:04 PM, Axel Lin wrote: >>> clk_enable/clk_disable maintain an enable_count, clk_prepare and >>> clk_unprepare >>> also maintain a prepare_count. These APIs will do prepare/enable when the >>> fi

Re: [PATCH 3/3] pwm: pxa: Remove clk_enabled field from struct pxa_pwm_chip

2013-04-01 Thread Axel Lin
2013/4/1 Eric Miao : > On Sun, Mar 31, 2013 at 11:04 PM, Axel Lin wrote: >> clk_enable/clk_disable maintain an enable_count, clk_prepare and >> clk_unprepare >> also maintain a prepare_count. These APIs will do prepare/enable when the >> first >> user calling these APIs, and do disable/unprepare

Re: [PATCH 3/3] pwm: pxa: Remove clk_enabled field from struct pxa_pwm_chip

2013-04-01 Thread Eric Miao
On Sun, Mar 31, 2013 at 11:04 PM, Axel Lin wrote: > clk_enable/clk_disable maintain an enable_count, clk_prepare and clk_unprepare > also maintain a prepare_count. These APIs will do prepare/enable when the > first > user calling these APIs, and do disable/unprepare when the corresponding > coun

[PATCH 3/3] pwm: pxa: Remove clk_enabled field from struct pxa_pwm_chip

2013-03-31 Thread Axel Lin
clk_enable/clk_disable maintain an enable_count, clk_prepare and clk_unprepare also maintain a prepare_count. These APIs will do prepare/enable when the first user calling these APIs, and do disable/unprepare when the corresponding counter reach 0. Thus We don't need to maintain a clk_enabled count