All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iskren Chernev <iskren.chernev@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Mark Brown <broonie@kernel.org>
Cc: Adam Skladowski <a39.skl@gmail.com>,
	Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Robert Marko <robimarko@gmail.com>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v2 2/5] dt-bindings: regulator: Document the PM6125 RPM regulators
Date: Wed, 27 Jul 2022 13:32:45 +0300	[thread overview]
Message-ID: <73a82790-52c4-b777-b4ff-f8d361f0bd29@gmail.com> (raw)
In-Reply-To: <7e742415-d93f-83d9-bf01-6f023a4d1a34@linaro.org>



On 7/27/22 10:26, Krzysztof Kozlowski wrote:
> On 26/07/2022 20:11, Iskren Chernev wrote:
>> Document the pm6125 compatible string and available regulators in the QCom SMD
>> RPM regulator documentation.
>>
>> Signed-off-by: Iskren Chernev <iskren.chernev@gmail.com>
>> Signed-off-by: Adam Skladowski <a39.skl@gmail.com>
>
> Unusual SoB chain here as well.

Will fix.

>> ---
>>  .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml
>> index c233461cc980..1122a3a17f56 100644
>> --- a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml
>> +++ b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml
>> @@ -57,6 +57,9 @@ description:
>>
>>    For pm660l s1, s2, s3, s5, l1, l2, l3, l4, l5, l6, l7, l8, l9, l10, bob
>>
>> +  For pm6125 s1, s2, s3, s4, s5, s6, s7, s8, l1, l2, l3, l5, l6, l7, l8, l9,
>> +  l10, l22, l12, l13, l14, l15, l16, l17, l18, l19, l20, l21, l22, l23, l24
>> +
>>    For pma8084, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, l1, l2, l3,
>>    l4, l5, l6, l7, l8, l9, l10, l11, l12, l13, l14, l15, l16, l17, l18, l19,
>>    l20, l21, l22, l23, l24, l25, l26, l27, lvs1, lvs2, lvs3, lvs4, 5vs1
>> @@ -90,6 +93,7 @@ properties:
>>        - qcom,rpm-pm8998-regulators
>>        - qcom,rpm-pm660-regulators
>>        - qcom,rpm-pm660l-regulators
>> +      - qcom,rpm-pm6125-regulators
>
> Put new entry in alphabetical order.

Will sort first (they are currently not sorted), then add pm6125. Should I also
sort the driver code?

> Best regards,
> Krzysztof

  reply	other threads:[~2022-07-27 10:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 18:11 [PATCH v2 0/5] PM6125 regulator support Iskren Chernev
2022-07-26 18:11 ` [PATCH v2 1/5] dt-bindings: regulator: Document the PM6125 SPMI PMIC Iskren Chernev
2022-07-26 20:36   ` Dmitry Baryshkov
2022-07-27  7:49     ` Iskren Chernev
2022-07-27  8:34       ` Dmitry Baryshkov
2022-07-26 18:11 ` [PATCH v2 2/5] dt-bindings: regulator: Document the PM6125 RPM regulators Iskren Chernev
2022-07-27  7:26   ` Krzysztof Kozlowski
2022-07-27 10:32     ` Iskren Chernev [this message]
2022-07-27 12:04       ` Krzysztof Kozlowski
2022-07-26 18:11 ` [PATCH v2 3/5] regulator: qcom_spmi: Add support for new regulator types Iskren Chernev
2022-07-27 11:57   ` Mark Brown
2022-07-27 23:14     ` Iskren Chernev
2022-07-28 11:11       ` Mark Brown
2022-07-28 20:59         ` Iskren Chernev
2022-07-29 12:04           ` Mark Brown
2022-07-29 21:07             ` Jorge Ramirez-Ortiz, Gmail
2022-07-26 18:11 ` [PATCH v2 4/5] regulator: qcom_spmi: Add PM6125 PMIC support Iskren Chernev
2022-07-26 20:41   ` Dmitry Baryshkov
2022-07-27 11:59   ` Mark Brown
2022-07-26 18:11 ` [PATCH v2 5/5] regulator: qcom_smd: Add PM6125 regulators support Iskren Chernev
2022-07-26 20:42   ` Dmitry Baryshkov

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=73a82790-52c4-b777-b4ff-f8d361f0bd29@gmail.com \
    --to=iskren.chernev@gmail.com \
    --cc=a39.skl@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robimarko@gmail.com \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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.