From: Jonathan Cameron <jic23@kernel.org>
To: Micka <mickamusset@gmail.com>,
martin.kepplinger@theobroma-systems.com,
christoph.muellner@theobroma-systems.com, knaack.h@gmx.de,
"lars@metafoo.de" <lars@metafoo.de>,
pmeerw@pmeerw.net, martink@posteo.de,
Robert Nelson <robertcnelson@gmail.com>,
javier@osg.samsung.com
Cc: linux-iio@vger.kernel.org
Subject: Re: Kernel 4.4 : mma8452 driver bug
Date: Sun, 3 Jul 2016 10:21:38 +0100 [thread overview]
Message-ID: <703152e6-58db-5f2a-bcf8-ee72145f9cab@kernel.org> (raw)
In-Reply-To: <bbc93394-b840-dd1f-0109-e8edff1c386d@kernel.org>
On 26/06/16 15:36, Jonathan Cameron wrote:
> On 23/06/16 15:20, Micka wrote:
>> Hi,
>>
>> I'm using your driver on the kernel 4.4 and I got this message :
>>
>> [ 24.145906] irq 94: nobody cared (try booting with the "irqpoll" option)
>> [ 24.146025] CPU: 0 PID: 219 Comm: irq/94-mma8452 Not tainted 4.4.13-bone11 #9
>> [ 24.146033] Hardware name: Generic AM33XX (Flattened Device Tree)
>> [ 24.146085] [<c0013e85>] (unwind_backtrace) from [<c0011eb9>]
>> (show_stack+0x11/0x14)
>> [ 24.146109] [<c0011eb9>] (show_stack) from [<c005f739>]
>> (__report_bad_irq+0x25/0x90)
>> [ 24.146124] [<c005f739>] (__report_bad_irq) from [<c005f9b3>]
>> (note_interrupt+0x1c3/0x200)
>> [ 24.146138] [<c005f9b3>] (note_interrupt) from [<c005e01b>]
>> (handle_irq_event_percpu+0xfb/0x154)
>> [ 24.146151] [<c005e01b>] (handle_irq_event_percpu) from
>> [<c005e095>] (handle_irq_event+0x21/0x2c)
>> [ 24.146164] [<c005e095>] (handle_irq_event) from [<c005fe51>]
>> (handle_level_irq+0x5d/0x9c)
>> [ 24.146177] [<c005fe51>] (handle_level_irq) from [<c005d965>]
>> (generic_handle_irq+0x1d/0x28)
>> [ 24.146198] [<c005d965>] (generic_handle_irq) from [<c039e531>]
>> (omap_gpio_irq_handler+0xb9/0xe4)
>> [ 24.146215] [<c039e531>] (omap_gpio_irq_handler) from [<c005dfab>]
>> (handle_irq_event_percpu+0x8b/0x154)
>> [ 24.146227] [<c005dfab>] (handle_irq_event_percpu) from
>> [<c005e095>] (handle_irq_event+0x21/0x2c)
>> [ 24.146240] [<c005e095>] (handle_irq_event) from [<c005fe51>]
>> (handle_level_irq+0x5d/0x9c)
>> [ 24.146253] [<c005fe51>] (handle_level_irq) from [<c005d965>]
>> (generic_handle_irq+0x1d/0x28)
>> [ 24.146265] [<c005d965>] (generic_handle_irq) from [<c005db07>]
>> (__handle_domain_irq+0x3b/0x80)
>> [ 24.146284] [<c005db07>] (__handle_domain_irq) from [<c066b68d>]
>> (__irq_svc+0x4d/0x74)
>> [ 24.146299] [<c066b68d>] (__irq_svc) from [<c005e982>]
>> (irq_thread_fn+0x32/0x38)
>> [ 24.146312] [<c005e982>] (irq_thread_fn) from [<c005eb9b>]
>> (irq_thread+0xdf/0x148)
>> [ 24.146333] [<c005eb9b>] (irq_thread) from [<c0040643>] (kthread+0xa3/0xb8)
>> [ 24.146350] [<c0040643>] (kthread) from [<c000ea95>]
>> (ret_from_fork+0x11/0x1c)
>> [ 24.146357] handlers:
>> [ 24.146405] [<c005e0a1>] irq_default_primary_handler threaded
>> [<bf94d101>] mma8452_interrupt [mma8452]
>> [ 24.146580] Disabling IRQ #94
>>
>> is it a bug from the driver or is it my fault ?
>>
> I'm stretching a bit, but any chance the registered irq is the wrong one?
> e.g. The mma8452 is registered for a different irq than 94?
> Not sure whether the bit at the end about handlers would display it in that
> case...
Hi Micka,
Any progress with getting this sorted out?
Thanks,
Jonathan
>
> Jonathan
>> Micka,
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-07-03 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 14:20 Kernel 4.4 : mma8452 driver bug Micka
2016-06-26 14:36 ` Jonathan Cameron
2016-07-03 9:21 ` Jonathan Cameron [this message]
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=703152e6-58db-5f2a-bcf8-ee72145f9cab@kernel.org \
--to=jic23@kernel.org \
--cc=christoph.muellner@theobroma-systems.com \
--cc=javier@osg.samsung.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=martin.kepplinger@theobroma-systems.com \
--cc=martink@posteo.de \
--cc=mickamusset@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=robertcnelson@gmail.com \
/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).