From: Krzysztof Kozlowski <krzk@kernel.org>
To: Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
Cc: 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>,
Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Tipton <mike.tipton@oss.qualcomm.com>
Subject: Re: [PATCH v3 0/3] Enable QoS configuration on QCS615
Date: Fri, 13 Mar 2026 08:57:50 +0100 [thread overview]
Message-ID: <20260313-illegal-satisfied-harrier-0f4ab2@quoll> (raw)
In-Reply-To: <20260311103548.1823044-1-odelu.kukatla@oss.qualcomm.com>
On Wed, Mar 11, 2026 at 04:05:45PM +0530, Odelu Kukatla wrote:
> This series enables QoS configuration for QNOC type device which
> can be found on QCS615 platform. It enables QoS configuration
> for master ports with predefined priority and urgency forwarding.
> This helps in prioritizing the traffic originating from different
> interconnect masters at NOC (Network On Chip).
>
> The system may function normally without this feature. However,
> enabling QoS helps optimize latency and bandwidth across subsystems
> like CPU, GPU, and multimedia engines, which becomes important in
> high-throughput scenarios. This is a feature aimed at performance
> enhancement to improve system performance under concurrent workloads.
>
> Changes in v3:
> - Refactored the schema to define 'clocks' in the top-level
> properties block as suggested by Krzysztof Kozlowski.
> - Removed the conditional logic that strictly checked for
> 'qcom,qcs615-aggre1-noc' to define 'clocks'. Instead, the property
> is now defined globally but explicitly forbidden for all other
> interconnect nodes except aggre1-noc node.
Where is the rest of the changelog? v2?
Where are links to previous versions (or: why aren't you using b4?)?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-13 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 10:35 Odelu Kukatla
2026-03-11 10:35 ` [PATCH v3 1/3] dt-bindings: interconnect: qcom,qcs615-rpmh: add clocks property to enable QoS Odelu Kukatla
2026-03-13 7:59 ` Krzysztof Kozlowski
2026-03-11 10:35 ` [PATCH v3 2/3] interconnect: qcom: qcs615: enable QoS configuration Odelu Kukatla
2026-03-16 12:24 ` Konrad Dybcio
2026-03-11 10:35 ` [PATCH v3 3/3] arm64: dts: qcom: talos: Add clocks for " Odelu Kukatla
2026-03-13 12:32 ` Konrad Dybcio
2026-03-13 7:57 ` Krzysztof Kozlowski [this message]
2026-04-05 19:40 ` (subset) [PATCH v3 0/3] Enable QoS configuration on QCS615 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=20260313-illegal-satisfied-harrier-0f4ab2@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@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=linux-pm@vger.kernel.org \
--cc=mike.tipton@oss.qualcomm.com \
--cc=odelu.kukatla@oss.qualcomm.com \
--cc=raviteja.laggyshetty@oss.qualcomm.com \
--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®