From: Marc Zyngier <maz@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
Bjorn Helgaas <helgaas@kernel.org>, Marek Vasut <marex@denx.de>,
Ksenija Stanojevic <ksenija.stanojevic@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: mxs_lradc_ts: Warning due to "0 is an invalid IRQ number"
Date: Tue, 21 Jun 2022 17:39:02 +0100 [thread overview]
Message-ID: <128b8f7dffe45dc241ad571e8a273a2e@kernel.org> (raw)
In-Reply-To: <CAOMZO5B6606rwWoG-ydEz2UQpnj9QhUK2b5dCHRtp9u=Pe4new@mail.gmail.com>
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@kernel.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...
next prev parent reply other threads:[~2022-06-21 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 23:52 mxs_lradc_ts: Warning due to "0 is an invalid IRQ number" Fabio Estevam
2020-07-01 15:32 ` Fabio Estevam
2020-07-01 22:41 ` Bjorn Helgaas
2022-06-21 14:00 ` Andy Shevchenko
2022-06-21 15:41 ` Marc Zyngier
2022-06-21 16:23 ` Fabio Estevam
2022-06-21 16:39 ` Marc Zyngier [this message]
2022-06-22 0:36 ` Fabio Estevam
2025-01-27 13:15 ` Andy Shevchenko
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=128b8f7dffe45dc241ad571e8a273a2e@kernel.org \
--to=maz@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=helgaas@kernel.org \
--cc=ksenija.stanojevic@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.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).