From: Nicolas Boichat <drinkcat@chromium.org>
To: linux-mediatek@lists.infradead.org
Cc: Sean Wang <sean.wang@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Chuanjia Liu <Chuanjia.Liu@mediatek.com>,
evgreen@chromium.org, swboyd@chromium.org
Subject: [PATCH 0/2] pinctrl: mediatek: Fix 2 issues related to resume from wake sources.
Date: Mon, 29 Apr 2019 11:55:13 +0800 [thread overview]
Message-ID: <20190429035515.73611-1-drinkcat@chromium.org> (raw)
This fixes 2 issues when resuming from a wake source, especially if these
wake sources are level-sensitive.
Tested on mt8183 with the series in https://patchwork.kernel.org/cover/10921121/,
but this should affect all mediatek platforms.
Nicolas Boichat (2):
pinctrl: mediatek: Ignore interrupts that are wake only during resume
pinctrl: mediatek: Update cur_mask in mask/mask ops
drivers/pinctrl/mediatek/mtk-eint.c | 34 ++++++++++++++++-------------
1 file changed, 19 insertions(+), 15 deletions(-)
--
2.21.0.593.g511ec345e18-goog
next reply other threads:[~2019-04-29 3:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 3:55 Nicolas Boichat [this message]
2019-04-29 3:55 ` [PATCH 1/2] pinctrl: mediatek: Ignore interrupts that are wake only during resume Nicolas Boichat
2019-06-21 4:47 ` Sean Wang
2019-06-25 13:50 ` Linus Walleij
2019-04-29 3:55 ` [PATCH 2/2] pinctrl: mediatek: Update cur_mask in mask/mask ops Nicolas Boichat
2019-05-13 22:29 ` Stephen Boyd
2019-05-14 1:37 ` Nicolas Boichat
2019-05-14 20:14 ` Stephen Boyd
2019-05-15 8:04 ` Nicolas Boichat
2019-05-30 17:12 ` Evan Green
2019-05-31 8:05 ` Chuanjia Liu
2019-05-31 17:17 ` Evan Green
2019-06-03 8:01 ` Chuanjia Liu
2019-06-04 0:57 ` Nicolas Boichat
2019-06-05 7:11 ` Chuanjia Liu
2019-06-10 22:25 ` Stephen Boyd
2019-06-21 4:20 ` Sean Wang
2019-06-25 13:52 ` 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=20190429035515.73611-1-drinkcat@chromium.org \
--to=drinkcat@chromium.org \
--cc=Chuanjia.Liu@mediatek.com \
--cc=evgreen@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@kernel.org \
--cc=swboyd@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox