Re: [PATCH 3/7] clocksource/cadence_ttc: Store timer frequency in driver data

2013-11-12 Thread Daniel Lezcano
On 11/08/2013 10:21 PM, Soren Brinkmann wrote: It is not allowed to call clk_get_rate() from interrupt context. To avoid such calls the timer input frequency is stored in the driver's data struct which makes it accessible to the driver in any context. Signed-off-by: Soren Brinkmann ---

Re: [PATCH 3/7] clocksource/cadence_ttc: Store timer frequency in driver data

2013-11-12 Thread Daniel Lezcano
On 11/08/2013 10:21 PM, Soren Brinkmann wrote: It is not allowed to call clk_get_rate() from interrupt context. To avoid such calls the timer input frequency is stored in the driver's data struct which makes it accessible to the driver in any context. Signed-off-by: Soren Brinkmann

[PATCH 3/7] clocksource/cadence_ttc: Store timer frequency in driver data

2013-11-08 Thread Soren Brinkmann
It is not allowed to call clk_get_rate() from interrupt context. To avoid such calls the timer input frequency is stored in the driver's data struct which makes it accessible to the driver in any context. Signed-off-by: Soren Brinkmann --- drivers/clocksource/cadence_ttc_timer.c | 21

[PATCH 3/7] clocksource/cadence_ttc: Store timer frequency in driver data

2013-11-08 Thread Soren Brinkmann
It is not allowed to call clk_get_rate() from interrupt context. To avoid such calls the timer input frequency is stored in the driver's data struct which makes it accessible to the driver in any context. Signed-off-by: Soren Brinkmann soren.brinkm...@xilinx.com ---