public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Steev Klimaszewski <steev@kali.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Georgi Djakov <djakov@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rajendra Nayak <quic_rjendra@quicinc.com>
Subject: Re: [PATCH 10/10] arm64: dts: qcom: sdm845: add LLCC BWMON
Date: Sat, 23 Jul 2022 10:36:11 +0200	[thread overview]
Message-ID: <fec6bd98-5efd-fe34-6d75-1765219acd82@linaro.org> (raw)
In-Reply-To: <d89a540f-672d-83de-d19d-00f10e4370d1@kali.org>

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

  reply	other threads:[~2022-07-23  8:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 19:27 [PATCH 00/10] soc/arm64: qcom: Add LLCC BWMON on SDM845 Krzysztof Kozlowski
2022-07-20 19:27 ` [PATCH 01/10] dt-bindings: interconnect: qcom,msm8998-bwmon: add support for SDM845 LLCC BWMON Krzysztof Kozlowski
2022-07-25 22:32   ` Rob Herring
2022-07-26 11:19   ` Sibi Sankar
2022-07-20 19:27 ` [PATCH 02/10] soc: qcom: icc-bwmon: re-use IRQ enable/clear define Krzysztof Kozlowski
2022-07-26 11:20   ` Sibi Sankar
2022-07-20 19:28 ` [PATCH 03/10] soc: qcom: icc-bwmon: drop unused BWMON_ZONE_COUNT Krzysztof Kozlowski
2022-07-26 11:25   ` Sibi Sankar
2022-07-26 13:29     ` Krzysztof Kozlowski
2022-07-20 19:28 ` [PATCH 04/10] soc: qcom: icc-bwmon: store reference to varian data in container Krzysztof Kozlowski
2022-07-26 11:28   ` Sibi Sankar
2022-07-20 19:28 ` [PATCH 05/10] soc: qcom: icc-bwmon: clear all registers on init Krzysztof Kozlowski
2022-07-20 19:28 ` [PATCH 06/10] soc: qcom: icc-bwmon: store count unit per variant Krzysztof Kozlowski
2022-07-26 11:37   ` Sibi Sankar
2022-07-20 19:28 ` [PATCH 07/10] soc: qcom: icc-bwmon: use regmap and prepare for BWMON v5 Krzysztof Kozlowski
2022-07-20 19:28 ` [PATCH 08/10] soc: qcom: icc-bwmon: add per-variant quirks Krzysztof Kozlowski
2022-07-20 19:28 ` [PATCH 09/10] soc: qcom: icc-bwmon: add support for SDM845 LLCC BWMON Krzysztof Kozlowski
2022-07-20 19:28 ` [PATCH 10/10] arm64: dts: qcom: sdm845: add " Krzysztof Kozlowski
2022-07-22  1:22   ` Steev Klimaszewski
2022-07-22 17:30     ` Krzysztof Kozlowski
2022-07-23  0:29       ` Steev Klimaszewski
2022-07-23  2:37         ` Steev Klimaszewski
2022-07-23  8:36           ` Krzysztof Kozlowski [this message]
2022-07-26 11:31             ` Sibi Sankar
2022-07-26 12:01               ` Sibi Sankar
2022-07-26 13:49                 ` Krzysztof Kozlowski
2022-07-26 15:15               ` Steev Klimaszewski

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=fec6bd98-5efd-fe34-6d75-1765219acd82@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=quic_rjendra@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=steev@kali.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