From: Rob Herring <robh@kernel.org>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
corbet@lwn.net, sre@kernel.org, agross@kernel.org,
bjorn.andersson@linaro.org, krzysztof.kozlowski+dt@linaro.org,
vkoul@kernel.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,
David Collins <quic_collinsd@quicinc.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: power: reset: qcom-pon: update "reg" property details
Date: Mon, 18 Jul 2022 14:56:27 -0600 [thread overview]
Message-ID: <20220718205627.GA3535152-robh@kernel.org> (raw)
In-Reply-To: <ffb31b6f-8ed3-e890-976d-64a48478d404@quicinc.com>
On Mon, Jul 18, 2022 at 12:57:09PM -0700, Anjelique Melendez wrote:
>
>
> On 7/14/2022 4:48 AM, Krzysztof Kozlowski wrote:
> > On 13/07/2022 21:33, Anjelique Melendez wrote:
> >> From: David Collins <quic_collinsd@quicinc.com>
> >>
> >> Update the description of "reg" property to add the PON_PBS base
> >> address along with PON_HLOS base address. Also add "reg-names"
> >> property description.
> >>
> >> Signed-off-by: David Collins <quic_collinsd@quicinc.com>
> >> Signed-off-by: Anjelique Melendez <quic_amelende@quicinc.com>
> >> ---
> >> Documentation/devicetree/bindings/power/reset/qcom,pon.yaml | 73 ++++++++++++++++++++++++++++--
> >> 1 file changed, 69 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml b/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
> >> index 353f155d..562fe308 100644
> >> --- a/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
> >> +++ b/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
> >> @@ -15,18 +15,26 @@ description: |
> >>
> >> This DT node has pwrkey and resin as sub nodes.
> >>
> >> -allOf:
> >> - - $ref: reboot-mode.yaml#
> >> -
> >> properties:
> >> compatible:
> >> enum:
> >> - qcom,pm8916-pon
> >> - qcom,pms405-pon
> >> - qcom,pm8998-pon
> >> + - qcom,pmk8350-pon
> >>
> >> reg:
> >> - maxItems: 1
> >> + description: |
> >> + Specifies the SPMI base address for the PON (power-on) peripheral. For
> >> + PMICs that have the PON peripheral (GEN3) split into PON_HLOS and PON_PBS
> >> + (e.g. PMK8350), this can hold addresses of both PON_HLOS and PON_PBS
> >> + peripherals. In that case, the PON_PBS address needs to be specified to
> >> + facilitate software debouncing on some PMIC.
> >
> > You miss here min and maxItems
> ACK
> >
> >> +
> >> + reg-names:
> >> + description: |
> >> + For PON GEN1 and GEN2, it should be "pon". For PON GEN3 it should include
> >> + "hlos" and optionally "pbs".
> >
> > Skip description. You miss here min and maxItems.
> >
> > See
> > https://elixir.bootlin.com/linux/v5.19-rc6/source/Documentation/devicetree/bindings/clock/samsung,exynos7-clock.yaml#L57
> > for examples.
> ACK
> >
> >
> >>
> >> pwrkey:
> >> type: object
> >> @@ -42,6 +50,63 @@ required:
> >>
> >> unevaluatedProperties: false
> >>
> >> +allOf:
> >> + - $ref: reboot-mode.yaml#
> >> + - if:
> >> + properties:
> >> + compatible:
> >> + contains:
> >> + const: qcom,pm8916-pon
> >> + then:
> >> + properties:
> >> + reg:
> >> + maxItems: 1
> >> + reg-names:
> >> + items:
> >> + - const: pon
> >> +
> >> + - if:
> >> + properties:
> >> + compatible:
> >> + contains:
> >> + const: qcom,pms405-pon
> >> + then:
> >> + properties:
> >> + reg:
> >> + maxItems: 1
> >> + reg-names:
> >> + items:
> >> + - const: pon
> >> +
> >> + - if:
> >> + properties:
> >> + compatible:
> >> + contains:
> >> + const: qcom,pm8998-pon
> >> + then:
> >> + properties:
> >> + reg:
> >> + maxItems: 1
> >> + reg-names:
> >> + items:
> >> + - const: pon
> >
> > No clue why you made three if statements. This is one if for all three
> > variants.
> >
> Sorry about that was not sure how to combine the if statements originally.
> Found that you could do:
>
> - if:
> properties:
> compatible:
> contains:
> enum:
> - qcom,pm8916-pon
> - qcom,pms405-pon
> - qcom,pm8998-pon
> then:
> ...
>
> I was wondering if for the "qcom,pmk8350-pon" compatible would you rather
> have the if statement the way it is or have it follow the same pattern as
> above i.e.
>
> contains:
> const: qcom,pmk8350-pon
>
> vs
>
> contains:
> enum:
> - qcom,pmk8350-pon
The former. If only 1 possibility, use 'const'.
Rob
next prev parent reply other threads:[~2022-07-18 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 19:33 [PATCH v3 0/2] add support for PON GEN3 device Anjelique Melendez
2022-07-13 19:33 ` [PATCH v3 1/2] dt-bindings: power: reset: qcom-pon: update "reg" property details Anjelique Melendez
2022-07-14 11:48 ` Krzysztof Kozlowski
2022-07-18 19:57 ` Anjelique Melendez
2022-07-18 20:56 ` Rob Herring [this message]
2022-07-13 19:33 ` [PATCH v3 2/2] power: reset: qcom-pon: add support for qcom,pmk8350-pon compatible string Anjelique Melendez
2022-07-16 21:58 ` Sebastian Reichel
2022-07-18 19:48 ` Anjelique Melendez
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=20220718205627.GA3535152-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--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-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=sre@kernel.org \
--cc=vkoul@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.