From: Maulik Shah <mkshah@codeaurora.org>
To: agross@kernel.org, robh+dt@kernel.org,
bjorn.andersson@linaro.org, linus.walleij@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, rnayak@codeaurora.org,
ilina@codeaurora.org, lsrao@codeaurora.org, mka@chromium.org,
swboyd@chromium.org, evgreen@chromium.org, dianders@chromium.org,
Maulik Shah <mkshah@codeaurora.org>
Subject: [PATCH 0/2] sc7180: Add PDC wakeup interrupt map for GPIOs
Date: Wed, 30 Oct 2019 12:36:16 +0530 [thread overview]
Message-ID: <1572419178-5750-1-git-send-email-mkshah@codeaurora.org> (raw)
GPIOs that can be configured as wakeup sources, have their interrupt
lines routed to PDC interrupt controller.
Add PDC wakeup interrupt map for sc7180 GPIOs.
This series has dependency on adding device tree support for sc7180 [1]
and support wakeup capable GPIOs [2] to merge first.
Dependencies:
[1] https://lkml.org/lkml/2019/10/23/223
[2] https://lkml.org/lkml/2019/9/13/1005
Maulik Shah (2):
pinctrl: qcom: sc7180: Add GPIO wakeup interrupt map
arm64: dts: qcom: sc7180: Add wakeup parent for TLMM
arch/arm64/boot/dts/qcom/sc7180.dtsi | 1 +
drivers/pinctrl/qcom/pinctrl-sc7180.c | 18 ++++++++++++++++++
2 files changed, 19 insertions(+)
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2019-10-30 7:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 7:06 Maulik Shah [this message]
2019-10-30 7:06 ` [PATCH 1/2] pinctrl: qcom: sc7180: Add GPIO wakeup interrupt map Maulik Shah
2019-11-05 9:49 ` Linus Walleij
2019-12-10 22:23 ` Lina Iyer
2019-12-11 7:09 ` Bjorn Andersson
2019-12-16 8:19 ` Linus Walleij
2019-10-30 7:06 ` [PATCH 2/2] arm64: dts: qcom: sc7180: Add wakeup parent for TLMM Maulik Shah
2019-12-10 22:27 ` Lina Iyer
2019-12-17 20:38 ` Doug Anderson
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=1572419178-5750-1-git-send-email-mkshah@codeaurora.org \
--to=mkshah@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=ilina@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsrao@codeaurora.org \
--cc=mka@chromium.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).