[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <128b8f7dffe45dc241ad571e8a273a2e@kernel.org>
Date: Tue, 21 Jun 2022 17:39:02 +0100
From: Marc Zyngier <maz@...nel.org>
To: Fabio Estevam <festevam@...il.com>
Cc: Andy Shevchenko <andriy.shevchenko@...el.com>,
Bjorn Helgaas <helgaas@...nel.org>,
Marek Vasut <marex@...x.de>,
Ksenija Stanojevic <ksenija.stanojevic@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-input@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: mxs_lradc_ts: Warning due to "0 is an invalid IRQ number"
Hi Fabio,
On 2022-06-21 17:23, Fabio Estevam wrote:
> Hi Marc,
>
> On Tue, Jun 21, 2022 at 12:41 PM Marc Zyngier <maz@...nel.org> wrote:
>
>> Something like the hack below could potentially make things less
>> broken, but I'm not holding my breath. If nobody cares, let's remove
>> the code altogether.
>
> With your patch applied, the warning is gone, thanks.
>
> The touchscreen is registered:
>
> [ 8.207461] input: mxs-lradc-ts as
> /devices/soc0/80000000.apb/80040000.apbx/80050000.lradc/mxs-lradc-ts/input/input0
>
> but when I run "cat /dev/input/event0" and touch the screen, no irq
> event is generated.
>
> Looking at cat /proc/interrupts shows that no mxs-lradc-touchscreen
> irq happened:
>
> 216: 0 - 10 Edge mxs-lradc-touchscreen
I'm not sure I can help you further on that. '10' seems to be
the correct interrupt for the interrupt number (irq index 0 in
the lradc device).
You'll have to debug it further, I'm afraid.
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists