linux-kernel - Re: [PATCH v1] Documentation: gpio: pca953x: clarify interrupt source detection

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]

Message-ID: <CAD++jL=VQXxZysUMqLOQC8ayaqvuOZe+mWGLvm6o0T9F+2UjGw@mail.gmail.com>
Date: Fri, 9 Jan 2026 11:08:20 +0100
From: Linus Walleij <linusw@...nel.org>
To: Ernest Van Hoecke <ernestvanhoecke@...il.com>
Cc: Bartosz Golaszewski <brgl@...nel.org>, Jonathan Corbet <corbet@....net>, 
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
	Ernest Van Hoecke <ernest.vanhoecke@...adex.com>, 
	Francesco Dolcini <francesco.dolcini@...adex.com>, linux-gpio@...r.kernel.org, 
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] Documentation: gpio: pca953x: clarify interrupt source detection

On Wed, Jan 7, 2026 at 10:31 AM Ernest Van Hoecke
<ernestvanhoecke@...il.com> wrote:

> From: Ernest Van Hoecke <ernest.vanhoecke@...adex.com>
>
> There are multiple design tradeoffs and considerations in how the
> PCA953x driver detects the source(s) of an interrupt. This driver
> supports PCAL variants with input latching, a feature that is
> constrained by the fact that the interrupt status and input port
> registers cannot be read atomically. These limits and the design
> decisions deserve an in-depth explanation.
>
> Update the documentation to clarify these hardware limits and describe
> how the driver determines pending interrupts, and how it makes use of
> the PCAL input latching.
>
> Signed-off-by: Ernest Van Hoecke <ernest.vanhoecke@...adex.com>

Reviewed-by: Linus Walleij <linusw@...nel.org>

Yours,
Linus Walleij