mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v4 0/4] arm64: dts: qcom: sm8650: rework CPU & GPU thermal zones
Date: Wed, 26 Feb 2025 07:40:48 -0600	[thread overview]
Message-ID: <174057724683.237840.9228702761146202585.b4-ty@kernel.org> (raw)
In-Reply-To: <20250203-topic-sm8650-thermal-cpu-idle-v4-0-65e35f307301@linaro.org>


On Mon, 03 Feb 2025 14:23:16 +0100, Neil Armstrong wrote:
> On the SM8650 platform, the dynamic clock and voltage scaling (DCVS) for
> the CPUs is handled by hardware & firmware using factory and
> form-factor determined parameters in order to maximize frequency while
> keeping the temperature way below the junction temperature where the SoC
> would experience a thermal shutdown if not permanent damages.
> 
> On the other side, the High Level Ooperating System (HLOS), like Linux,
> is able to adjust the CPU and GPU frequency using the internal SoC
> temperature sensors (here tsens) and it's UP/LOW interrupts, but it
> effectly does the same work twice for CPU in an less effective manner.
> 
> [...]

Applied, thanks!

[1/4] arm64: dts: qcom: sm8650: drop cpu thermal passive trip points
      commit: 7f9a670396029116424a803d3971ff0e552ff0b3
[2/4] arm64: dts: qcom: sm8650: setup gpu thermal with higher temperatures
      commit: 2250f65b32565eb8b757e89248c75977f370f498
[3/4] arm64: dts: qcom: sm8650: harmonize all unregulated thermal trip points
      commit: c516beb248a96f5a93fb4f9a6cb0dda4155eadbb
[4/4] arm64: dts: qcom: sm8650: drop remaining polling-delay-passive properties
      commit: 30235bb8b0487537ddd7dd4a480c907add6cd19b

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2025-02-26 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 13:23 Neil Armstrong
2025-02-03 13:23 ` [PATCH v4 1/4] arm64: dts: qcom: sm8650: drop cpu thermal passive trip points Neil Armstrong
2025-02-03 13:29   ` Konrad Dybcio
2025-02-03 13:23 ` [PATCH v4 2/4] arm64: dts: qcom: sm8650: setup gpu thermal with higher temperatures Neil Armstrong
2025-02-03 13:31   ` Konrad Dybcio
2025-02-03 13:53     ` Konrad Dybcio
2025-02-03 13:23 ` [PATCH v4 3/4] arm64: dts: qcom: sm8650: harmonize all unregulated thermal trip points Neil Armstrong
2025-02-11 13:34   ` Konrad Dybcio
2025-02-03 13:23 ` [PATCH v4 4/4] arm64: dts: qcom: sm8650: drop remaining polling-delay-passive properties Neil Armstrong
2025-02-26 13:40 ` Bjorn Andersson [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=174057724683.237840.9228702761146202585.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@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®