From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: corbet@lwn.net, sre@kernel.org, robh+dt@kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, bjorn.andersson@linaro.org,
swboyd@chromium.org, linux-doc@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 3/5] input: misc: pm8941-pwrkey: add support for PON GEN3 base addresses
Date: Sun, 24 Apr 2022 21:07:15 -0700 [thread overview]
Message-ID: <YmYeczmNcN/sVUPk@google.com> (raw)
In-Reply-To: <20220422191239.6271-4-quic_amelende@quicinc.com>
On Fri, Apr 22, 2022 at 12:12:41PM -0700, Anjelique Melendez wrote:
> Currently, PON address is read from the "reg" property. For PON GEN3,
> which starts with PMK8350, the "reg" property will have both the PON
> HLOS and PON PBS addesses defined. Add support so that all PON
> generations can be configured.
>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> Signed-off-by: Anjelique Melendez <quic_amelende@quicinc.com>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2022-04-25 4:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:12 [PATCH v6 0/5] Extend pm8941-pwrkey driver Anjelique Melendez
2022-04-22 19:12 ` [PATCH v6] dt-bindings: power: reset: qcom-pon: update "reg" property details Anjelique Melendez
2022-04-25 21:45 ` Rob Herring
2022-05-19 22:30 ` Anjelique Melendez
2022-04-22 19:12 ` [PATCH v6 2/5] input: misc: pm8941-pwrkey: fix error message Anjelique Melendez
2022-04-25 4:07 ` Dmitry Torokhov
2022-04-22 19:12 ` [PATCH v6 3/5] input: misc: pm8941-pwrkey: add support for PON GEN3 base addresses Anjelique Melendez
2022-04-25 4:07 ` Dmitry Torokhov [this message]
2022-04-22 19:12 ` [PATCH v6 4/5] input: misc: pm8941-pwrkey: add software key press debouncing support Anjelique Melendez
2022-04-25 4:07 ` Dmitry Torokhov
2022-04-22 19:12 ` [PATCH v6 5/5] input: misc: pm8941-pwrkey: simulate missed key press events Anjelique Melendez
2022-04-25 4:07 ` Dmitry Torokhov
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=YmYeczmNcN/sVUPk@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_amelende@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sre@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.