linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: dmitry.torokhov@gmail.com, corbet@lwn.net, sre@kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, bjorn.andersson@linaro.org,
	swboyd@chromium.org, linux-doc@vger.kernel.org,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	David Collins <collinsd@quicinc.com>,
	David Collins <quic_collinsd@quicinc.com>
Subject: Re: [PATCH v6] dt-bindings: power: reset: qcom-pon: update "reg" property details
Date: Mon, 25 Apr 2022 16:45:08 -0500	[thread overview]
Message-ID: <YmcWZLp2X8UYOVas@robh.at.kernel.org> (raw)
In-Reply-To: <20220422191239.6271-2-quic_amelende@quicinc.com>

On Fri, Apr 22, 2022 at 12:12:38PM -0700, Anjelique Melendez wrote:
> From: David Collins <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>
> ---
>  .../bindings/power/reset/qcom,pon.yaml | 19 ++++++++++++++++++-
>  1 file changed, 18 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml b/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
> index 353f155d..65ec8197 100644
> --- a/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
> +++ b/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
> @@ -26,7 +26,24 @@ properties:
>        - qcom,pm8998-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 PMICs.
> +    minItems: 1
> +    maxItems: 2
> +
> +  reg-names:
> +    description: |
> +      For PON GEN1 and GEN2, it should be "pon".  For PON GEN3 it should include
> +      "pon_hlos" and optionally "pon_pbs".
> +    minItems: 1
> +    items:
> +      - const: pon_hlos
> +      - const: pon_pbs
> +      - const: pon

Did you test that 'reg-names = "pon";' works? It doesn't. The schema 
says 'pon' is the 3rd entry in reg-names.

As 'reg-names' is new I thin this should be:

items:
  - const: hlos
  - const: pbs

And if there's 1 entry, then 'reg-names' should not be there.

Rob

  reply	other threads:[~2022-04-25 22:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 19:12 [PATCH v6 0/5] Extend pm8941-pwrkey driver Anjelique Melendez
2022-04-22 19:12 ` [PATCH v6] dt-bindings: power: reset: qcom-pon: update "reg" property details Anjelique Melendez
2022-04-25 21:45   ` Rob Herring [this message]
2022-05-19 22:30     ` Anjelique Melendez
2022-04-22 19:12 ` [PATCH v6 2/5] input: misc: pm8941-pwrkey: fix error message Anjelique Melendez
2022-04-25  4:07   ` Dmitry Torokhov
2022-04-22 19:12 ` [PATCH v6 3/5] input: misc: pm8941-pwrkey: add support for PON GEN3 base addresses Anjelique Melendez
2022-04-25  4:07   ` Dmitry Torokhov
2022-04-22 19:12 ` [PATCH v6 4/5] input: misc: pm8941-pwrkey: add software key press debouncing support Anjelique Melendez
2022-04-25  4:07   ` Dmitry Torokhov
2022-04-22 19:12 ` [PATCH v6 5/5] input: misc: pm8941-pwrkey: simulate missed key press events Anjelique Melendez
2022-04-25  4:07   ` Dmitry Torokhov

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=YmcWZLp2X8UYOVas@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=collinsd@quicinc.com \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@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=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;
as well as URLs for NNTP newsgroup(s).