From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Luca Weiss <luca.weiss@fairphone.com>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Alexander Koskovich <akoskovich@pm.me>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] arm64: dts: qcom: milos: add OSM L3 node
Date: Fri, 10 Jul 2026 15:44:29 +0200 [thread overview]
Message-ID: <bf766035-54fa-4e98-8abe-22cf0a229ffa@oss.qualcomm.com> (raw)
In-Reply-To: <20260710-milos-cpu-opp-v1-2-ae7f4b09bc77@fairphone.com>
On 7/10/26 11:22 AM, Luca Weiss wrote:
> Add the OSC L3 Cache controller node.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
I'd suggest to squash this series into 1 big patch, without patch
3 applied the OSM driver will engage and perform sync_state (with
0 requests, so it will vote for 0/lowest) and the system
performance will be tragic
Konrad
next prev parent reply other threads:[~2026-07-10 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 9:22 [PATCH 0/4] Add Milos CPU OPP table for DDR & L3 bandwidth scaling Luca Weiss
2026-07-10 9:22 ` [PATCH 1/4] dt-bindings: interconnect: OSM L3: Document Milos OSM L3 compatible Luca Weiss
2026-07-10 9:22 ` [PATCH 2/4] arm64: dts: qcom: milos: add OSM L3 node Luca Weiss
2026-07-10 13:44 ` Konrad Dybcio [this message]
2026-07-10 13:58 ` Luca Weiss
2026-07-10 14:04 ` Konrad Dybcio
2026-07-10 9:22 ` [PATCH 3/4] arm64: dts: qcom: milos: add CPU interconnect properties Luca Weiss
2026-07-10 9:37 ` sashiko-bot
2026-07-10 9:22 ` [PATCH 4/4] arm64: dts: qcom: milos: add CPU OPP table with DDR & L3 bandwidths Luca Weiss
2026-07-10 9:28 ` sashiko-bot
2026-07-10 13:45 ` Konrad Dybcio
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=bf766035-54fa-4e98-8abe-22cf0a229ffa@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=akoskovich@pm.me \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@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=linux-pm@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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