From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from saturn.retrosnub.co.uk ([178.18.118.26]:57023 "EHLO saturn.retrosnub.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751480AbcGCJVl (ORCPT ); Sun, 3 Jul 2016 05:21:41 -0400 Subject: Re: Kernel 4.4 : mma8452 driver bug To: Micka , martin.kepplinger@theobroma-systems.com, christoph.muellner@theobroma-systems.com, knaack.h@gmx.de, "lars@metafoo.de" , pmeerw@pmeerw.net, martink@posteo.de, Robert Nelson , javier@osg.samsung.com References: Cc: linux-iio@vger.kernel.org From: Jonathan Cameron Message-ID: <703152e6-58db-5f2a-bcf8-ee72145f9cab@kernel.org> Date: Sun, 3 Jul 2016 10:21:38 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.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] [] (unwind_backtrace) from [] >> (show_stack+0x11/0x14) >> [ 24.146109] [] (show_stack) from [] >> (__report_bad_irq+0x25/0x90) >> [ 24.146124] [] (__report_bad_irq) from [] >> (note_interrupt+0x1c3/0x200) >> [ 24.146138] [] (note_interrupt) from [] >> (handle_irq_event_percpu+0xfb/0x154) >> [ 24.146151] [] (handle_irq_event_percpu) from >> [] (handle_irq_event+0x21/0x2c) >> [ 24.146164] [] (handle_irq_event) from [] >> (handle_level_irq+0x5d/0x9c) >> [ 24.146177] [] (handle_level_irq) from [] >> (generic_handle_irq+0x1d/0x28) >> [ 24.146198] [] (generic_handle_irq) from [] >> (omap_gpio_irq_handler+0xb9/0xe4) >> [ 24.146215] [] (omap_gpio_irq_handler) from [] >> (handle_irq_event_percpu+0x8b/0x154) >> [ 24.146227] [] (handle_irq_event_percpu) from >> [] (handle_irq_event+0x21/0x2c) >> [ 24.146240] [] (handle_irq_event) from [] >> (handle_level_irq+0x5d/0x9c) >> [ 24.146253] [] (handle_level_irq) from [] >> (generic_handle_irq+0x1d/0x28) >> [ 24.146265] [] (generic_handle_irq) from [] >> (__handle_domain_irq+0x3b/0x80) >> [ 24.146284] [] (__handle_domain_irq) from [] >> (__irq_svc+0x4d/0x74) >> [ 24.146299] [] (__irq_svc) from [] >> (irq_thread_fn+0x32/0x38) >> [ 24.146312] [] (irq_thread_fn) from [] >> (irq_thread+0xdf/0x148) >> [ 24.146333] [] (irq_thread) from [] (kthread+0xa3/0xb8) >> [ 24.146350] [] (kthread) from [] >> (ret_from_fork+0x11/0x1c) >> [ 24.146357] handlers: >> [ 24.146405] [] irq_default_primary_handler threaded >> [] 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 >