public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: webgeek1234@gmail.com, Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Viresh Kumar <vireshk@kernel.org>,
	Lukasz Luba <lukasz.luba@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Xilin Wu <wuxilin123@gmail.com>
Subject: Re: [PATCH] arm64: dts: qcom: sm8550: Update EAS properties
Date: Thu, 29 Jan 2026 12:23:07 +0100	[thread overview]
Message-ID: <76c24508-bb75-475a-b973-d7ad18c302ce@oss.qualcomm.com> (raw)
In-Reply-To: <l6vdnit4sd5rx3k236dwrmywudkmydxfjprn2c5i7fsfmlqfnu@tabbezrje36b>

On 1/29/26 12:05 PM, Viresh Kumar wrote:
> On 29-01-26, 12:00, Konrad Dybcio wrote:
>> On 1/28/26 8:11 PM, Aaron Kling via B4 Relay wrote:
>>> It should be noted that the A715 cores seem less efficient than the
>>> A710 cores. Therefore, an average value has been assigned to them,
>>> considering that the A715 and A710 cores share a single cpufreq
>>> domain.
>>
>> Regarding the CPUFreq domain shared across cores with different power
>> characteristics, I think we shouldn't be lying to the OS, rather Linux
>> should be able to deal with it, somehow.
> 
> cpufreq-domain == cpufreq-policy here I guess. All CPUs that change
> their DVFS state together should be part of one policy. Not sure if
> there is something else you were pointing at.

Yes, they change their state together.

The question is whether it's okay for these CPUs to have different
dynamic-power-coefficient values, and whether the EM code won't be
thrown off by that.

Again, they differ because within that shared policy, there's 2
separate kinds of cores (2x Cortex-A715 + 2x Cortex-A710).

Konrad

  reply	other threads:[~2026-01-29 11:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 19:11 [PATCH] arm64: dts: qcom: sm8550: Update EAS properties Aaron Kling via B4 Relay
2026-01-29  8:36 ` Neil Armstrong
2026-01-29 11:00 ` Konrad Dybcio
2026-01-29 11:05   ` Viresh Kumar
2026-01-29 11:23     ` Konrad Dybcio [this message]
2026-01-29 11:38       ` Lukasz Luba
2026-01-29 11:56         ` Konrad Dybcio
2026-02-02  9:28           ` Lukasz Luba
2026-02-03 10:19             ` Konrad Dybcio
2026-03-18 13:50 ` Bjorn Andersson

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=76c24508-bb75-475a-b973-d7ad18c302ce@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=vireshk@kernel.org \
    --cc=webgeek1234@gmail.com \
    --cc=wuxilin123@gmail.com \
    /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