Re: [PATCH v4 10/10] arm_mpam: detect and enable MPAM-Fb PCC support

On Mon, Jul 27, 2026 at 03:33:21PM +0200, Lorenzo Pieralisi wrote:

On Mon, Jul 27, 2026 at 02:20:02PM +0100, Sudeep Holla wrote:

quoted

On Mon, Jul 27, 2026 at 02:48:47PM +0200, Lorenzo Pieralisi wrote:

[...]

quoted

quoted

I suppose it is to have properties parity between OF and ACPI without
having to change the driver property parsing path.

Yes, that was my initial thought as well. However, after looking into it
further, I could not find any device tree bindings in the upstream tree.
I am therefore unsure whether MPAM is supported on DT platforms.

The use of these device properties appears to have been based on DT bindings
that may never have been upstreamed. As [1] suggests, the bindings were
dropped before the initial merge.

Although we could rename these properties later to align with any DT bindings
that are introduced, I think it would be preferable to avoid adding new
properties unless they are strictly necessary.

Ah. That makes sense, if DT bindings get published the driver can be
reworked accordingly (if we want to improve how the code looks), this is
just Linux kernel internals anyway.

As it stands the "msc-id" property is churn, that's what you are saying.

Indeed why add more property with names that may need to be changed with
DT bindings in the future especially if we don't need it(IIUC it is already
there in pdev->id unless I am missing something.

-- 
Regards,
Sudeep

quoted

[1] https://lore.kernel.org/all/20251107123450.664001-1-ben.horgan@arm.com/ (local)