lkml.org 
[lkml]   [2015]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: intel_soc_dts_thermal binding issues
Date
What kernel are you using?
I think it should be fixed by commit 014d9d5d0cc1da79bbe48fbc5e1068c5616238d2, which is merged in 3.19-rc5.

Thanks,
rui

-----Original Message-----
From: jwboyer@gmail.com [mailto:jwboyer@gmail.com] On Behalf Of Josh Boyer
Sent: Wednesday, March 4, 2015 10:05 PM
To: Zhang, Rui; Eduardo Valentin
Cc: Linux PM list; Linux-Kernel@Vger. Kernel. Org
Subject: intel_soc_dts_thermal binding issues
Importance: High

Hi All,

We've seen a number of reports where people see:

[ 20.499427] intel_soc_dts_thermal: request_threaded_irq ret -22
[ 20.519160] intel_soc_dts_thermal: request_threaded_irq ret -22
[ 20.532660] intel_soc_dts_thermal: request_threaded_irq ret -22

in their boot logs. They view this as a kernel bug and report is as such. The above log came from an ASUS x200ma machine, which has a quad core Baytrail-M Pentium CPU (N3530).

I can't tell if the issue is because the driver is trying to bind to all 4 cores and only CPU0 works, or what other issue would cause this.
I personally have a Celeron based NUC with a N2820 that gets the error above for both cores and the driver doesn't load at all.

Is there something else the driver should be doing to bind to the various CPUs? If there's nothing else it can key off of, can we drop the pr_err so it stops showing up in dmesg?

josh


\
 
 \ /
  Last update: 2015-03-05 03:01    [W:0.042 / U:3.000 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site