mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@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>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] arm64: dts: qcom: sc8280xp: remove GCC from CX power domain
Date: Mon, 2 Jan 2023 09:43:26 +0100	[thread overview]
Message-ID: <6ece10ff-cc8c-04b2-4afd-43db216227e1@linaro.org> (raw)
In-Reply-To: <9bfe5409-3174-c3be-b0b9-55c5a857e834@linaro.org>

On 31/12/2022 00:41, Konrad Dybcio wrote:
> 
> 
> On 30.12.2022 17:00, Krzysztof Kozlowski wrote:
>> Bindings do not allow power-domain property in GCC clock controller and
>> documentation does not indicate that GCC is part of VDD_CX.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> ---
>>
>> Maybe the bindings should be fixed? Maybe this was added as workaround?
>> Anyway looking at documentation I do not see such relation, except
>> downstream vdd_cx-supply (which is the same as in other SoCs and we do
>> not represent it in upstream).
> Some clocks scale with _CX, which is annotated on downstream with vdd-levels.
> We take care of that by using opp tables in consumer drivers. Usually if
> power-domains is added to a clock controller, it means that at least one of
> the clocks needs the power domain to be on (which.. should be true for CX
> if the ARM part runs anyway, no?), as for example VDD_MX/VDD_GFX may not be
> on at boot and trying to enable such clocks would result in a big kaboom..
> 
> TL;DR: if nothing exploded, it's fine to remove it

According to Bjorn, we should keep the domain.

Best regards,
Krzysztof


  reply	other threads:[~2023-01-02  8:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 16:00 Krzysztof Kozlowski
2022-12-30 16:00 ` [PATCH 2/7] arm64: dts: qcom: sc8280xp: align PSCI domain names with DT schema Krzysztof Kozlowski
2022-12-30 23:42   ` Konrad Dybcio
2022-12-30 16:00 ` [PATCH 3/7] arm64: dts: qcom: sm6375: " Krzysztof Kozlowski
2022-12-30 23:42   ` Konrad Dybcio
2022-12-30 16:01 ` [PATCH 4/7] arm64: dts: qcom: sm8150: " Krzysztof Kozlowski
2022-12-30 23:42   ` Konrad Dybcio
2022-12-30 16:01 ` [PATCH 5/7] arm64: dts: qcom: sm8250: " Krzysztof Kozlowski
2022-12-30 23:43   ` Konrad Dybcio
2022-12-30 16:01 ` [PATCH 6/7] arm64: dts: qcom: sm8350: " Krzysztof Kozlowski
2022-12-30 23:43   ` Konrad Dybcio
2022-12-30 16:01 ` [PATCH 7/7] arm64: dts: qcom: sm8450: " Krzysztof Kozlowski
2022-12-30 23:43   ` Konrad Dybcio
2022-12-30 16:03 ` [PATCH 1/7] arm64: dts: qcom: sc8280xp: remove GCC from CX power domain Krzysztof Kozlowski
2022-12-30 23:41 ` Konrad Dybcio
2023-01-02  8:43   ` Krzysztof Kozlowski [this message]
2022-12-31 11:04 ` Bryan O'Donoghue

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=6ece10ff-cc8c-04b2-4afd-43db216227e1@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@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 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®