From: Bjorn Andersson <andersson@kernel.org>
To: Andy Gross <agross@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Georgi Djakov <djakov@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/4] SM8250 + SM6350 BWMONs
Date: Thu, 13 Jul 2023 22:33:59 -0700 [thread overview]
Message-ID: <168931284121.1538684.4889558485048519833.b4-ty@kernel.org> (raw)
In-Reply-To: <20230711-topic-sm638250_bwmon-v1-0-bd4bb96b0673@linaro.org>
On Tue, 11 Jul 2023 16:35:12 +0200, Konrad Dybcio wrote:
> SM8250 and SM6350 both have 5 BWMONs: one for the CPU path, one for the
> LLCC path and 3 more for the NPU.
>
> This series hooks up the first two for both SoCs.
>
> Rebased on top of djakov/icc/icc-next, atop the 7180 addition.
>
> [...]
Applied, thanks!
[3/4] arm64: dts: qcom: sm8250: Add BWMONs
commit: 2a2bd124d4c01c53833a4f0c7fef4faf18351c51
[4/4] arm64: dts: qcom: sm6350: Add BWMONs
commit: 1df6b32e3819dc1de5ccd49982686153ab9e158c
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-07-14 5:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 14:35 [PATCH 0/4] SM8250 + SM6350 BWMONs Konrad Dybcio
2023-07-11 14:35 ` [PATCH 1/4] dt-bindings: interconnect: qcom,msm8998-bwmon: Add SM8250 bwmon instances Konrad Dybcio
2023-07-11 18:09 ` Conor Dooley
2023-07-11 14:35 ` [PATCH 2/4] dt-bindings: interconnect: qcom,msm8998-bwmon: Add SM6350 " Konrad Dybcio
2023-07-11 18:09 ` Conor Dooley
2023-07-11 14:35 ` [PATCH 3/4] arm64: dts: qcom: sm8250: Add BWMONs Konrad Dybcio
2023-07-11 14:35 ` [PATCH 4/4] arm64: dts: qcom: sm6350: " Konrad Dybcio
2023-07-14 5:33 ` Bjorn Andersson [this message]
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=168931284121.1538684.4889558485048519833.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@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 \
--cc=robh+dt@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