From: Anjelique Melendez <quic_amelende@quicinc.com>
To: Rob Herring <robh@kernel.org>
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>, <collinsd@codeaurora.org>,
<bjorn.andersson@linaro.org>, <swboyd@chromium.org>,
<skakit@codeaurora.org>, <linux-doc@vger.kernel.org>,
<linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
David Collins <quic_collinsd@quicinc.com>
Subject: Re: [PATCH v5 1/5] dt-bindings: power: reset: qcom-pon: update "reg" property details
Date: Fri, 15 Apr 2022 11:44:10 -0700 [thread overview]
Message-ID: <89483178-2b8b-e583-7f4f-572076c95141@quicinc.com> (raw)
In-Reply-To: <Ylg+7MVRS4sKbOFb@robh.at.kernel.org>
On 4/14/2022 8:34 AM, Rob Herring wrote:
> On Mon, Apr 11, 2022 at 01:05:03PM -0700, 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>
>> ---
>> .../bindings/power/reset/qcom,pon.yaml | 20 +++++++++++++++++++-
>> 1 file changed, 19 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..542200b2 100644
>> --- a/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
>> +++ b/Documentation/bindings/power/reset/qcom,pon.yaml
>> @@ -26,7 +26,25 @@ 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
>> + maxItems: 2
>> + items:
>> + - const: pon_hlos
>> + - const: pon_pbs
>> + - const: pon
>
> This says there are 3 entries, but you limited to 2. The schema also
> doesn't match what the description says. Entries should be extended by
> adding new entries to the end and keeping optional entries last. So like
> this:
>
> minItems: 1
> items:
> - const: pon
> - const: pon_hlos
> - const: pon_pbs
>
> RobWill update in next patch. Thanks
next prev parent reply other threads:[~2022-04-15 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 20:05 [PATCH v5 0/5] Extend pm8941-pwrkey driver Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 1/5] dt-bindings: power: reset: qcom-pon: update "reg" property details Anjelique Melendez
2022-04-14 15:34 ` Rob Herring
2022-04-15 18:44 ` Anjelique Melendez [this message]
2022-04-11 20:05 ` [PATCH v5 2/5] input: misc: pm8941-pwrkey: fix error message Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 3/5] input: misc: pm8941-pwrkey: add support for PON GEN3 base addresses Anjelique Melendez
2022-04-14 21:18 ` Dmitry Baryshkov
2022-04-15 18:46 ` Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 4/5] input: misc: pm8941-pwrkey: add software key press debouncing support Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 5/5] input: misc: pm8941-pwrkey: simulate missed key press events 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=89483178-2b8b-e583-7f4f-572076c95141@quicinc.com \
--to=quic_amelende@quicinc.com \
--cc=bjorn.andersson@linaro.org \
--cc=collinsd@codeaurora.org \
--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_collinsd@quicinc.com \
--cc=robh@kernel.org \
--cc=skakit@codeaurora.org \
--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