lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 21 Jun 2022 21:36:57 -0300
From:   Fabio Estevam <festevam@...il.com>
To:     Marc Zyngier <maz@...nel.org>
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 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.

You can add:

Tested-by: Fabio Estevam <festevam@...il.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ