From: Melody Olvera <quic_molvera@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] dt-bindings: soc: qcom,rpmh-rsc: Update to allow for generic nodes
Date: Tue, 8 Nov 2022 13:34:01 -0800 [thread overview]
Message-ID: <d13d5638-67b1-218b-c16d-505a389ccc42@quicinc.com> (raw)
In-Reply-To: <ad1d4135-031e-9393-07af-7b81c9ecffb5@linaro.org>
On 10/27/2022 8:08 AM, Krzysztof Kozlowski wrote:
> On 26/10/2022 16:04, Melody Olvera wrote:
>> Update the bindings to allow for generic regulator nodes instead of
>> device-specific node names.
>>
>> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
>> ---
>> Documentation/devicetree/bindings/soc/qcom/qcom,rpmh-rsc.yaml | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,rpmh-rsc.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,rpmh-rsc.yaml
>> index 4a50f1d27724..0e7e07975f3a 100644
>> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,rpmh-rsc.yaml
>> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,rpmh-rsc.yaml
>> @@ -109,7 +109,7 @@ properties:
>> $ref: /schemas/power/qcom,rpmpd.yaml#
>>
>> patternProperties:
>> - '-regulators$':
>> + 'regulators$':
> This should be rather fixed like:
> https://lore.kernel.org/linux-devicetree/20220926092104.111449-1-krzysztof.kozlowski@linaro.org/
Got it.
Thanks,
Melody
>
> I don't know why there is such a popularity of adding specific model
> names as device node names...
next prev parent reply other threads:[~2022-11-08 21:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 20:04 [PATCH v3 0/4] Add base device tree files for QDU1000/QRU1000 Melody Olvera
2022-10-26 20:04 ` [PATCH v3 1/4] dt-bindings: soc: qcom,rpmh-rsc: Update to allow for generic nodes Melody Olvera
2022-10-27 15:08 ` Krzysztof Kozlowski
2022-11-08 21:34 ` Melody Olvera [this message]
2022-10-26 20:04 ` [PATCH v3 2/4] dt-bindings: arm: qcom: Document QDU1000/QRU1000 SoCs and boards Melody Olvera
2022-10-27 15:15 ` Krzysztof Kozlowski
2022-10-26 20:04 ` [PATCH v3 3/4] arm64: dts: qcom: Add base QDU1000/QRU1000 DTSIs Melody Olvera
2022-10-27 15:21 ` Krzysztof Kozlowski
2022-10-31 21:49 ` Melody Olvera
2022-10-31 23:25 ` Melody Olvera
2022-11-02 16:25 ` Krzysztof Kozlowski
2022-11-02 16:24 ` Krzysztof Kozlowski
2022-11-03 21:13 ` Melody Olvera
2022-11-04 4:05 ` Trilok Soni
2022-11-04 9:32 ` Konrad Dybcio
2022-11-04 15:34 ` Rob Herring
2022-11-09 18:19 ` Melody Olvera
2022-11-16 17:34 ` Melody Olvera
2022-10-26 20:04 ` [PATCH v3 4/4] arm64: dts: qcom: Add base QDU1000/QRU1000 IDP DTs Melody Olvera
2022-10-27 15:23 ` Krzysztof Kozlowski
2022-11-08 1:27 ` (subset) [PATCH v3 0/4] Add base device tree files for QDU1000/QRU1000 Bjorn Andersson
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=d13d5638-67b1-218b-c16d-505a389ccc42@quicinc.com \
--to=quic_molvera@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).