From: Dhruva Gole <d-gole@ti.com>
To: <linux-gpio@vger.kernel.org>
Cc: Dhruva Gole <d-gole@ti.com>, <linux-kernel@vger.kernel.org>,
Keerthy <j-keerthy@ti.com>, Bartosz Golaszewski <brgl@bgdev.pl>,
Linus Walleij <linus.walleij@linaro.org>,
Devarsh Thakkar <devarsht@ti.com>,
Tony Lindgren <tony@atomide.com>,
Vibhore Vardhan <vibhore@ti.com>
Subject: [PATCH 0/2] gpio: davinci: interrupt related fixes
Date: Mon, 3 Apr 2023 12:54:41 +0530 [thread overview]
Message-ID: <20230403072443.83810-1-d-gole@ti.com> (raw)
This series fixes some critical bugs in the gpio-davinci driver
that come to light when the system tries to wakeup from a suspended
state.
It was earlier posted as an RFC here:
https://lore.kernel.org/all/20230323122910.991148-1-d-gole@ti.com/
No changes, just resending without the RFC tag since the patches are now
proposed to be merged into mainline.
Also add all the Acks and R-by's from respective maintainers and reviewers.
Cc: Keerthy <j-keerthy@ti.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Devarsh Thakkar <devarsht@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Vibhore Vardhan <vibhore@ti.com>
Dhruva Gole (2):
gpio: davinci: Do not clear the bank intr enable bit in save_context
gpio: davinci: Add irq chip flag to skip set wake
drivers/gpio/gpio-davinci.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2023-04-03 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 7:24 Dhruva Gole [this message]
2023-04-03 7:24 ` [PATCH 1/2] gpio: davinci: Do not clear the bank intr enable bit in save_context Dhruva Gole
2023-04-03 7:24 ` [PATCH 2/2] gpio: davinci: Add irq chip flag to skip set wake Dhruva Gole
2023-04-03 15:41 ` [PATCH 0/2] gpio: davinci: interrupt related fixes Bartosz Golaszewski
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=20230403072443.83810-1-d-gole@ti.com \
--to=d-gole@ti.com \
--cc=brgl@bgdev.pl \
--cc=devarsht@ti.com \
--cc=j-keerthy@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vibhore@ti.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®