From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ernest Van Hoecke <ernestvanhoecke@gmail.com>
Cc: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Ernest Van Hoecke <ernest.vanhoecke@toradex.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Documentation: gpio: pca953x: clarify interrupt source detection
Date: Wed, 7 Jan 2026 17:26:40 +0200 [thread overview]
Message-ID: <aV57MPlhm53SapP6@smile.fi.intel.com> (raw)
In-Reply-To: <20260107093125.4053468-1-ernestvanhoecke@gmail.com>
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@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-07 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 9:31 [PATCH v1] Documentation: gpio: pca953x: clarify interrupt source detection Ernest Van Hoecke
2026-01-07 15:26 ` Andy Shevchenko [this message]
2026-01-08 9:50 ` Bartosz Golaszewski
2026-01-09 10:08 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aV57MPlhm53SapP6@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=corbet@lwn.net \
--cc=ernest.vanhoecke@toradex.com \
--cc=ernestvanhoecke@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=linusw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.