From: Will Deacon <will@kernel.org>
To: robin.murphy@arm.com, Shouping Wang <allen.wang@hj-micro.com>
Cc: catalin.marinas@arm.com, mark.rutland@arm.com,
kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
peter.du@hj-micro.com, andy.xu@hj-micro.com
Subject: Re: [PATCH v2] perf/arm-cmn: Fix wp_dev_sel2 setting for multi-DTM configurations
Date: Fri, 11 Sep 2026 14:44:07 +0100 [thread overview]
Message-ID: <178912838524.2439009.7355093627260324589.b4-ty@kernel.org> (raw)
In-Reply-To: <20260910114601.165237-1-allen.wang@hj-micro.com>
On Thu, 10 Sep 2026 19:46:01 +0800, Shouping Wang wrote:
> When MXP_MULTIPLE_DTM_EN is TRUE, each DTM will monitor at most
> two device ports. In this case, {wp_dev_sel2, wp_dev_sel} will
> only use values 2'b00 and 2'b01 per DTM.
>
> Previously the setting allowed values beyond the supported range
> per DTM, which could cause each DTM to select invalid ports when
> MXP_MULTIPLE_DTM_EN is TRUE.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] perf/arm-cmn: Fix wp_dev_sel2 setting for multi-DTM configurations
https://git.kernel.org/arm64/c/49daa3d668b6
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-09-11 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:54 [PATCH] perf/arm-cmn: Fix {wp_dev_sel2, wp_dev_sel} limited to 0/1 when MXP_MULTIPLE_DTM_EN is TRUE Shouping Wang
2026-09-08 8:15 ` allen.wang
2026-09-08 15:04 ` Robin Murphy
2026-09-09 2:01 ` allen.wang
2026-09-09 16:19 ` Robin Murphy
2026-09-10 11:46 ` [PATCH v2] perf/arm-cmn: Fix wp_dev_sel2 setting for multi-DTM configurations Shouping Wang
2026-09-10 12:37 ` Robin Murphy
2026-09-11 13:44 ` Will Deacon [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=178912838524.2439009.7355093627260324589.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=allen.wang@hj-micro.com \
--cc=andy.xu@hj-micro.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peter.du@hj-micro.com \
--cc=robin.murphy@arm.com \
/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
all inboxes | Powered by JetHome®