All of lore.kernel.org
 help / color / mirror / Atom feed
From: neil.armstrong@linaro.org
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 2/8] arm64: dts: qcom: add initial SM8650 dtsi
Date: Mon, 6 Nov 2023 09:22:08 +0100	[thread overview]
Message-ID: <9f5f317a-4f3a-4bdd-b640-b75858bd79d4@linaro.org> (raw)
In-Reply-To: <30b4c424-39ee-7ae6-faf2-c5ba32dda07f@linaro.org>

On 02/11/2023 14:32, Konrad Dybcio wrote:
> 
> 
> On 02/11/2023 11:54, Neil Armstrong wrote:
>> On 25/10/2023 11:01, Konrad Dybcio wrote:
>>>
>>>
>>> On 10/25/23 09:47, Neil Armstrong wrote:
>>>> Add initial DTSI for the Qualcomm SM8650 platform,
>>>> only contains nodes which doesn't depend on interconnect.
>>>>
>>>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>>>> ---[...]
>>>
>>>> +            CLUSTER_SLEEP_1: cluster-sleep-1 {
>>>> +                compatible = "domain-idle-state";
>>>> +                arm,psci-suspend-param = <0x4100c344>;
>>> I think this parameter signals the AOSS to attempt system
>>> suspend and CLUSTER_SLEEP is a shallower, separate state.
>>
>> OK, so downstream call this state "APSS_OFF" and the other state
>> calling 0x41000044 "CLUSTER_PWR_DN"Well, the name APSS_OFF suggests that all clusters go offline so
> that would be a bit more complex than a simple "cut power to this
> cluster"
> 
> 
>> On sm8[345]0 and qdu1000/sm4450 there's both states called CLUSTER_SLEEP_0 and CLUSTER_SLEEP_1,
>> and referenced into CLUSTER_PD cluster power domain.
>>
>> I assume this is the same as SM8550, so what's the issue ?
> It's just that we've been naming it in the most generic way possible
> and that it could be more descriptive, especially given its
> correlation with different things

Ack, will change the naming

Neil

> 
> Konrad


  reply	other threads:[~2023-11-06  8:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  7:47 [PATCH RFC 0/8] arm64: dts: qcom: Introduce SM8650 platforms device tree Neil Armstrong
2023-10-25  7:47 ` [PATCH RFC 1/8] dt-bindings: arm: qcom: document SM8650 and the reference boards Neil Armstrong
2023-10-25  9:13   ` Krzysztof Kozlowski
2023-10-25  7:47 ` [PATCH RFC 2/8] arm64: dts: qcom: add initial SM8650 dtsi Neil Armstrong
2023-10-25  9:01   ` Konrad Dybcio
2023-10-25 11:55     ` Neil Armstrong
2023-11-02 10:54     ` Neil Armstrong
2023-11-02 13:32       ` Konrad Dybcio
2023-11-06  8:22         ` neil.armstrong [this message]
2023-10-25  7:47 ` [PATCH RFC 3/8] arm64: dts: qcom: pm8550ve: make PMK8550VE SID configurable Neil Armstrong
2023-10-25  9:02   ` Konrad Dybcio
2023-10-25  9:03   ` Dmitry Baryshkov
2023-10-25  9:17   ` Krzysztof Kozlowski
2023-10-25 11:51     ` Neil Armstrong
2023-10-25  7:47 ` [PATCH RFC 4/8] arm64: dts: qcom: sm8650: add initial SM8650 MTP dts Neil Armstrong
2023-10-25  9:03   ` Konrad Dybcio
2023-10-26  7:07   ` kernel test robot
2023-10-25  7:47 ` [PATCH RFC 5/8] arm64: dts: qcom: sm8650: add initial SM8650 QRD dts Neil Armstrong
2023-10-25  9:03   ` Konrad Dybcio
2023-10-25  7:47 ` [PATCH RFC 6/8] arm64: dts: qcom: sm8650: add interconnect dependent device nodes Neil Armstrong
2023-10-25  9:10   ` Konrad Dybcio
2023-10-25 11:52     ` Neil Armstrong
2023-10-25  7:47 ` [PATCH RFC 7/8] arm64: dts: qcom: sm8650-mtp: " Neil Armstrong
2023-10-25  9:11   ` Konrad Dybcio
2023-10-25 11:54     ` Neil Armstrong
2023-10-25  7:47 ` [PATCH RFC 8/8] arm64: dts: qcom: sm8650-qrd: " Neil Armstrong
2023-10-25  9:11   ` Konrad Dybcio
2023-10-26  7:43 ` [PATCH RFC 0/8] arm64: dts: qcom: Introduce SM8650 platforms device tree Neil Armstrong

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=9f5f317a-4f3a-4bdd-b640-b75858bd79d4@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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.