The MPAMF_IIDR characteristics are:
Uniquely identifies the MSC implementation by the combination of implementer, product ID, variant, and revision.
The power domain of MPAMF_IIDR is IMPLEMENTATION DEFINED.
This register is present only when FEAT_MPAM is implemented. Otherwise, direct accesses to MPAMF_IIDR are RES0.
The power and reset domain of each MSC component is specific to that component.
MPAMF_IIDR is a 32-bit register.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ProductID | Variant | Revision | Implementer |
The MSC implementer as identified in the MPAMF_IIDR.Implementer field must assure each product has a unique ProductID from any other with the same Implementer value.
This field has an IMPLEMENTATION DEFINED value.
Access to this field is RO.
This field distinguishes product variants or major revisions of the product.
Implementations of ProductID with differing software interfaces are expected to have different values in the MPAMF_IIDR.Variant field.
This field has an IMPLEMENTATION DEFINED value.
Access to this field is RO.
This field distinguishes minor revisions of the product.
This field is intended to differentiate product revisions that are minor changes and are largely software compatible with previous revisions.
This field has an IMPLEMENTATION DEFINED value.
Access to this field is RO.
Contains the JEP106 manufacturer's identification code of the designer of the MPAM MSC.
The code identifies the designer of the component, which might not be the same as the implementer of the device containing the component.
Zero is not a valid JEP106 identification code, meaning a value of zero for MPAMF_IIDR indicates this register is not implemented.
For an implementation designed by Arm, this field reads as 0x43B.
Bits [11:8] contain the JEP106 bank identifier of the designer minus 1.
Bit 7 is RES0.
Bits [6:0] contain bits [6:0] of the JEP106 manufacturer's identification code of the designer.
This field has an IMPLEMENTATION DEFINED value.
Access to this field is RO.
This register is within the MPAM feature page memory frames.
In a system that supports Secure, Non-secure, Root, and Realm memory maps, there must be MPAM feature pages in all four address maps.
MPAMF_IIDR is read-only.
MPAMF_IIDR must be readable from the Secure, Non-secure, Root, and Realm MPAM feature pages.
MPAMF_IIDR must have the same contents in the Secure, Non-secure, Root, and Realm MPAM feature pages.
Component | Frame | Offset | Instance |
---|---|---|---|
MPAM | MPAMF_BASE_s | 0x0018 | MPAMF_IIDR_s |
Accesses to this register are RO.
Component | Frame | Offset | Instance |
---|---|---|---|
MPAM | MPAMF_BASE_ns | 0x0018 | MPAMF_IIDR_ns |
Accesses to this register are RO.
Component | Frame | Offset | Instance |
---|---|---|---|
MPAM | MPAMF_BASE_rt | 0x0018 | MPAMF_IIDR_rt |
When FEAT_RME is implemented, accesses to this register are RO.
Component | Frame | Offset | Instance |
---|---|---|---|
MPAM | MPAMF_BASE_rl | 0x0018 | MPAMF_IIDR_rl |
When FEAT_RME is implemented, accesses to this register are RO.
15/12/2024 22:27; 5e0a212688c6bd7aee92394b6f5e491b4d0fee1d
Copyright © 2010-2024 Arm Limited or its affiliates. All rights reserved. This document is Non-Confidential.