From: Rob Herring <robh@kernel.org>
To: devi priya <quic_devipriy@quicinc.com>
Cc: agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, lgirdwood@gmail.com,
broonie@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, quic_srichara@quicinc.com,
quic_gokulsri@quicinc.com, quic_sjaganat@quicinc.com,
quic_kathirav@quicinc.com, quic_arajkuma@quicinc.com,
quic_anusha@quicinc.com, quic_poovendh@quicinc.com
Subject: Re: [PATCH 4/6] regulator: qcom_smd: Add PMIC compatible for IPQ9574
Date: Tue, 17 Jan 2023 12:38:35 -0600 [thread overview]
Message-ID: <20230117183835.GA3427325-robh@kernel.org> (raw)
In-Reply-To: <20230113150310.29709-5-quic_devipriy@quicinc.com>
On Fri, Jan 13, 2023 at 08:33:08PM +0530, devi priya wrote:
> Add mp5496 PMIC compatible string for IPQ9574 SoC
>
> Co-developed-by: Praveenkumar I <quic_ipkumar@quicinc.com>
> Signed-off-by: Praveenkumar I <quic_ipkumar@quicinc.com>
> Signed-off-by: devi priya <quic_devipriy@quicinc.com>
> ---
> .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml
> index 8c45f53212b1..7907d9385583 100644
> --- a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml
> +++ b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml
> @@ -22,7 +22,7 @@ description:
> Each sub-node is identified using the node's name, with valid values listed
> for each of the pmics below.
>
> - For mp5496, s2
> + For mp5496, s1, s2
>
> For pm2250, s1, s2, s3, s4, l1, l2, l3, l4, l5, l6, l7, l8, l9, l10, l11,
> l12, l13, l14, l15, l16, l17, l18, l19, l20, l21, l22
> @@ -84,6 +84,7 @@ properties:
> compatible:
> enum:
> - qcom,rpm-mp5496-regulators
> + - qcom,rpm-ipq9574-mp5496-regulators
Is this a different part than just mp5496? Or used in a different,
incompatible way?
> - qcom,rpm-pm2250-regulators
> - qcom,rpm-pm6125-regulators
> - qcom,rpm-pm660-regulators
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-01-17 19:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 15:03 [PATCH 0/6] Add regulator support for IPQ9574 SoC devi priya
2023-01-13 15:03 ` [PATCH 1/6] soc: qcom: smd-rpm: Add IPQ9574 compatible devi priya
2023-01-13 16:42 ` Krzysztof Kozlowski
2023-01-16 11:12 ` Mark Brown
2023-01-27 15:57 ` Devi Priya
2023-01-27 15:54 ` Devi Priya
2023-01-13 15:03 ` [PATCH 2/6] dt-bindings: soc: qcom: smd-rpm: Add IPQ9574 compatible string devi priya
2023-01-13 16:43 ` Krzysztof Kozlowski
2023-01-27 15:59 ` Devi Priya
2023-01-13 15:03 ` [PATCH 3/6] regulator: qcom_smd: Add MP5496 regulators devi priya
2023-01-13 15:24 ` Konrad Dybcio
2023-01-27 16:01 ` Devi Priya
2023-01-27 16:03 ` Konrad Dybcio
2023-01-31 10:16 ` Devi Priya
2023-01-13 15:03 ` [PATCH 4/6] regulator: qcom_smd: Add PMIC compatible for IPQ9574 devi priya
2023-01-17 18:38 ` Rob Herring [this message]
2023-01-27 16:05 ` Devi Priya
2023-01-27 20:12 ` Rob Herring
2023-01-31 10:22 ` Devi Priya
2023-01-13 15:03 ` [PATCH 5/6] arm64: dts: qcom: ipq9574: Add cpufreq & RPM related nodes devi priya
2023-01-13 15:32 ` Konrad Dybcio
2023-02-02 9:54 ` Devi Priya
2023-01-13 15:03 ` [PATCH 6/6] regulator: qcom_smd: Add support to define the bootup voltage devi priya
2023-01-13 15:37 ` Konrad Dybcio
2023-01-27 16:07 ` Devi Priya
2023-01-27 16:10 ` Konrad Dybcio
2023-01-31 9:28 ` Devi Priya
2023-01-31 12:44 ` Konrad Dybcio
2023-02-02 11:09 ` Devi Priya
2023-02-02 11:43 ` Konrad Dybcio
2023-02-06 13:48 ` Devi Priya
2023-01-31 9:37 ` Dmitry Baryshkov
2023-02-02 11:09 ` Devi Priya
2023-02-06 22:30 ` (subset) [PATCH 0/6] Add regulator support for IPQ9574 SoC Bjorn Andersson
2023-02-08 6:09 ` Devi Priya
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=20230117183835.GA3427325-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_anusha@quicinc.com \
--cc=quic_arajkuma@quicinc.com \
--cc=quic_devipriy@quicinc.com \
--cc=quic_gokulsri@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_poovendh@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
/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).