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>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
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 5/5] arm64: dts: qcom: sm6350: Add clocks for aggre1 & aggre2 NoC
Date: Mon, 10 Nov 2025 11:21:57 +0100 [thread overview]
Message-ID: <55870352-eb6d-4cc2-840f-9de1a59ead93@oss.qualcomm.com> (raw)
In-Reply-To: <20251107-sm6350-icc-qos-v1-5-8275e5fc3f61@fairphone.com>
On 11/7/25 5:08 PM, Luca Weiss wrote:
> As per updated bindings, add the clocks for those two interconnects,
> which are required to set up QoS correctly.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
prev parent reply other threads:[~2025-11-10 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 16:08 [PATCH 0/5] Enable QoS configuration for SM6350 Luca Weiss
2025-11-07 16:08 ` [PATCH 1/5] dt-bindings: interconnect: qcom,sm6350-rpmh: Add clocks for QoS Luca Weiss
2025-11-08 12:09 ` Krzysztof Kozlowski
2025-11-07 16:08 ` [PATCH 2/5] interconnect: qcom: icc-rpmh: Get parent's regmap for nested NoCs Luca Weiss
2025-11-08 17:46 ` Dmitry Baryshkov
2025-11-07 16:08 ` [PATCH 3/5] interconnect: qcom: sm6350: Remove empty BCM arrays Luca Weiss
2025-11-08 17:47 ` Dmitry Baryshkov
2025-11-07 16:08 ` [PATCH 4/5] interconnect: qcom: sm6350: enable QoS configuration Luca Weiss
2025-11-08 17:48 ` Dmitry Baryshkov
2025-11-07 16:08 ` [PATCH 5/5] arm64: dts: qcom: sm6350: Add clocks for aggre1 & aggre2 NoC Luca Weiss
2025-11-08 17:48 ` Dmitry Baryshkov
2025-11-10 10:21 ` 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=55870352-eb6d-4cc2-840f-9de1a59ead93@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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=~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