From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: satya priya <skakit@codeaurora.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Sebastian Reichel <sre@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
David Collins <collinsd@codeaurora.org>,
kgunda@codeaurora.org, linux-input@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Courtney Cavin <courtney.cavin@sonymobile.com>,
Vinod Koul <vkoul@kernel.org>, Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH V3 1/5] input: pm8941-pwrkey: add support for PMK8350 PON_HLOS PMIC peripheral
Date: Tue, 1 Jun 2021 21:36:23 -0700 [thread overview]
Message-ID: <YLcKx+0/zih3iDFk@google.com> (raw)
In-Reply-To: <1620630064-16354-2-git-send-email-skakit@codeaurora.org>
On Mon, May 10, 2021 at 12:31:00PM +0530, satya priya wrote:
> From: David Collins <collinsd@codeaurora.org>
>
> On Qualcomm Technologies, Inc. PMIC PMK8350, the PON peripheral
> is split into two peripherals: PON_HLOS and PON_PBS. The
> application processor only has write access to PON_HLOS which
> limits it to only receiving PON interrupts.
>
> Add support for the PMK8350 PON_HLOS peripheral so that its
> KPDPWR_N and RESIN_N interrupts can be used to detect key
> presses.
>
> Signed-off-by: David Collins <collinsd@codeaurora.org>
> Signed-off-by: satya priya <skakit@codeaurora.org>
> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2021-06-02 4:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 7:00 [PATCH V3 0/5] Add support for PMK8350 PON_HLOS PMIC peripheral satya priya
2021-05-10 7:01 ` [PATCH V3 1/5] input: pm8941-pwrkey: add " satya priya
2021-06-02 4:36 ` Dmitry Torokhov [this message]
2021-05-10 7:01 ` [PATCH V3 2/5] dt-bindings: input: pm8941-pwrkey: add pmk8350 compatible strings satya priya
2021-06-02 4:36 ` Dmitry Torokhov
2021-05-10 7:01 ` [PATCH V3 3/5] dt-bindings: power: reset: Change 'additionalProperties' to true satya priya
2021-05-10 16:20 ` Rob Herring
2021-06-04 11:08 ` Sebastian Reichel
2021-05-10 7:01 ` [PATCH V3 4/5] dt-bindings: input: pm8941-pwrkey: Convert pm8941 power key binding to yaml satya priya
2021-05-10 14:01 ` Rob Herring
2021-05-10 16:24 ` Rob Herring
2021-05-12 4:47 ` skakit
2021-06-02 4:37 ` Dmitry Torokhov
2021-06-02 10:31 ` skakit
2021-05-10 7:01 ` [PATCH V3 5/5] dt-bindings: power: reset: qcom-pon: Convert qcom PON " satya priya
2021-05-10 16:25 ` Rob Herring
2021-06-04 11:09 ` Sebastian Reichel
2021-06-04 11:42 ` skakit
2021-06-04 11:45 ` skakit
2021-06-04 11:58 ` Sebastian Reichel
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=YLcKx+0/zih3iDFk@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=agross@kernel.org \
--cc=andy.yan@rock-chips.com \
--cc=bjorn.andersson@linaro.org \
--cc=collinsd@codeaurora.org \
--cc=courtney.cavin@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=kgunda@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=skakit@codeaurora.org \
--cc=sre@kernel.org \
--cc=vkoul@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 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).