[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fec6bd98-5efd-fe34-6d75-1765219acd82@linaro.org>
Date: Sat, 23 Jul 2022 10:36:11 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Steev Klimaszewski <steev@...i.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
Georgi Djakov <djakov@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Rajendra Nayak <quic_rjendra@...cinc.com>
Subject: Re: [PATCH 10/10] arm64: dts: qcom: sdm845: add LLCC BWMON
On 23/07/2022 04:37, Steev Klimaszewski wrote:
>>
>> Currently it's 5.19.0-rc7 (torvalds tree at 4ba1329c) with a few extra
>> patches on top, the bwmon set included. It's possible that secure
>> world uses it, but I do not know enough about that to say one way or
>> the other.
To test patches you should apply them on maintainer's tree or
linux-next. Applying on other trees of course might be useful for
testing some backports, but it is independent process and different issue.
>>
>> -- steev
>>
> I think you may be right; I just applied this patchset to -next
> (20220722) and i do not see the error message there. On my 5.19-rc7
> tree, i am also testing a patchset that enables qcom devices to access
> efivars, so possibly we are ending up in secure world there?
Actually mapping of IO space should not touch secure world, so this was
a long shot assuming you test it on the next.
Best regards,
Krzysztof
Powered by blists - more mailing lists