[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z5eHCsri9NphhKOW@smile.fi.intel.com>
Date: Mon, 27 Jan 2025 15:15:54 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Fabio Estevam <festevam@...il.com>
Cc: Marc Zyngier <maz@...nel.org>, 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"
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@...nel.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@...il.com>
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists