<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE register_page SYSTEM "registers.dtd">
<!-- Copyright (c) 2010-2026 Arm Limited or its affiliates. All rights reserved. -->
<!-- This document is Non-Confidential. This document may only be used and distributed in accordance with the terms of the agreement entered into by Arm and the party that Arm delivered this document to. -->
<!--The data contained in this document is preliminary and subject to change or correction following further review. -->
<?xml-stylesheet href="one_register.xsl" type="text/xsl" ?>







<register_page>
  <registers>
  
    <register is_register="True" is_internal="False" is_stub_entry="False">
      <reg_short_name>MPAMF_IMPL_IDR</reg_short_name>
        
        <reg_long_name>MPAM Implementation-Specific Partitioning Feature Identification Register</reg_long_name>

        <power_domain_text>The power domain of MPAMF_IMPL_IDR is <arm-defined-word>IMPLEMENTATION DEFINED</arm-defined-word></power_domain_text>


      
            <reg_condition otherwise="RES0">when (FEAT_MPAMv0p1 is implemented or FEAT_MPAMv1p0 is implemented) and MPAMF_IDR.HAS_IMPL_IDR == '1'</reg_condition>
      

    
  <reg_address
      external_access="False"
    mem_map_access="True"
      power_domain="None"
  >
    <reg_component>MPAM</reg_component>
    <reg_frame>MPAMF_BASE_s</reg_frame>
    <reg_offset><hexnumber>0x0028</hexnumber></reg_offset>
    <reg_instance>MPAMF_IMPL_IDR_s</reg_instance>
    <reg_access>
      
        
      <reg_access_state>
          <reg_access_level>When FEAT_MPAMv1p0 is implemented or FEAT_MPAMv0p1 is implemented</reg_access_level>
          <reg_access_type>RO</reg_access_type>
      </reg_access_state>
    </reg_access>
</reg_address>
    
  <reg_address
      external_access="False"
    mem_map_access="True"
      power_domain="None"
  >
    <reg_component>MPAM</reg_component>
    <reg_frame>MPAMF_BASE_ns</reg_frame>
    <reg_offset><hexnumber>0x0028</hexnumber></reg_offset>
    <reg_instance>MPAMF_IMPL_IDR_ns</reg_instance>
    <reg_access>
      
        
      <reg_access_state>
          <reg_access_level>When FEAT_MPAMv1p0 is implemented or FEAT_MPAMv0p1 is implemented</reg_access_level>
          <reg_access_type>RO</reg_access_type>
      </reg_access_state>
    </reg_access>
</reg_address>
    
  <reg_address
      external_access="False"
    mem_map_access="True"
      power_domain="None"
  >
    <reg_component>MPAM</reg_component>
    <reg_frame>MPAMF_BASE_rt</reg_frame>
    <reg_offset><hexnumber>0x0028</hexnumber></reg_offset>
    <reg_instance>MPAMF_IMPL_IDR_rt</reg_instance>
    <reg_access>
      
        
      <reg_access_state>
          <reg_access_level>When FEAT_RME is implemented and (FEAT_MPAMv1p0 is implemented or FEAT_MPAMv0p1 is implemented)</reg_access_level>
          <reg_access_type>RO</reg_access_type>
      </reg_access_state>
    </reg_access>
</reg_address>
    
  <reg_address
      external_access="False"
    mem_map_access="True"
      power_domain="None"
  >
    <reg_component>MPAM</reg_component>
    <reg_frame>MPAMF_BASE_rl</reg_frame>
    <reg_offset><hexnumber>0x0028</hexnumber></reg_offset>
    <reg_instance>MPAMF_IMPL_IDR_rl</reg_instance>
    <reg_access>
      
        
      <reg_access_state>
          <reg_access_level>When FEAT_RME is implemented and (FEAT_MPAMv1p0 is implemented or FEAT_MPAMv0p1 is implemented)</reg_access_level>
          <reg_access_type>RO</reg_access_type>
      </reg_access_state>
    </reg_access>
</reg_address>



          <reg_reset_value></reg_reset_value>

      <reg_mappings>
        




      </reg_mappings>

        <reg_purpose>
          
    
      <purpose_text>
        <para>Indicates the implementation-defined partitioning and monitoring features and parameters of the MSC.</para>
      </purpose_text>

        </reg_purpose>

      <reg_groups>
          <reg_group>MPAM</reg_group>
      </reg_groups>
      <reg_configuration>
        
    
      <configuration_text>
        <para>If <register_link state="ext" id="ext-mpamf_idr.xml">MPAMF_IDR</register_link>.HAS_RIS is 1, this register gives the implementation-specific features and parameters of the resource instance selected by <register_link state="ext" id="ext-mpamcfg_part_sel.xml">MPAMCFG_PART_SEL</register_link>.RIS for any features that are specific to the resource.</para>

      </configuration_text>
      <configuration_text>
        <para>If <xref linkend="#FEAT_MPAMv1p0">FEAT_MPAMv1p0</xref> or <xref linkend="#FEAT_MPAMv0p1">FEAT_MPAMv0p1</xref> is implemented, then the following statements apply:</para>

      </configuration_text>
      <configuration_text>
        <list type="unordered">
<listitem><content>
<para>MPAMF_IMPL_IDR_s indicates <arm-defined-word>IMPLEMENTATION DEFINED</arm-defined-word> partitioning and monitoring features accessed from the Secure MPAM feature page. </para>
</content>
</listitem><listitem><content>
<para>MPAMF_IMPL_IDR_ns indicates those accessed from the Non-secure MPAM feature page.</para>
</content>
</listitem><listitem><content>
<para>If <xref linkend="#FEAT_RME">FEAT_RME</xref> is implemented, then the following statements also apply:</para>
<list type="unordered">
<listitem><content>
<para>MPAMF_IMPL_IDR_rt indicates <arm-defined-word>IMPLEMENTATION DEFINED</arm-defined-word> partitioning and monitoring features accessed from the Root MPAM feature page.</para>
</content>
</listitem><listitem><content>
<para>MPAMF_IMPL_IDR_rl indicates those accessed from the Realm MPAM feature page.</para>
</content>
</listitem></list>
</content>
</listitem></list>

      </configuration_text>
      <configuration_text>
        <para>The power and reset domain of each MSC component is specific to that component.</para>
      </configuration_text>

      </reg_configuration>
      
      
        
      <reg_attributes>
          
    
      <attributes_text>
        <para>MPAMF_IMPL_IDR is a 32-bit register.</para>
      </attributes_text>

      </reg_attributes>
      <reg_fieldsets>
        






<fields id="fieldset_0" length="32">
  <text_before_fields/>
  <field id="fieldset_0-31_0-1" has_partial_fieldset="False" is_linked_to_partial_fieldset="False" is_access_restriction_possible="False" is_variable_length="False" is_constant_value="True" is_partial_field="False" is_conditional_field_name="True" reserved_type="RES0">
    <field_name>IMPLFEAT</field_name>
    <field_msb>31</field_msb>
    <field_lsb>0</field_lsb>
    <rel_range>31:0</rel_range>
    <field_description order="before"><para>All 32 bits of this register are available to be used as the implementer sees fit to indicate the presence of <arm-defined-word>IMPLEMENTATION DEFINED</arm-defined-word> MPAM features in this MSC and to give additional implementation-specific read-only information about the parameters of implementation-specific MPAM features to software.</para>
<para>If RIS is implemented, this register indicates the implementation-specific features and parameters of the resource instance selected by <register_link state="ext" id="ext-mpamcfg_part_sel.xml">MPAMCFG_PART_SEL</register_link>.RIS.</para></field_description>
    <field_description order="after">
      <para>This field has an <arm-defined-word>IMPLEMENTATION DEFINED</arm-defined-word> value.</para>
    </field_description>
    <field_access>
      <field_access_state>
        <field_access_type>RO</field_access_type>
      </field_access_state>
    </field_access>
    <fields_condition>When FEAT_MPAMv0p1 is implemented or FEAT_MPAMv1p1 is implemented</fields_condition>
  </field>
  <field id="fieldset_0-31_0-2" has_partial_fieldset="False" is_linked_to_partial_fieldset="False" is_access_restriction_possible="False" is_variable_length="False" is_constant_value="False" is_partial_field="False" is_conditional_field_name="True" reserved_type="RES0">
    <field_name>IMPLEMENTATION DEFINED</field_name>
    <field_msb>31</field_msb>
    <field_lsb>0</field_lsb>
    <rel_range>31:0</rel_range>
    <field_description order="before">
      <para>All 32 bits of this register are available to be used as the implementer sees fit to indicate the presence of <arm-defined-word>IMPLEMENTATION DEFINED</arm-defined-word> MPAM features in this MSC and to give additional implementation-specific read-only information about the parameters of implementation-specific MPAM features to software.</para>
    </field_description>
    <fields_condition>Otherwise</fields_condition>
  </field>
  <text_after_fields/>
</fields>




<reg_fieldset length="32">
  <fieldat id="fieldset_0-31_0-1" msb="31" lsb="0"/>
</reg_fieldset>


      </reg_fieldsets>

      <access_mechanisms>
          


  
    
      <access_permission_text>
        <para>If both <xref linkend="#FEAT_MPAM">FEAT_MPAM</xref> and <xref linkend="#FEAT_RME">FEAT_RME</xref> are implemented, the following statements apply:</para>

      </access_permission_text>
      <access_permission_text>
        <list type="unordered">
<listitem><content>
<para>In a system that supports Secure, Non-secure, Root, and Realm memory maps, there must be MPAM feature pages in all four address maps.</para>
</content>
</listitem><listitem><content>
<para>MPAMF_IMPL_IDR must be readable from the Non-secure, Secure, Root, and Realm MPAM feature pages.</para>
</content>
</listitem><listitem><content>
<para>MPAMF_IMPL_IDR is permitted to have the same contents when read from the Secure, Non-secure, Root, and Realm MPAM feature pages unless the register contents are different for the different versions:</para>
</content>
</listitem><listitem><content>
<para>MPAMF_IMPL_IDR_s is permitted to have either the same or different contents to MPAMF_IMPL_IDR_ns, MPAMF_IMPL_IDR_rt, or MPAMF_IMPL_IDR_rl.</para>
</content>
</listitem><listitem><content>
<para>MPAMF_IMPL_IDR_ns is permitted to have either the same or different contents to MPAMF_IMPL_IDR_rt or MPAMF_IMPL_IDR_rl.</para>
</content>
</listitem><listitem><content>
<para>MPAMF_IMPL_IDR_rt is permitted to have either the same or different contents to MPAMF_IMPL_IDR_rl.</para>
</content>
</listitem><listitem><content>
<para>There must be separate registers in the Secure (MPAMF_IMPL_IDR_s), Non-secure (MPAMF_IMPL_IDR_ns), Root (MPAMF_IMPL_IDR_rt), and Realm (MPAMF_IMPL_IDR_rl) MPAM feature pages.</para>
</content>
</listitem></list>

      </access_permission_text>
      <access_permission_text>
        <para>If any one of these features is implemented:</para>

      </access_permission_text>
      <access_permission_text>
        <list type="unordered">
<listitem><content>
<para><xref linkend="#FEAT_MPAMv0p1">FEAT_MPAMv0p1</xref></para>
</content>
</listitem><listitem><content>
<para><xref linkend="#FEAT_MPAMv1p1">FEAT_MPAMv1p1</xref></para>
</content>
</listitem></list>

      </access_permission_text>
      <access_permission_text>
        <para>then, the following statements apply:</para>

      </access_permission_text>
      <access_permission_text>
        <list type="unordered">
<listitem><content>When <register_link state="ext" id="ext-mpamf_idr.xml">MPAMF_IDR</register_link>.HAS_RIS is 1, MPAMF_IMPL_IDR shows the configuration of implementation-specific features for the  resource instance selected by <register_link state="ext" id="ext-mpamcfg_part_sel.xml">MPAMCFG_PART_SEL</register_link>.RIS. Fields that mention RIS in their field descriptions have values that track the implemented properties of the resource instance. Fields that do not mention RIS are constant across all resource instances.</content>
</listitem></list>
      </access_permission_text>





    
    
    
    

      </access_mechanisms>

      <arch_variants>
      </arch_variants>
  </register>
</registers>
<timestamp>2026-03-26 20:27:25</timestamp>
<commit_id>2026-03_rel</commit_id>
</register_page>