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] [thread-next>] [day] [month] [year] [list]

Message-ID: <aV57MPlhm53SapP6@smile.fi.intel.com>
Date: Wed, 7 Jan 2026 17:26:40 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Ernest Van Hoecke <ernestvanhoecke@...il.com>
Cc: Linus Walleij <linusw@...nel.org>,
	Bartosz Golaszewski <brgl@...nel.org>,
	Jonathan Corbet <corbet@....net>,
	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 07, 2026 at 10:31:22AM +0100, Ernest Van Hoecke wrote:

> 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.

Thank you very much for this piece!
Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>

-- 
With Best Regards,
Andy Shevchenko