On Mon, Apr 01, 2013 at 02:08:48PM -0700, David Collins wrote:
Hi,
I am working on a thermal driver which needs to be able to read a
temperature threshold from a device tree property. The hardware supports
thresholds in the range -204.8 to +204.7 C in 0.1 C steps. I have found,
as I am
2013/4/1 Ning Jiang ning.n.ji...@gmail.com:
2013/4/1 Daniel Lezcano daniel.lezc...@linaro.org:
On 03/29/2013 10:24 AM, ning.n.ji...@gmail.com wrote:
From: Ning Jiang ning.n.ji...@gmail.com
Currently there are two problems when we try to stop local timer.
First, it calls set_mode function
On 04/02/2013 12:29 AM, David Gibson wrote:
On Mon, Apr 01, 2013 at 05:24:19PM -0700, David Collins wrote:
On 04/01/2013 03:00 PM, Stephen Warren wrote:
On 04/01/2013 03:08 PM, David Collins wrote:
Hi,
I am working on a thermal driver which needs to be able to
read a temperature threshold
Hot-plugging with CONFIG_DEBUG_PREEMPT=y on a device with arm
architected timers causes a slew of using smp_processor_id() in
preemptible warnings:
BUG: using smp_processor_id() in preemptible [] code: sh/111
caller is arch_timer_cpu_notify+0x14/0xc8
This happens because sometimes
