From: "Satya Priya Kakitapalli (Temp)" <quic_c_skakit@quicinc.com>
To: Stephen Boyd <swboyd@chromium.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Das Srinagesh <gurus@codeaurora.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_collinsd@quicinc.com>,
<quic_subbaram@quicinc.com>, <quic_jprakash@quicinc.com>
Subject: Re: [PATCH V8 1/7] dt-bindings: mfd: pm8008: Modify the compatible as per driver
Date: Wed, 30 Mar 2022 16:25:03 +0530 [thread overview]
Message-ID: <26e7298c-9337-c4d4-ce32-2a67d727ccfc@quicinc.com> (raw)
In-Reply-To: <CAE-0n523f-aAUkj1SUscNgw_Gh=mP8JfXV4u_hNeFhqtfr_Fgg@mail.gmail.com>
On 3/25/2022 11:32 PM, Stephen Boyd wrote:
> Quoting Satya Priya (2022-03-25 04:58:05)
>> Modify the compatible string as per the pm8008 mfd driver.
>> Add reset-gpios property and make interrupts and interrupt-cells
>> as optional properties, they are not strictly required and may
>> cause yaml compilation errors when not added in the DT files.
> Does it have an interrupt controller inside? If so, the properties
> should be present even if the driver isn't using them.
Yes it has an interrupt controller but we are not configuring/using any
interrupts currently in the DT node. So, if we add the properties under
"required" list it throws a make dtbs error. Do you think we can somehow
bypass this error?
>> Also, change the node name in example to match with the
>> pm8008_infra DT node.
>>
>> Signed-off-by: Satya Priya <quic_c_skakit@quicinc.com>
>> ---
>> Changes in V5:
>> - Remove compatible for regulators node.
>> - Move supply nodes of the regulators to chip level.
>>
>> Changes in V6:
>> - No changes.
>>
>> Changes in V7:
>> - Removed the intermediate regulators node and added ldos
>> directly under mfd node.
>>
>> Changes in V8:
>> - Change the compatible as per driver, remove interrupts from required
>> properties, add reset-gpios and move regulators to separate binding.
>>
>> Documentation/devicetree/bindings/mfd/qcom,pm8008.yaml | 15 ++++++++++-----
>> 1 file changed, 10 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/mfd/qcom,pm8008.yaml b/Documentation/devicetree/bindings/mfd/qcom,pm8008.yaml
>> index ec3138c..12431ea 100644
>> --- a/Documentation/devicetree/bindings/mfd/qcom,pm8008.yaml
>> +++ b/Documentation/devicetree/bindings/mfd/qcom,pm8008.yaml
>> @@ -16,7 +16,7 @@ description: |
>>
>> properties:
>> compatible:
>> - const: qcom,pm8008
>> + const: qcom,pm8008-infra
> Why is the compatible being replaced with -infra postfix?
I've changed the compatible after splitting the probe into two parts
pm8008-infra-probe and pm8008-regulators-probe. Only reason for change
is to make it more readable/understandable.
>> reg:
>> description:
>> @@ -44,6 +44,10 @@ properties:
>> "#size-cells":
>> const: 0
>>
>> + reset-gpios:
>> + description: |
>> + Specifies the GPIO to be toggled to bring pm8008 chip out of reset.
> Remove description. Add maxItems: 1
Okay.
>> +
>> patternProperties:
>> "^gpio@[0-9a-f]+$":
>> type: object
>> @@ -88,10 +92,8 @@ patternProperties:
>> required:
>> - compatible
>> - reg
>> - - interrupts
>> - "#address-cells"
>> - "#size-cells"
>> - - "#interrupt-cells"
> Should reset-gpios be required? I'd expect this patch to be adding
> reset-gpios and making it required and that's about it. Given that
> there isn't a DT using this compatible upstream so far it looks like we
> don't need to do anything like worry about backwards compatibility.
Okay.
>> additionalProperties: false
>>
>> @@ -99,11 +101,12 @@ examples:
>> - |
>> #include <dt-bindings/mfd/qcom-pm8008.h>
>> #include <dt-bindings/interrupt-controller/irq.h>
>> + #include <dt-bindings/gpio/gpio.h>
>> qupv3_se13_i2c {
>> #address-cells = <1>;
>> #size-cells = <0>;
>> - pm8008i@8 {
>> - compatible = "qcom,pm8008";
>> + pm8008_infra: pmic@8 {
> Remove unused phandle.
Okay.
>> + compatible = "qcom,pm8008-infra";
>> reg = <0x8>;
>> #address-cells = <1>;
>> #size-cells = <0>;
>> @@ -113,6 +116,8 @@ examples:
>> interrupt-parent = <&tlmm>;
>> interrupts = <32 IRQ_TYPE_EDGE_RISING>;
>>
>> + reset-gpios = <&pm8350c_gpios 4 GPIO_ACTIVE_HIGH>;
>> +
>> pm8008_gpios: gpio@c000 {
>> compatible = "qcom,pm8008-gpio", "qcom,spmi-gpio";
>> reg = <0xc000>;
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2022-03-30 10:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 11:58 [PATCH V8 0/7] Add Qualcomm Technologies, Inc. PM8008 regulator driver Satya Priya
2022-03-25 11:58 ` [PATCH V8 1/7] dt-bindings: mfd: pm8008: Modify the compatible as per driver Satya Priya
2022-03-25 18:02 ` Stephen Boyd
2022-03-30 10:55 ` Satya Priya Kakitapalli (Temp) [this message]
2022-03-31 21:15 ` Stephen Boyd
2022-04-04 12:53 ` Satya Priya Kakitapalli (Temp)
2022-03-25 11:58 ` [PATCH V8 2/7] dt-bindings: mfd: pm8008: Add pm8008 regulator bindings Satya Priya
2022-03-25 18:08 ` Stephen Boyd
2022-03-30 10:56 ` Satya Priya Kakitapalli (Temp)
2022-03-25 11:58 ` [PATCH V8 3/7] mfd: pm8008: Add mfd cell struct to register LDOs Satya Priya
2022-03-25 11:58 ` [PATCH V8 4/7] regulator: Add a regulator driver for the PM8008 PMIC Satya Priya
2022-03-25 11:58 ` [PATCH V8 5/7] arm64: dts: qcom: pm8008-infra: Add base dts file for pm8008 infra Satya Priya
2022-03-25 11:58 ` [PATCH V8 6/7] arm64: dts: qcom: pm8008-regulators: Add base dts file for pm8008 regulators Satya Priya
2022-03-25 17:43 ` Stephen Boyd
2022-03-30 10:36 ` Satya Priya Kakitapalli (Temp)
2022-03-25 11:58 ` [PATCH V8 7/7] arm64: dts: qcom: sc7280: Add pm8008 support for sc7280-idp Satya Priya
2022-03-25 17:48 ` Stephen Boyd
2022-03-30 10:44 ` Satya Priya Kakitapalli (Temp)
2022-03-31 21:18 ` Stephen Boyd
2022-04-01 10:48 ` Satya Priya Kakitapalli (Temp)
2022-04-01 18:48 ` Stephen Boyd
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=26e7298c-9337-c4d4-ce32-2a67d727ccfc@quicinc.com \
--to=quic_c_skakit@quicinc.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gurus@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_collinsd@quicinc.com \
--cc=quic_jprakash@quicinc.com \
--cc=quic_subbaram@quicinc.com \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®