From: Anjelique Melendez <quic_amelende@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<corbet@lwn.net>, <sre@kernel.org>, <robh+dt@kernel.org>,
<agross@kernel.org>, <bjorn.andersson@linaro.org>
Cc: <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 v4 1/2] dt-bindings: power: reset: qcom-pon: update "reg" property details
Date: Thu, 8 Sep 2022 16:57:00 -0700 [thread overview]
Message-ID: <725f50bf-96dc-7976-7982-4810e8fc0610@quicinc.com> (raw)
In-Reply-To: <889151be-9ea8-6a9e-e5fe-eac1dd93250c@linaro.org>
On 9/8/2022 7:55 AM, Krzysztof Kozlowski wrote:
> On 19/08/2022 22:26, Anjelique Melendez wrote:
>>
>> Hi Krzysztof,
>> First I would like to apologize for my lack of response to this patch series
>> over these past few weeks. I have been out of office.
>>
>> On 7/26/2022 3:25 AM, Krzysztof Kozlowski wrote:
>>> On 25/07/2022 21:13, 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 constraints.
>>>>
>>>> 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 | 50 +++++++++++++++++++++++++++---
>>>> 1 file changed, 46 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..d7b6b875 100644
>>>> --- a/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
>>>> +++ b/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml
>>>> @@ -15,18 +15,27 @@ 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.
>>>> + minItems: 1
>>>> + maxItems: 2
>>>> +
>>>> + reg-names:
>>>> + minItems: 1
>>>> + maxItems: 2
>>>>
>>>> pwrkey:
>>>> type: object
>>>> @@ -42,6 +51,39 @@ required:
>>>>
>>>> unevaluatedProperties: false
>>>>
>>>> +allOf:
>>>> + - $ref: reboot-mode.yaml#
>>>> + - if:
>>>> + properties:
>>>> + compatible:
>>>> + contains:
>>>> + enum:
>>>> + - qcom,pm8916-pon
>>>> + - qcom,pms405-pon
>>>> + - qcom,pm8998-pon
>>>> + then:
>>>> + properties:
>>>> + reg:
>>>> + maxItems: 1
>>>> + reg-names:
>>>> + items:
>>>> + - const: pon
>>>
>>> All your previous patches were actually missing (in commit msg, in the
>>> code) that piece of information which you add here. You now add
>>> reg-names with "pon" for older devices. I assumed previous that it is
>>> somehow needed, so I gave you the hints how it should be coded. But I
>>> don't understand - why are you doing it
>>>
>>> This should be explained in commit msg. To me it is not needed at all...
>>> unless you want to mark that first address space is entirely different
>>> for other devices?
>> Adding reg-names "pon" for older devices is simply to provide clarification
>> about what the register relates to. Similar to reg-names "hlos" and "pbs"
>> for gen3 children devices, reg-names is completely optional and is not
>> consumed by any driver.
>
> OK, can be. Include it in the commit msg, please.
ACK
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-09-08 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 19:13 [PATCH v4 0/2] add support for PON GEN3 device Anjelique Melendez
2022-07-25 19:13 ` [PATCH v4 1/2] dt-bindings: power: reset: qcom-pon: update "reg" property details Anjelique Melendez
2022-07-26 10:25 ` Krzysztof Kozlowski
2022-08-19 20:26 ` Anjelique Melendez
2022-09-07 20:27 ` Anjelique Melendez
2022-09-08 14:55 ` Krzysztof Kozlowski
2022-09-08 23:57 ` Anjelique Melendez [this message]
2022-07-25 19:13 ` [PATCH v4 2/2] power: reset: qcom-pon: add support for qcom,pmk8350-pon compatible string Anjelique Melendez
2022-07-26 10:27 ` Krzysztof Kozlowski
2022-08-19 20:26 ` Anjelique Melendez
2022-09-07 20:28 ` Anjelique Melendez
2022-09-08 14:56 ` Krzysztof Kozlowski
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=725f50bf-96dc-7976-7982-4810e8fc0610@quicinc.com \
--to=quic_amelende@quicinc.com \
--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_collinsd@quicinc.com \
--cc=robh+dt@kernel.org \
--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 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®