From: Vinod Koul <vkoul@kernel.org>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: corbet@lwn.net, sre@kernel.org, robh+dt@kernel.org,
agross@kernel.org, andersson@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-doc@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_collinsd@quicinc.com
Subject: Re: [RESEND PATCH v5 1/2] dt-bindings: power: reset: qcom-pon: Add new compatible "qcom,pmk8350-pon"
Date: Mon, 12 Sep 2022 10:03:05 +0530 [thread overview]
Message-ID: <Yx62gekFa3hguPWL@matsya> (raw)
In-Reply-To: <20220909204207.15820-2-quic_amelende@quicinc.com>
On 09-09-22, 13:42, Anjelique Melendez wrote:
> From: David Collins <quic_collinsd@quicinc.com>
>
> Add a new compatible string "qcom,pmk8350-pon" for GEN3 PMIC PON
> peripherals and update "reg" property.
> Also, Add an optional "reg-names" property to differentiate between
> GEN1/GEN2 and GEN3 peripherals. GEN1/GEN2 peripherals only need one
> register address to be specified (e.g. "pon") whereas GEN3 peripherals
> can have two register addresses specified ("hlos", "pbs").
Reviewed-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2022-09-12 4:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 20:42 [RESEND PATCH v5 0/2] add support for PON GEN3 device Anjelique Melendez
2022-09-09 20:42 ` [RESEND PATCH v5 1/2] dt-bindings: power: reset: qcom-pon: Add new compatible "qcom,pmk8350-pon" Anjelique Melendez
2022-09-10 7:57 ` Krzysztof Kozlowski
2022-09-12 4:33 ` Vinod Koul [this message]
2022-09-09 20:42 ` [RESEND PATCH v5 2/2] power: reset: qcom-pon: add support for qcom,pmk8350-pon compatible string Anjelique Melendez
2022-09-10 7:57 ` Krzysztof Kozlowski
2022-09-12 4:33 ` Vinod Koul
2022-09-11 12:18 ` [RESEND PATCH v5 0/2] add support for PON GEN3 device 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=Yx62gekFa3hguPWL@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_amelende@quicinc.com \
--cc=quic_collinsd@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sre@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 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.