From: Georgi Djakov <djakov@kernel.org>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: interconnect: qcom-bwmon: Add Hawi cpu-bwmon compatible
Date: Mon, 18 May 2026 15:28:49 +0300 [thread overview]
Message-ID: <5d80590e-d443-4e16-9203-7251d52faf49@kernel.org> (raw)
In-Reply-To: <20260518112949.ui2gfxvkjdmgc6ks@hu-mojha-hyd.qualcomm.com>
On 5/18/26 2:29 PM, Mukesh Ojha wrote:
> Hi Georgi,
>
> On Mon, Apr 27, 2026 at 11:52:55PM +0530, Mukesh Ojha wrote:
>> Add the Qualcomm Hawi SoC compatible string for the CPU bandwidth
>> monitor and there is single instance present globally to monitor
>> the traffic from CPU to LLCC.
>>
>> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
>> ---
>> .../devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml b/Documentation/devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml
>> index ce79521bb1ef..82b1d94d3010 100644
>> --- a/Documentation/devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml
>> +++ b/Documentation/devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml
>> @@ -26,6 +26,7 @@ properties:
>> - items:
>> - enum:
>> - qcom,glymur-cpu-bwmon
>> + - qcom,hawi-cpu-bwmon
>> - qcom,kaanapali-cpu-bwmon
>> - qcom,qcm2290-cpu-bwmon
>> - qcom,qcs615-cpu-bwmon
>> --
>> 2.53.0
>>
>
> I am hoping, you would be picking this., let me know.
Yes, i applied it.
Thanks,
Georgi
prev parent reply other threads:[~2026-05-18 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 18:22 [PATCH] dt-bindings: interconnect: qcom-bwmon: Add Hawi cpu-bwmon compatible Mukesh Ojha
2026-04-27 20:16 ` Krzysztof Kozlowski
2026-05-18 11:29 ` Mukesh Ojha
2026-05-18 12:28 ` Georgi Djakov [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=5d80590e-d443-4e16-9203-7251d52faf49@kernel.org \
--to=djakov@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=robh@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