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 v2 0/2] pinctrl: mediatek: mt8183: Add support for wake sources
Date: Wed, 8 May 2019 15:33:29 +0800 [thread overview]
Message-ID: <20190508073331.27475-1-drinkcat@chromium.org> (raw)
This adds support for wake sources in pinctrl-mtk-common-v2, and
pinctrl-mt8183. Without this patch, all interrupts that are left
enabled on suspend act as wake sources (and wake sources without
interrupt enabled do not).
Changes since v1:
- Move changes from mtk-common-v2 to mtk-pinctrl-paris, as
recommended by Sean, to keep better separation between eint
and pinctrl-common features.
Nicolas Boichat (2):
pinctrl: mediatek: Add pm_ops to pinctrl-paris
pinctrl: mediatek: mt8183: Add mtk_pinctrl_paris_pm_ops
drivers/pinctrl/mediatek/pinctrl-mt8183.c | 1 +
drivers/pinctrl/mediatek/pinctrl-paris.c | 19 +++++++++++++++++++
drivers/pinctrl/mediatek/pinctrl-paris.h | 2 ++
3 files changed, 22 insertions(+)
--
2.21.0.1020.gf2820cf01a-goog
next reply other threads:[~2019-05-08 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 7:33 Nicolas Boichat [this message]
2019-05-08 7:33 ` [PATCH v2 1/2] pinctrl: mediatek: Add pm_ops to pinctrl-paris Nicolas Boichat
2019-05-08 7:33 ` [PATCH v2 2/2] pinctrl: mediatek: mt8183: Add pm_ops Nicolas Boichat
2019-05-16 11:55 ` [PATCH v2 0/2] pinctrl: mediatek: mt8183: Add support for wake sources Linus Walleij
2019-05-16 12:47 ` Nicolas Boichat
2019-05-21 10:13 ` Sean Wang
2019-06-01 17:41 ` 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=20190508073331.27475-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
all inboxes | Powered by JetHome®