linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@somainline.org>
To: Rob Herring <robh@kernel.org>
Cc: bjorn.andersson@linaro.org, agross@kernel.org,
	daniel.lezcano@linaro.org, rjw@rjwysocki.net,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org,
	konrad.dybcio@somainline.org, marijn.suijten@somainline.org,
	martin.botka@somainline.org, jeffrey.l.hugo@gmail.com,
	jami.kettunen@somainline.org,
	~postmarketos/upstreaming@lists.sr.ht,
	devicetree@vger.kernel.org, stephan@gerhold.net
Subject: Re: [PATCH v7 5/5] dt-bindings: soc: qcom: spm: Document SDM660 and MSM8998 compatibles
Date: Thu, 29 Jul 2021 15:26:08 +0200	[thread overview]
Message-ID: <285d7b38-da08-e263-d664-1cdf73d7c0d1@somainline.org> (raw)
In-Reply-To: <20210713222111.GA944952@robh.at.kernel.org>

Il 14/07/21 00:21, Rob Herring ha scritto:
> On Tue, Jun 22, 2021 at 04:11:17PM +0200, AngeloGioacchino Del Regno wrote:
>> The driver was updated to add SAW2 v4.1 support for new SoCs: document
>> the new compatibles.
> 
> Can't take patches without a S-o-b. Run checkpatch.pl, it points this
> out for you.
> 

I am truly sorry for missing my S-o-b.

>> ---
>>   .../bindings/soc/qcom/qcom,spm.yaml           | 21 +++++++++++++++++++
>>   1 file changed, 21 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,spm.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,spm.yaml
>> index 4aaa319b2932..0faf52700dec 100644
>> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,spm.yaml
>> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,spm.yaml
>> @@ -17,6 +17,10 @@ description: |
>>   properties:
>>     compatible:
>>       enum:
>> +      - qcom,sdm660-gold-saw2-v4.1-l2
>> +      - qcom,sdm660-silver-saw2-v4.1-l2
>> +      - qcom,msm8998-gold-saw2-v4.1-l2
>> +      - qcom,msm8998-silver-saw2-v4.1-l2
> 
> What's the difference between gold and silver? Are the h/w instances
> different (I realize the CPUs are) in some way? How does the OS use the
> different compatible strings?
> 

They have different configuration parameters and the HW instances should
be different indeed (at least from what I remember), plus they're always
at different iostart.

The driver is using the different compatible strings to choose which
configuration gets written. You can also avoid writing the configuration
to one of them or both (if you wish to lose capabilities given by this
driver, perhaps also if you want to simply never use the gold cluster, for
example).


>>         - qcom,msm8974-saw2-v2.1-cpu
>>         - qcom,apq8084-saw2-v2.1-cpu
>>         - qcom,apq8064-saw2-v1.1-cpu
>> @@ -33,6 +37,8 @@ additionalProperties: false
>>   
>>   examples:
>>     - |
>> +
>> +    /* Example 1: SoC using SAW2 and kpss-acc-v2 CPUIdle */
>>       cpus {
>>           #address-cells = <1>;
>>           #size-cells = <0>;
>> @@ -52,4 +58,19 @@ examples:
>>           reg = <0xf9089000 0x1000>;
>>       };
>>   
>> +  - |
>> +
>> +    /* Example 2: New-gen multi cluster SoC using SAW only for L2;
>> +     * This does not require any cpuidle driver, nor any cpu phandle.
>> +     */
>> +    power-controller@17812000 {
>> +        compatible = "qcom,msm8998-gold-saw2-v4.1-l2", "qcom,saw2";
>> +        reg = <0x17812000 0x1000>;
>> +    };
>> +
>> +    power-controller@17912000 {
>> +        compatible = "qcom,msm8998-silver-saw2-v4.1-l2", "qcom,saw2";
>> +        reg = <0x17912000 0x1000>;
>> +    };
>> +
>>   ...
>> -- 
>> 2.32.0
>>
>>


      reply	other threads:[~2021-07-29 13:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 14:11 [PATCH v7 0/5] Implement SPM/SAW for MSM8998 and SDM6xx AngeloGioacchino Del Regno
2021-06-22 14:11 ` [PATCH v7 1/5] cpuidle: qcom_spm: Detach state machine from main SPM handling AngeloGioacchino Del Regno
2021-06-22 15:06   ` Stephan Gerhold
2021-06-22 14:11 ` [PATCH v7 2/5] dt-bindings: soc: qcom: Add devicetree binding for QCOM SPM AngeloGioacchino Del Regno
2021-06-23 14:19   ` Rob Herring
2021-06-22 14:11 ` [PATCH v7 3/5] soc: qcom: spm: Implement support for SAWv4.1, SDM630/660 L2 AVS AngeloGioacchino Del Regno
2021-06-22 15:14   ` Stephan Gerhold
2021-06-22 14:11 ` [PATCH v7 4/5] soc: qcom: spm: Add compatible for MSM8998 SAWv4.1 L2 AngeloGioacchino Del Regno
2021-06-22 15:18   ` Stephan Gerhold
2021-06-22 14:11 ` [PATCH v7 5/5] dt-bindings: soc: qcom: spm: Document SDM660 and MSM8998 compatibles AngeloGioacchino Del Regno
2021-07-13 22:21   ` Rob Herring
2021-07-29 13:26     ` AngeloGioacchino Del Regno [this message]

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=285d7b38-da08-e263-d664-1cdf73d7c0d1@somainline.org \
    --to=angelogioacchino.delregno@somainline.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jami.kettunen@somainline.org \
    --cc=jeffrey.l.hugo@gmail.com \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=martin.botka@somainline.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=robh@kernel.org \
    --cc=stephan@gerhold.net \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).