From: Will Deacon <will@kernel.org>
To: Ben Horgan <ben.horgan@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
james.morse@arm.com, reinette.chatre@intel.com,
fenghuay@nvidia.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm_mpam: Fix software reset values of MPAMCFG_PRI
Date: Thu, 16 Jul 2026 17:47:56 +0100 [thread overview]
Message-ID: <178420945293.36085.2697955489302440125.b4-ty@kernel.org> (raw)
In-Reply-To: <20260515085825.1157812-1-ben.horgan@arm.com>
On Fri, 15 May 2026 09:58:25 +0100, Ben Horgan wrote:
> Priority partitioning is not supported other than to set the per-PARTID
> defaults in MPAMCFG_PRI, INTPRI and DSPRI, to the highest priority. When 0
> is the lowest priority, all ones is the highest priority. However, these
> values are calculated with an extra higher bit set.
>
> Luckily, there is still no chance of setting functional bits incorrectly.
> When the priority widths are maximal, this is ensured as the fields have
> width 16 and a u16 holds the value for each field. When the widths are
> smaller, the higher order bits beyond the advertised widths,
> MPAMF_PRI_IDR.DSPRI_WD and MPAMF_PRI_IDR.INTPRI_WD, in the priority fields
> INTPRI and DSPRI are not used to calculate the priority. It is not
> specified whether these higher order bits are RAZ/WI or Res0 and so it is
> desirable not to set them to avoid the chance of misleading reads.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm_mpam: Fix software reset values of MPAMCFG_PRI
https://git.kernel.org/arm64/c/9469764292e0
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-07-16 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 8:58 Ben Horgan
2026-07-16 16:47 ` 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=178420945293.36085.2697955489302440125.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.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®