[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7781e371-781c-c301-6504-99fdeb7f2b36@linaro.org>
Date: Wed, 25 Jan 2023 02:57:26 +0100
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
linux-arm-msm@...r.kernel.org, andersson@...nel.org,
agross@...nel.org, krzysztof.kozlowski@...aro.org
Cc: marijn.suijten@...ainline.org, Georgi Djakov <djakov@...nel.org>,
AngeloGioacchino Del Regno <kholk11@...il.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Loic Poulain <loic.poulain@...aro.org>,
Shawn Guo <shawn.guo@...aro.org>
Subject: Re: [PATCH v3 2/9] interconnect: qcom: rpm: Always set QoS params on
QNoC
On 19.01.2023 01:27, Bryan O'Donoghue wrote:
> On 18/01/2023 20:36, Konrad Dybcio wrote:
>> Would be very nice if somebody could test this one in particular
>> on QCM2290 to make sure it does not regress that SoC..
>>
>> Shawn, Loic?
>>
>> Konrad
>
> I have a 2290.
>
> Since I'm already helping with review, I'm happy to help with test too.
Thanks!
I'm afraid it won't be necessary though..
This patch gives more trouble than it solves. Here's the thing:
It was working perfectly on my SM6375 for quite some time and then
I rebased my branch on a newer -next and suddenly it makes things go
boom boom.. I think I'll drop it in the next revision, even if that's
what downstream does.. At least until I pretend to be an archaeologist
surgeon again and debug this..
Konrad
>
> ---
> bod
Powered by blists - more mailing lists