From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org, andersson@kernel.org,
agross@kernel.org, krzysztof.kozlowski@linaro.org
Cc: marijn.suijten@somainline.org, Georgi Djakov <djakov@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
AngeloGioacchino Del Regno <kholk11@gmail.com>
Subject: Re: [PATCH 2/4] interconnect: qcom: rpm: Set QoS parameters regardless of RPM bw setting
Date: Tue, 3 Jan 2023 23:48:57 +0000 [thread overview]
Message-ID: <ca7bcae0-2427-fe65-92c2-9ca1f1526ef0@linaro.org> (raw)
In-Reply-To: <0e2bdaec-b7ba-0474-8b80-8901fcc87a0f@linaro.org>
On 03/01/2023 23:43, Bryan O'Donoghue wrote:
> On 03/01/2023 17:30, Konrad Dybcio wrote:
> I agree your code does what it says on the tin but, whats the overall
> justification to depart from the downstream logic ?
>
> ---
> bod
and can we prove with a meaningful test a behaviour change ? Better
throughput ? Lower thermals ?
---
bod
next prev parent reply other threads:[~2023-01-03 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 17:30 [PATCH 1/4] interconnect: qcom: rpm: Don't set QoS params before non-zero bw is requested Konrad Dybcio
2023-01-03 17:30 ` [PATCH 2/4] interconnect: qcom: rpm: Set QoS parameters regardless of RPM bw setting Konrad Dybcio
2023-01-03 23:43 ` Bryan O'Donoghue
2023-01-03 23:48 ` Bryan O'Donoghue [this message]
2023-01-04 0:39 ` Konrad Dybcio
2023-01-04 1:10 ` Bryan O'Donoghue
2023-01-04 0:48 ` Konrad Dybcio
2023-01-03 17:30 ` [PATCH 3/4] interconnect: qcom: rpm: make QoS INVALID default, separate out driver data Konrad Dybcio
2023-01-03 17:30 ` [PATCH 4/4] interconnect: qcom: rpm: Add support for specifying channel num Konrad Dybcio
2023-01-03 23:07 ` [PATCH 1/4] interconnect: qcom: rpm: Don't set QoS params before non-zero bw is requested Bryan O'Donoghue
2023-01-04 0:25 ` 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=ca7bcae0-2427-fe65-92c2-9ca1f1526ef0@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=djakov@kernel.org \
--cc=kholk11@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marijn.suijten@somainline.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