mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Ramón Jesús Miranda Hernández" <ramonjesusmiranda@gmail.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, krzk@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: icc-bwmon: drop the bandwidth vote across system suspend
Date: Tue, 20 Oct 2026 07:56:30 +0200	[thread overview]
Message-ID: <8a63e842-3b06-4eaa-95ae-4ba4ebe2ca1c@oss.qualcomm.com> (raw)
In-Reply-To: <CAP08=V3QB+pq0jd3UcAqzUhffv9D1fLO2UJjEKk6hURFRFfrmQ@mail.gmail.com>

On 10/19/26 5:48 PM, Ramón Jesús Miranda Hernández wrote:
> Hi Konrad,
> 
> Thanks for asking. I have now run the negative test on X1E80100 (Surface
> Pro 11): kernel 7.2.8-arch1-10 with the icc-bwmon PM ops removed (patch
> 0002 reverted), then s2idle.
> 
> - Duration: 10308 s (2 h 52 min), suspended 14:23 to 17:15 local.
> - Residency from qcom_stats: CXSD 100 %, AOSD 99.8 % (S0ix), DDR 100 %.
> - With the patch, earlier runs of 849 s and 880 s: S0ix 99.7 % and 99.9 %.
> - No CDSP crash (sleep_statsi) during this boot.
> 
> This contradicts the claim in my commit message that the qcom_stats "ddr"
> counter never advances without the patch. In this configuration it does
> advance, so reverting the PM ops alone does not break DDR collapse on this
> platform. It is one sample, and the runs differ in duration and conditions,
> so it is not a controlled comparison. I have not yet read the bwmon votes
> from the interconnect debugfs before suspend; I can add that if you want it.

No, this is conclusive enough that we can drop this patch.

Konrad

      parent reply	other threads:[~2026-10-20  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 15:54 Ramón Jesús Miranda
2026-10-19  8:40 ` Konrad Dybcio
     [not found]   ` <CAP08=V3QB+pq0jd3UcAqzUhffv9D1fLO2UJjEKk6hURFRFfrmQ@mail.gmail.com>
2026-10-20  5:56     ` Konrad Dybcio [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=8a63e842-3b06-4eaa-95ae-4ba4ebe2ca1c@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ramonjesusmiranda@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

all inboxes | Powered by JetHome®