[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <176786583791.10451.8759479946329178276.b4-ty@oss.qualcomm.com>
Date: Thu, 8 Jan 2026 10:50:41 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
To: Linus Walleij <linusw@...nel.org>, Bartosz Golaszewski <brgl@...nel.org>,
Jonathan Corbet <corbet@....net>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Ernest Van Hoecke <ernestvanhoecke@...il.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.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, 07 Jan 2026 10:31:22 +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.
>
> [...]
Applied, thanks!
[1/1] Documentation: gpio: pca953x: clarify interrupt source detection
commit: 8ba379879aa3e8cef871fed4a509d4f0a6370e6c
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
Powered by blists - more mailing lists