linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
	LM Sensors <lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: Re: Unhandled LM90 irq 308 on Dalmore?
Date: Fri, 20 Dec 2013 11:16:09 +0800	[thread overview]
Message-ID: <52B3B679.20206@nvidia.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1312191423090.30198@tamien>

On 12/20/2013 06:36 AM, Paul Walmsley wrote:
> Hi Jean,
> 
> On Thu, 19 Dec 2013, Jean Delvare wrote:
> 
>> Adding Wei who added interrupt support to the lm90 driver, and moving
>> to the appropriate list.
> 
> Thanks for the speedy response and list correction.
> 
>> On Thu, 19 Dec 2013 02:08:45 -0800, Paul Walmsley wrote:
>>> Just FYI, the Tegra114 Dalmore board here reports an unhandled IRQ about
>>> two minutes after boot:
>>>
>>> [  120.950839] irq 308: nobody cared (try booting with the "irqpoll" option)
> 
> ...
> 
>>> [  121.019825] handlers:
>>> [  121.022117] [<c0064408>] irq_default_primary_handler threaded
>>> [<c0384764>] lm90_irq_thread
>>> [  121.030418] Disabling IRQ #308
>>>
>>> This is on next-20131218.
>>
>> Which temperature chip is the Tegra114 Dalmore board using?
> 
> It's an NCT72.
> 
>> Is the interrupt shared with something else?
> 
> Doesn't look like it.  From /proc/interrupts:
> 
> 308:      74181          0          0          0      GPIO 116  lm90

Hi, Paul
When I developed it, my Dalmore board used GPIO 116 (GPIO_PO4) as
interrupt line, but according to our downsttream kernel, there also have
other Dalmore board used GPIO 190 (GPIO_PX6). So I think your
problems was caused by it. Please try to change the interrupt line in
dts file.

Thanks.
Wei.

> 
> That's from shortly after boot.  From successive 'cat's of 
> /proc/interrupts, I see that the interrupt count is increasing very 
> quickly.  So something is definitely not right.
> 
>> Is there any monitoring script, application or daemon polling for
>> temperatures on this system?
> 
> This is a totally quiet system, booted with 'init=/bin/bash' on the kernel 
> command line - nothing else running at all.
> 
> regards
> 
> - Paul
> 

  reply	other threads:[~2013-12-20  3:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 10:08 Unhandled LM90 irq 308 on Dalmore? Paul Walmsley
     [not found] ` <52B2C5AD.5080405-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-19 10:45   ` Jean Delvare
     [not found]     ` <20131219114500.1b1ea0b7-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2013-12-19 22:36       ` Paul Walmsley
2013-12-20  3:16         ` Wei Ni [this message]
     [not found]           ` <52B3B679.20206-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-20 16:26             ` Stephen Warren
     [not found]               ` <52B46FD2.1030409-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-12-21  5:47                 ` Paul Walmsley
     [not found]                   ` <52B52B64.5020304-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-01-06 19:13                     ` Stephen Warren
     [not found]                       ` <52CB0048.5040304-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-01-06 19:40                         ` Guenter Roeck
     [not found]                           ` <20140106194052.GA27078-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-01-06 19:42                             ` Stephen Warren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52B3B679.20206@nvidia.com \
    --to=wni-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).