From: Georgi Djakov <djakov@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>,
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: Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
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 1/3] dt-bindings: interconnect: add clocks property to enable QoS on sa8775p
Date: Fri, 29 Aug 2025 00:59:49 +0300 [thread overview]
Message-ID: <26e5309e-3705-4d70-a2e7-3f0e9344816b@kernel.org> (raw)
In-Reply-To: <6e036d6a-f2d1-43d6-bb35-54467edd7ec9@kernel.org>
On 8/28/25 9:20 PM, Krzysztof Kozlowski wrote:
> On 28/08/2025 20:16, Odelu Kukatla wrote:
>>
>>>> QoS configuration is essential for managing latency and bandwidth across
>>>> subsystems such as CPU, GPU, and multimedia engines. Without it, the
>>>> system may experience performance degradation, especially under
>>>
>>> So how was it working for the last 2 years?
>>>
>> The system may function normally without this feature. However, enabling
>
>
> Huh? So you agree but keep continuing the discussion?
>
> I don't understand what we are discussing in such case, but just to
> close the topic from my side and be explicit: based on above you cannot
> break the ABI.
To be even more specific, if we already have some DT binding without any
clocks and reg properties, we can't just suddenly change them from now
on to be "required". But they can still be "optional" and this will not
break the ABI, right? The old DT is still valid and the QoS will be
active when the new properties are present and this is handled properly
by the driver.
BR,
Georgi
>
>> QoS helps optimize latency and bandwidth across subsystems like CPU,
>> GPU, and multimedia engines, which becomes important in high-throughput
>> scenarios.
>
> No one discussed that.
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-08-28 21:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 14:02 [PATCH 0/3] Enable QoS configuration on SA8775P Odelu Kukatla
2025-08-08 14:02 ` [PATCH 1/3] dt-bindings: interconnect: add clocks property to enable QoS on sa8775p Odelu Kukatla
2025-08-12 10:17 ` Krzysztof Kozlowski
2025-08-13 5:55 ` Odelu Kukatla
2025-08-13 6:02 ` Krzysztof Kozlowski
2025-08-20 8:51 ` Odelu Kukatla
2025-08-24 9:08 ` Krzysztof Kozlowski
2025-08-28 18:16 ` Odelu Kukatla
2025-08-28 18:20 ` Krzysztof Kozlowski
2025-08-28 21:59 ` Georgi Djakov [this message]
2025-09-03 12:42 ` Konrad Dybcio
2025-09-03 18:01 ` Odelu Kukatla
2025-08-28 22:36 ` Dmitry Baryshkov
2025-08-08 14:02 ` [PATCH 2/3] interconnect: qcom: sa8775p: enable QoS configuration Odelu Kukatla
2025-08-09 7:35 ` Dmitry Baryshkov
2025-08-12 10:25 ` Odelu Kukatla
2025-08-08 14:03 ` [PATCH 3/3] arm64: dts: qcom: sa8775p: Add clocks for " Odelu Kukatla
2025-08-09 7:36 ` Dmitry Baryshkov
2025-08-12 9:51 ` Konrad Dybcio
2025-08-13 5:45 ` Odelu Kukatla
2025-08-15 13:11 ` Georgi Djakov
2025-08-19 9:10 ` Odelu Kukatla
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=26e5309e-3705-4d70-a2e7-3f0e9344816b@kernel.org \
--to=djakov@kernel.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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=quic_rlaggysh@quicinc.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;
as well as URLs for NNTP newsgroup(s).