From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Marc Zyngier <maz@kernel.org>, 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: Mon, 27 Jan 2025 15:15:54 +0200 [thread overview]
Message-ID: <Z5eHCsri9NphhKOW@smile.fi.intel.com> (raw)
In-Reply-To: <CAOMZO5DmKJia+6O_H3oUP64HQsaac3kDTOKx_UwG0tWJd1bsxw@mail.gmail.com>
On Tue, Jun 21, 2022 at 09:36:57PM -0300, Fabio Estevam wrote:
> Hi Marc,
>
> On Tue, Jun 21, 2022 at 1:39 PM Marc Zyngier <maz@kernel.org> wrote:
>
> > 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).
>
> As your proposed changes improve things (no more irq 0 warning is seen and the
> touchscreen irq is registered), please submit it formally, if you have a chance.
Sorry, I haven't followed here, is there any progress on this? Or in other words
what the state of affairs with this driver?
> You can add:
>
> Tested-by: Fabio Estevam <festevam@gmail.com>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-01-27 13:15 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
2022-06-22 0:36 ` Fabio Estevam
2025-01-27 13:15 ` Andy Shevchenko [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=Z5eHCsri9NphhKOW@smile.fi.intel.com \
--to=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=maz@kernel.org \
--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).