From: William Breathitt Gray <william.gray@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: broonie@kernel.org, linus.walleij@linaro.org,
andriy.shevchenko@linux.intel.com, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/6] regmap-irq: Add no_status support
Date: Fri, 10 Mar 2023 07:01:23 -0500 [thread overview]
Message-ID: <ZAscE+AQVgikm74J@fedora> (raw)
In-Reply-To: <CAMRc=MdkkO4DpdLJA4SkEbAFFrdDtfZBOtLFPmkTBnSMDz=gCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
On Mon, Mar 06, 2023 at 11:11:26AM +0100, Bartosz Golaszewski wrote:
> On Mon, Feb 27, 2023 at 5:54 PM William Breathitt Gray
> <william.gray@linaro.org> wrote:
> >
> > Some devices lack status registers, yet expect to handle interrupts.
> > Introduce a no_status flag to indicate such a configuration, where
> > rather than read a status register to verify, all interrupts received
> > are assumed to be active.
> >
> > Cc: Mark Brown <broonie@kernel.org>
> > Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
[...]
> Mark,
>
> If this looks good to you, could you Ack it so that I can take it
> through the GPIO tree?
>
> Bart
Bart,
There's a change to the regmap-irq handle_mask_sync() callback I
submitted that will affect these patches [0]. If you haven't already
picked up this series, I suggest waiting until the handle_mask_sync()
change is resolved, after which I can rebase this series on top of it
and we'll end up with a cleaner git history.
[0] https://lore.kernel.org/all/20230309232009.2938-1-william.gray@linaro.org/
William Breathitt Gray
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-10 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 16:45 [PATCH v2 0/6] Migrate IDIO-16 GPIO drivers to regmap API William Breathitt Gray
2023-02-27 16:45 ` [PATCH v2 1/6] regmap-irq: Add no_status support William Breathitt Gray
2023-03-06 10:11 ` Bartosz Golaszewski
2023-03-10 12:01 ` William Breathitt Gray [this message]
2023-03-15 13:28 ` Mark Brown
2023-02-27 16:45 ` [PATCH v2 2/6] gpio: 104-dio-48e: Utilize no_status regmap-irq flag William Breathitt Gray
2023-02-27 16:45 ` [PATCH v2 3/6] gpio: idio-16: Migrate to the regmap API William Breathitt Gray
2023-02-27 16:45 ` [PATCH v2 4/6] gpio: 104-idio-16: " William Breathitt Gray
2023-02-27 16:45 ` [PATCH v2 5/6] gpio: pci-idio-16: " William Breathitt Gray
2023-03-22 16:37 ` Bartosz Golaszewski
2023-02-27 16:45 ` [PATCH v2 6/6] gpio: idio-16: Remove unused legacy interface William Breathitt Gray
2023-03-06 14:09 ` (subset) [PATCH v2 0/6] Migrate IDIO-16 GPIO drivers to regmap API Mark Brown
2023-03-06 14:12 ` Linus Walleij
2023-03-15 10:02 ` Bartosz Golaszewski
2023-03-15 10:14 ` 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=ZAscE+AQVgikm74J@fedora \
--to=william.gray@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.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.