SPRUIU1C July 2020 – February 2024 DRA821U , DRA821U-Q1
Table 12-3458 lists the PCIE_CORE_EP_PF registers. All register offset addresses not listed in Table 12-3458 should be considered as reserved locations and the register contents should not be modified.
EP mode physical function (PF) PCIE core registers. There are 6 Physical Functions, which are assigned to function numbers 0 through 5.
Instance | Base Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0000h |
PCIE_CORE_PFn_I_VENDOR_ID_DEVICE_ID is shown in Figure 12-1267 and described in Table 12-2472.
Return to the Summary Table.
16-bit Vendor ID register and 16-bit Device ID register.
Offset = 0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0000h + formula |
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 |
DID | VID | ||||||||||||||||||||||||||||||
R/W-100h | R-17CDh | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | DID | R/W | 100h | Device ID assigned by the manufacturer of the device. On power-up, the Controller sets it to the value defined in the RTL file reg_defaults.h. This field can be rewritten independently for each Function from the local management bus. |
15-0 | VID | R | 17CDh | This is the Vendor ID assigned by PCI SIG to the manufacturer of the device. The Vendor ID is set in the Vendor ID Register within the local management register block. |
PCIE_CORE_PFn_I_COMMAND_STATUS is shown in Figure 12-1268 and described in Table 12-2474.
Return to the Summary Table.
16-bit Command Register and 16-bit Status Register.
Offset = 4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0004h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
DPE | SSE | RMA | RTA | STA | R6 | MDPE | |
R/W1C-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h | R-0h | R/W1C-0h | |
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R5 | CL | IS | R4 | ||||
R-0h | R-1h | R-0h | R-0h | ||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R3 | IMD | R2 | SE | ||||
R-0h | R/W-0h | R-0h | R/W-0h | ||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R1 | PERE | R0 | BE | MSE | ISE | ||
R-0h | R/W-0h | R-0h | R/W-0h | R/W-0h | R/W-0h | ||
LEGEND: R = Read Only; R/W = Read/Write; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | DPE | R/W1C | 0h | This bit is set when the Controller has received a poisoned TLP. The Parity Error Response enable bit [bit 6] has no effect on the setting of this bit. This field can also be cleared from the local management bus by writing a 1 into this bit position. |
30 | SSE | R/W1C | 0h | If the SERR enable bit is 1, this bit is set when the Controller has sent out a fatal or non-fatal error message on the link to the Root Complex. If the SERR enable bit is 0, this bit remains 0. This field can also be cleared from the local management bus by writing a 1 into this bit position. |
29 | RMA | R/W1C | 0h | This bit is set when the Controller has received a completion from the link with the Unsupported Request status. This field can also be cleared from the local management bus by writing a 1 into this bit position |
28 | RTA | R/W1C | 0h | This bit is set when the Controller has received a completion from the link with the Completer Abort status. This field can also be cleared from the local management bus by writing a 1 into this bit position |
27 | STA | R/W1C | 0h | This bit is set when the Controller has sent a completion to the link with the Completer Abort status. This field can also be cleared from the local management bus by writing a 1 into this bit position. |
26-25 | R6 | R | 0h | Reserved |
24 | MDPE | R/W1C | 0h | When the Parity Error Response enable bit is 1, the Controller sets this bit when it detects the following error conditions: [i] The Controller receives a poisoned completion from the link in response to a request. [ii] The Controller sends out a poisoned write request on the link [this may be because an underflow occurred during the packet transfer at the host interface of the Controller.]. This bit remains 0 when the Parity Error Response enable bit is 0. This field can also be cleared from the local management bus by writing a 1 into this bit position. |
23-21 | R5 | R | 0h | Reserved |
20 | CL | R | 1h | Indicates the presence of PCI Extended Capabilities registers. This bit is hardwired to 1. |
19 | IS | R | 0h | This bit is valid only when the Controller is configured to support legacy interrupts. Indicates that the Controller has a pending interrupt, that is, the Controller has sent an Assert_INTx message but has not transmitted a corresponding Deassert_INTx message. |
18-16 | R4 | R | 0h | Reserved |
15-11 | R3 | R | 0h | Reserved |
10 | IMD | R/W | 0h | Enables or disables the transmission of INTx Assert and De-assert messages from the Controller. Setting this bit to 1 disables generation of INTx assert/de-assert messages in the Controller. This field can be written from the local management bus. |
9 | R2 | R | 0h | Reserved |
8 | SE | R/W | 0h | Enables the reporting of fatal and non-fatal errors detected by the Controller to the Root Complex. This field can be written from the local management bus. |
7 | R1 | R | 0h | Reserved |
6 | PERE | R/W | 0h | When this bit is 1, the Controller sets the Master Data Parity Error status bit when it detects the following error conditions: [i] The Controller receives a poisoned completion from the link in response to a request. [ii] The Controller sends out a poisoned write request on the link [this may be because an underflow occurred during the packet transfer at the host interface of the Controller.]. When this bit is 0, the Master Data Parity Error status bit is never set. This field can be written from the local management bus. |
5-3 | R0 | R | 0h | Reserved |
2 | BE | R/W | 0h | Controls the ability of a Function to issue Memory and I/O Read/Write Requests, in the Upstream direction. . This field can be written from the local management bus. Note: The Controller does not gate any requests based on this bit. The Client Application logic must use this bit to gate requests as follows: - When this bit is Set, the Function is allowed to issue Memory or I/O Requests on the pcie_master_AXI interface. - When this bit is Clear, the Function must not allowed to issue any Memory or I/O Requests on the pcie_master_AXI interface. |
1 | MSE | R/W | 0h | Controls a Function's response to Memory Space accesses received from PCIe Link. The Controller internally uses this bit to respond to received Memort Requests as follows: - When this bit is Clear, all received Memory Space accesses are handled as Unsupported Requests. - When this bit is Set, all received Memory Space accesses are decoded and processed normally. This field can be written from the local management bus. |
0 | ISE | R/W | 0h | Controls a Function's response to IO Space accesses received from PCIe Link. The Controller internally uses this bit to respond to received IO Requests as follows: - When this bit is Clear, all received IO Space accesses are handled as Unsupported Requests. - When this bit is Set, all received IO Space accesses are decoded and processed normally. This field can be written from the local management bus. |
PCIE_CORE_PFn_I_REVISION_ID_CLASS_CODE is shown in Figure 12-1269 and described in Table 12-2476.
Return to the Summary Table.
This register contains the Revision ID and Class Code associated with the device
incorporating the PCIe Controller.
Offset = 8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0008h + formula |
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 |
CC | SCC | PIB | RID | ||||||||||||||||||||||||||||
R/W-0h | R/W-0h | R/W-0h | R/W-0h | ||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | CC | R/W | 0h | Identifies the function of the device. On power-up, the Controller sets it to the value defined in the RTL file reg_defaults.h. This field can be rewritten independently for each Function from the local management bus |
23-16 | SCC | R/W | 0h | Identifies a sub-category within the selected function. On power-up, the Controller sets it to the value defined in the RTL file reg_defaults.h. This field can be re-written independently for each Function from the local management bus. |
15-8 | PIB | R/W | 0h | Identifies the register set layout of the device. On power-up, the Controller sets it to the value defined in the RTL file reg_defaults.h. This field can be re-written independently for each Function from the local management bus. |
7-0 | RID | R/W | 0h | Assigned by the manufacturer of the device to identify the revision number of the device. On power-up, the Controller sets it to the value defined in the RTL file reg_defaults.h. This field can be re-written independently for each Function from the local management bus. |
PCIE_CORE_PFn_I_BIST_HEADER_LATENCY_CACHE_LINE is shown in Figure 12-1270 and described in Table 12-2478.
Return to the Summary Table.
This location contains the BIST, header-type, Latency Timer and Cache Line Size
Registers.
Offset = Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 000Ch + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
BR | DT | HT | |||||||||||||
R/W-0h | R-1h | R-0h | |||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
LT | CLS | ||||||||||||||
R-0h | R/W-0h | ||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | BR | R/W | 0h | BIST control register.It can be accessed using local management bus. This is a sticky field. |
23 | DT | R | 1h | Identifies whether the device supports a single Function or multiple Functions. This bit is read as 0 when only Function 0 has been enabled in the Physical Function Configuration Register [in the local management block], and as 1 when more than one Function has been enabled. |
22-16 | HT | R | 0h | Identifies format of header. This field is hardwired to 0. |
15-8 | LT | R | 0h | This is an unused field and is hardwired to 0. |
7-0 | CLS | R/W | 0h | Cache Line Size Register defined in PCI Specifications 3.0. This field can be read or written, both from the link and from the local management bus, but its value is not used. |
PCIE_CORE_PFn_I_BASE_ADDR_0 is shown in Figure 12-1271 and described in Table 12-2480.
Return to the Summary Table.
This is one of the six Base Address Registers defined by the PCI
Specifications 3.0. These registers are used to define address ranges for memory and I/O
accesses to the Endpoint device. During the initial configuration of the device, the configuration
program determines the size of
the address range defined by the BAR by writing a pattern of all 1s into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned
value. A value of 0 is returned by the Controller if BAR 0 is not configured. Otherwise, the number of
1s returned is based on the size of the BAR. BAR0 can be setup as 32-bit memory or IO BAR, or
can be paired with BAR 1 to form a 64bit memory BAR. The settings of this BAR is defined in the
BAR Configuration Register associated with this PF.
The BAR aperture can be controller in two different ways:
(i) When the Resizable BAR Capability is enabled, the aperture is
controlled by the setting of the BAR width field in Resizable BAR Control Register.
The Resizable BAR Capability is enabled by setting the Enable Resizable BAR
Capability bit (bit 31) of the associated Physical Function BAR Configuration Register 1.
(ii) When the Resizable BAR Capability is disabled for the Physical
Function, the aperture is controlled by the setting of the PF BAR
Configuration Register.
Offset = 10h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0010h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
BAMRW | |||||||
R/W-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
BAMRW | |||||||
R/W-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
BAMRW | BAMR0 | ||||||
R/W-0h | R-0h | ||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R8 | P0 | S0 | R7 | MSI0 | |||
R-0h | R-0h | R-0h | R-0h | R-0h | |||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-12 | BAMRW | R/W | 0h | This field defines the base address of the memory address range. The number of implemented bits in this field determines the BAR aperture configured in BAR Configuration Registers of the associated Physical Function. |
11-8 | BAMR0 | R | 0h | This field defines the base address of the memory address range. The number of implemented bits in this field determines the BAR aperture configured in BAR Configuration Registers of the associated Physical Function. All other bits are not writeable, and are read as 0's. |
7-4 | R8 | R | 0h | These bits are hardwired to 0 |
3 | P0 | R | 0h | When the BAR is used to define a memory address range, this field declares whether data from the address range is prefetchable [0 = non-prefetchable, 1 = prefetchable]. The value read in this field is determined by the setting of BAR Configuration Registers of the associated Physical Function |
2 | S0 | R | 0h | When the BAR is used to define a memory address range, this field indicates whether the address range is 32-bit or 64-bit [0 = 32-bit, 1 = 64 bit]. For 64-bit address ranges, the value in BAR 1 is treated as a continuation of the base address in BAR 0. The value read in this field is determined by the setting of BAR Configuration Registers of the associated Physical Function. |
1 | R7 | R | 0h | This bit is hardwired to 0 for both memory and I/O BARs. |
0 | MSI0 | R | 0h | Specifies whether this BAR defines a memory address range or an I/O address range [0 = memory, 1 = I/O]. The value read in this field is determined by the setting of BAR Configuration Registers of the associated Physical Function |
PCIE_CORE_PFn_I_BASE_ADDR_1 is shown in Figure 12-1272 and described in Table 12-2482.
Return to the Summary Table.
This is one of the six Base Address Registers defined by the PCI
Specifications 3.0. BAR1 can be setup as 32-bit memory or IO BAR, or
can be paired with BAR 0 to form a 64bit memory BAR.
This register can be used in two distinct ways: (i) When BAR 0 defines a 64-bit memory address range,
this register is used to define the high-order bits of the base address. The number of writable bits
in this field is based on the aperture setting of the BAR. (ii) When the BAR 0 is
used to define a 32-bit memory address range or an I/O address range, this register can be used
to define a new 32-bit memory address range or an I/O address range. The individual fields in
the register have the same format as those of BAR 0 and is described below. The settings of this BAR
is defined in the BAR Configuration Register associated with this PF.
When configured as a 32-bit memory or IO BAR, the BAR aperture can be controller in two different ways:
(a) When the Resizable BAR Capability is enabled, the aperture is
controlled by the setting of the BAR width field in Resizable BAR Control Register 1.
The Resizable BAR Capability is enabled by setting the Enable Resizable BAR
Capability bit (bit 31) of the associated Physical Function BAR Configuration Register.
(b) When the Resizable BAR Capability is disabled for the Physical
Function, the aperture is controlled by the setting of the Physical Function BAR
Configuration Register.
Offset = 14h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0014h + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_I_BASE_ADDR_2 is shown in Figure 12-1273 and described in Table 12-2484.
Return to the Summary Table.
This is one of the six Base Address Registers defined by the PCI
Specifications 3.0. These registers are used to define address ranges for memory and I/O
accesses to the Endpoint device. During the initial configuration of the device, the configuration
program determines the size of
the address range defined by the BAR by writing a pattern of all 1s into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned
value. A value of 0 is returned by the Controller if BAR 2 is not configured. Otherwise, the number of
1s returned is based on the size of the BAR. BAR2 can be setup as 32-bit memory or IO BAR, or
can be paired with BAR 3 to form a 64bit memory BAR. The settings of this BAR is defined in the
BAR Configuration Register associated with this PF.
The BAR aperture can be controller in two different ways:
(i) When the Resizable BAR Capability is enabled, the aperture is
controlled by the setting of the BAR width field in Resizable BAR Control Register.
The Resizable BAR Capability is enabled by setting the Enable Resizable BAR
Capability bit (bit 31) of the associated Physical Function BAR Configuration Register 1.
(ii) When the Resizable BAR Capability is disabled for the Physical
Function, the aperture is controlled by the setting of the PF BAR
Configuration Register.
Offset = 18h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0018h + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_I_BASE_ADDR_3 is shown in Figure 12-1274 and described in Table 12-2486.
Return to the Summary Table.
This is one of the six Base Address Registers defined by the PCI
Specifications 3.0. BAR3 can be setup as 32-bit memory or IO BAR, or
can be paired with BAR 2 to form a 64bit memory BAR.
This register can be used in two distinct ways: (i) When BAR 2 defines a 64-bit memory address range,
this register is used to define the high-order bits of the base address. The number of writable bits
in this field is based on the aperture setting of the BAR. (ii) When the BAR 2 is
used to define a 32-bit memory address range or an I/O address range, this register can be used
to define a new 32-bit memory address range or an I/O address range. The individual fields in
the register have the same format as those of BAR 2 and is described below. The settings of this BAR
is defined in the BAR Configuration Register associated with this PF.
When configured as a 32-bit memory or IO BAR, the BAR aperture can be controller in two different ways:
(a) When the Resizable BAR Capability is enabled, the aperture is
controlled by the setting of the BAR width field in Resizable BAR Control Register 3.
The Resizable BAR Capability is enabled by setting the Enable Resizable BAR
Capability bit (bit 31) of the associated Physical Function BAR Configuration Register.
(b) When the Resizable BAR Capability is disabled for the Physical
Function, the aperture is controlled by the setting of the Physical Function BAR
Configuration Register.
Offset = 1Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 001Ch + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_I_BASE_ADDR_4 is shown in Figure 12-1275 and described in Table 12-2488.
Return to the Summary Table.
This is one of the six Base Address Registers defined by the PCI
Specifications 3.0. These registers are used to define address ranges for memory and I/O
accesses to the Endpoint device. During the initial configuration of the device, the configuration
program determines the size of
the address range defined by the BAR by writing a pattern of all 1s into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned
value. A value of 0 is returned by the Controller if BAR 4 is not configured. Otherwise, the number of
1s returned is based on the size of the BAR. BAR4 can be setup as 32-bit memory or IO BAR, or
can be paired with BAR 5 to form a 64bit memory BAR. The settings of this BAR is defined in the
BAR Configuration Register associated with this PF.
The BAR aperture can be controller in two different ways:
(i) When the Resizable BAR Capability is enabled, the aperture is
controlled by the setting of the BAR width field in Resizable BAR Control Register.
The Resizable BAR Capability is enabled by setting the Enable Resizable BAR
Capability bit (bit 31) of the associated Physical Function BAR Configuration Register 1.
(ii) When the Resizable BAR Capability is disabled for the Physical
Function, the aperture is controlled by the setting of the PF BAR
Configuration Register.
Offset = 20h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0020h + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_I_BASE_ADDR_5 is shown in Figure 12-1276 and described in Table 12-2490.
Return to the Summary Table.
This is one of the six Base Address Registers defined by the PCI
Specifications 3.0. BAR5 can be setup as 32-bit memory or IO BAR, or
can be paired with BAR 4 to form a 64bit memory BAR.
This register can be used in two distinct ways: (i) When BAR 4 defines a 64-bit memory address range,
this register is used to define the high-order bits of the base address. The number of writable bits
in this field is based on the aperture setting of the BAR. (ii) When the BAR 4 is
used to define a 32-bit memory address range or an I/O address range, this register can be used
to define a new 32-bit memory address range or an I/O address range. The individual fields in
the register have the same format as those of BAR 4 and is described below. The settings of this BAR
is defined in the BAR Configuration Register associated with this PF.
When configured as a 32-bit memory or IO BAR, the BAR aperture can be controller in two different ways:
(a) When the Resizable BAR Capability is enabled, the aperture is
controlled by the setting of the BAR width field in Resizable BAR Control Register 5.
The Resizable BAR Capability is enabled by setting the Enable Resizable BAR
Capability bit (bit 31) of the associated Physical Function BAR Configuration Register.
(b) When the Resizable BAR Capability is disabled for the Physical
Function, the aperture is controlled by the setting of the Physical Function BAR
Configuration Register.
Offset = 24h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0024h + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_RSVD_0A is shown in Figure 12-1277 and described in Table 12-2492.
Return to the Summary Table.
Reserved
Offset = 28h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0028h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_SUBSYSTEM_VENDOR_ID_SUBSYSTEM_I is shown in Figure 12-1278 and described in Table 12-2494.
Return to the Summary Table.
This register contains the Subsystem Vendor ID and Subsystem ID associated with the
device incorporating the PCIe Controller.
Offset = 2Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 002Ch + formula |
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 |
SID | SVID | ||||||||||||||||||||||||||||||
R/W-0h | R-17CDh | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | SID | R/W | 0h | Specifies the Subsystem ID assigned by the manufacturer of the device. On power-up, the Controller sets it to the value defined in the RTL file reg_defaults.h. This field can be re-written independently for each Function from the local management bus. |
15-0 | SVID | R | 17CDh | Specifies the Subsystem Vendor ID assigned by the PCI SIG to the manufacturer of the device. Its value comes fom the Subsystem Vendor ID Register in the local management register block. |
PCIE_CORE_PFn_RSVD_0C is shown in Figure 12-1279 and described in Table 12-2496.
Return to the Summary Table.
Reserved
Offset = 30h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0030h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_CAPABILITIES_POINTER is shown in Figure 12-1280 and described in Table 12-2498.
Return to the Summary Table.
This location contains the pointer to the first PCI Capabilities Structure. Its default
value points to the Power Management Capability Structure (register number 0x80 hex).
Offset = 34h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0034h + formula |
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 |
R15 | CP | ||||||||||||||||||||||||||||||
R-0h | R/W-80h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-8 | R15 | R | 0h | Reserved |
7-0 | CP | R/W | 80h | Contains pointer to the first PCI Capability Structure. This field is set by default to the value defined in the RTL file reg_defaults.h. It can be re-written independently for every Function from the local management bus. |
PCIE_CORE_PFn_RSVD_0E is shown in Figure 12-1281 and described in Table 12-2500.
Return to the Summary Table.
Reserved
Offset = 38h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0038h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_INTRPT_LINE_INTRPT_PIN is shown in Figure 12-1282 and described in Table 12-2502.
Return to the Summary Table.
This location contains the PCI 3.0 Interrupt Line and Interrupt Pin Registers. These
registers are used only when the Controller is configured to support PCI legacy interrupts. If the
legacy interrupt mode is configured, the Controller receives interrupt indications from the client
logic on its INTA_IN, INTB_IN, INTC_IN and INTD_IN inputs, and sends out Assert_INTx or
Deassert_INTx messages on the link in response to their activation or deactivation,
respectively. The Interrupt Pin Register defines which of the four inputs is connected to the
Function corresponding to this register set. The Interrupt Line register defines the input of
the interrupt controller (IRQ0 - IRQ15) in the Root Complex that is activated by each
Assert_INTx message.
Offset = 3Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 003Ch + formula |
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 |
R16 | IPR | ILR | |||||||||||||||||||||||||||||
R-0h | R/W-1h | R/W-FFh | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-11 | R16 | R | 0h | Reserved |
10-8 | IPR | R/W | 1h | Identifies the interrupt input [A, B, C, D] to which this Functions interrupt output is connected to [01 = INTA, 02 = INTB, 03 = INTC, 04 = INTD]. The assignment of interrupt inputs to Functions is fixed when the Controller is configured. This field can be re-written independently for each Function from the local management bus. Please see the define macros den_db_Fx_INTR_PIN values [where x is the function number] for default values of each function in the reg_defaults.v files. |
7-0 | ILR | R/W | FFh | Identifies the IRQx input of the interrupt controller at the Root Complex that is activated by this Functions interrupt [00 = IRQ0, ... , 0F = IRQ15, FF = unknown or not connected]. This field is writable from the local management bus. Please see the define macros den_db_Fx_INTR_LINE values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_RSVD_010_01F is shown in Figure 12-1283 and described in Table 12-2504.
Return to the Summary Table.
Reserved
Offset = 40h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0040h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_PWR_MGMT_CAP is shown in Figure 12-1284 and described in Table 12-2506.
Return to the Summary Table.
This location contains the Power Management Capabilities Register, its Capability ID,
and a pointer to the next capability. This version of the Controller supports the PCI power states D0
,D1 and D3.
Offset = 80h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0080h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
PSDCS | PSDHS | PSD2S | PSD1S | PSD0S | D2S | D1S | MCRAPS |
R-0h | R/W-1h | R-0h | R/W-1h | R/W-1h | R-0h | R/W-1h | R-0h |
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
MCRAPS | DSI | R0 | PC | VID | |||
R-0h | R-0h | R-0h | R-0h | R/W-3h | |||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
CP | |||||||
R/W-90h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
CID | |||||||
R/W-1h | |||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | PSDCS | R | 0h | Indicates whether the Function is capable of sending PME messages when in the D3cold state. Because the device does not have aux power, this bit is hardwired to 0. |
30 | PSDHS | R/W | 1h | Indicates whether the Function is capable of sending PME messages when in the D3hot state. This bit is set to 1 by default, but can be modified from the local management bus by writing into Function 0. All other Functions assume the value set in Function 0s Power Management Capabilities Register. |
29 | PSD2S | R | 0h | Indicates whether the Function is capable of sending PME messages when in the D2 state. This bit is hardwired to 0 because D2 state is not supported. |
28 | PSD1S | R/W | 1h | Indicates whether the Function is capable of sending PME messages when in the D1 state. This bit can be modified from the local management bus by writing into Function 0. All other Functions assume the value set in Function 0s Power Management Capabilities Register. |
27 | PSD0S | R/W | 1h | Indicates whether the Function is capable of sending PME messages when in the D0 state. This bit is set to 1 by default, but can be modified from the local management bus by writing into Function 0. All other Functions assume the value set in Function 0s Power Management Capabilities Register. |
26 | D2S | R | 0h | Set if the Function supports the D2 power state. Currently hardwired to 0. |
25 | D1S | R/W | 1h | Set if the Function supports the D1 power state. This bit can be modified from the local management bus by writing into Function 0. All other Functions assume the value set in Function 0s Power Management Capabilities Register. |
24-22 | MCRAPS | R | 0h | Specifies the maximum current drawn by the device from the aux power source in the D3cold state. This field is not implemented in devices not supporting PME notification when in the D3cold state, and is therefore hardwired to 0. |
21 | DSI | R | 0h | This bit, when set, indicates that the device requires additional configuration steps beyond setting up its PCI configuration space, to bring it to the D0 active state from the D0 uninitialized state. This bit is hardwired to 0. |
20 | R0 | R | 0h | Reserved |
19 | PC | R | 0h | Not applicable to PCI Express. This bit is hardwired to 0. |
18-16 | VID | R/W | 3h | Indicates the version of the PCI Bus Power Management Specifications that the Function implements. This field is set by default to 011 [Version 1.2]. It can be re-written independently for each Function from the local management bus. |
15-8 | CP | R/W | 90h | Contains pointer to the next PCI Capability Structure. The Controller sets it to the value defined in the RTL file reg_defaults.h. This field can be re-written independently for each Function from the local management bus. |
7-0 | CID | R/W | 1h | Identifies that the capability structure is for Power Management. This field is set by default to 01 hex. It can be re-written independently for each Function from the local management bus. |
PCIE_CORE_PFn_I_PWR_MGMT_CTRL_STAT_REP is shown in Figure 12-1285 and described in Table 12-2508.
Return to the Summary Table.
This location contains the Power Management Control/Status and Data Registers.
Offset = 84h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0084h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
DR | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R1 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
PMES | R2 | PE | |||||
R/W-0h | R-0h | R/W-0h | |||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R3 | NSR | R4 | PS | ||||
R-0h | R/W-1h | R-0h | R/W-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | DR | R | 0h | This optional register is not implemented in the PCIe Controller. This field is hardwired to 0. |
23-16 | R1 | R | 0h | Reserved |
15 | PMES | R/W | 0h | When PME notification is enabled, writing a 1 into this bit position from the local management bus sets this bit and causes the Controller to send a PME message from the associated Function. When the Root Complex processes this message, it will turn off this bit by writing a 1 into this bit position through a Config Write. This bit can be set or cleared from the local management bus, by writing a 1 or 0, respectively. It can only be cleared from the configuration path [by writing a 1]. This is a sticky field. |
14-9 | R2 | R | 0h | Reserved |
8 | PE | R/W | 0h | Setting this bit enables the notification of PME events from the associated Function. This bit can be set also by writing into this register from the local management bus. This is a sticky field. |
7-4 | R3 | R | 0h | Reserved |
3 | NSR | R/W | 1h | When this bit is set to 1, the Function will maintain all its state in the PM state D3hot. The software is not required to re-initialize the Function registers on the transition back to D0. This bit is set to 1 by default, but can be modified independently for each PF from the local management bus. |
2 | R4 | R | 0h | Reserved |
1-0 | PS | R/W | 0h | Indicates the power state this Function is currently in. This field can be read by the software to monitor the current power state, or can be written to cause a transition to a new state. The valid settings are 00 [state D0], 01 [state D1] and 11 [state D3hot]. The software should not write any other value into this field. This field can also be written from the local management bus independently for each Function. |
PCIE_CORE_PFn_RSVD_022_023 is shown in Figure 12-1286 and described in Table 12-2510.
Return to the Summary Table.
Reserved
Offset = 88h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0088h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_MSI_CTRL_REG is shown in Figure 12-1287 and described in Table 12-2512.
Return to the Summary Table.
This register is used only when the Controller is configured to support Message Signaled
Interrupts (MSIs). In addition to the MSI control bits, this location also contains the
Capability ID for MSI and the pointer to the next PCI Capability Structure.
Offset = 90h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0090h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R0 | MC | ||||||
R-0h | R/W-1h | ||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
BAC64 | MME | MMC | ME | ||||
R/W-1h | R/W-0h | R/W-0h | R/W-0h | ||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
CP1 | |||||||
R/W-B0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
CID1 | |||||||
R-5h | |||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-25 | R0 | R | 0h | Reserved |
24 | MC | R/W | 1h | can be modified using localmanagement interface |
23 | BAC64 | R/W | 1h | Set to 1 to indicate that the device is capable of generating 64-bit addresses for MSI messages.Can be modified using local management interface |
22-20 | MME | R/W | 0h | Encodes the number of distinct messages that the Controller is programmed to generate for this Function [000 = 1, 001 = 2, 010 = 4, 011 = 8, 100 = 16, 101 = 32]. This setting must be based on the number of interrupt inputs of the Controller that are actually used by this Function. This field can be written from the local management bus. |
19-17 | MMC | R/W | 0h | Encodes the number of distinct messages that the Controller is capable of generating for this Function [000 = 1, 001 = 2, 010 = 4, 011 = 8, 100 = 16, 101 = 32]. Thus, this field defines the number of the interrupt vectors for this Function. The Controller allows up to 32 distinct messages, but the setting of this field must be based on the number of interrupt inputs of the Controller that are actually used by the client. For example, if the client logic uses 8 of the 32 distinct MSI interrupt inputs of the Controller for this Function, then the value of this field must be set to 011. This field can be written from the local management bus. Please see the define den_db_Fx_MSI_MULTIPLE_MSG_CAPABLE values [where x is the function number] for default values of each function in the reg_defaults.v files. |
16 | ME | R/W | 0h | Set by the configuration program to enable the MSI feature. This field can also be written from the local management bus. |
15-8 | CP1 | R/W | B0h | Pointer to the next PCI Capability Structure. This can be modified from the local management bus. This field can be written from the local management bus. |
7-0 | CID1 | R | 5h | Specifies that the capability structure is for MSI. Hardwired to 05 hex. |
PCIE_CORE_PFn_I_MSI_MSG_LOW_ADDR is shown in Figure 12-1288 and described in Table 12-2514.
Return to the Summary Table.
This register contains the first 32 bits of the address to be used in the MSI messages
generated by the Controller for this Function. This address is taken as a 32-bit address if the value
programmed in the MSI Message High Address Register is 0. Otherwise, this address is taken as
the least significant 32 bits of the 64-bit address sent in MSI messages.
Offset = 94h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0094h + formula |
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 |
MAL | R1 | ||||||||||||||||||||||||||||||
R/W-0h | R-0h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-2 | MAL | R/W | 0h | Lower bits of the address to be used in MSI messages. This field can also be written from the local management bus. |
1-0 | R1 | R | 0h | The two lower bits of the address are hardwired to 0 to align the address on a double-word boundary. |
PCIE_CORE_PFn_I_MSI_MSG_HI_ADDR is shown in Figure 12-1289 and described in Table 12-2516.
Return to the Summary Table.
This register contains the most significant 32 bits of the 64-bit address sent by the
Controller in MSI messages. A value of all zeroes in this register is taken to mean that the Controller
should use 32-bit addresses in the messages.
Offset = 98h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0098h + formula |
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 |
MAH | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | MAH | R/W | 0h | Contains bits 63:32 of the 64-bit address to be used in MSI Messages. A value of 0 specifies that 32-bit addresses are to be used in the messages. This field can also be written from the local management bus. |
PCIE_CORE_PFn_I_MSI_MSG_DATA is shown in Figure 12-1290 and described in Table 12-2518.
Return to the Summary Table.
This register contains the write data to be used in the MSI messages to be generated for
the associated PCI Function. When the number of distinct messages programmed in the MSI Control
Register is 1, the 32-bit value from this register is used as the data value in the MSI packets
generated by the Controller for this Function. If the number of distinct messages is more than 1, the
least significant bits of the programmed value are replaced with the encoded interrupt vector
[31:0] of the specific message to generate the write data value for the message.
Offset = 9Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 009Ch + formula |
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 |
R2 | MD | ||||||||||||||||||||||||||||||
R-0h | R/W-0h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | R2 | R | 0h | Hardwired to 0 |
15-0 | MD | R/W | 0h | Message data to be used for this Function. This field can also be written from the local management bus. |
PCIE_CORE_PFn_I_MSI_MASK is shown in Figure 12-1291 and described in Table 12-2520.
Return to the Summary Table.
This register contains the MSI mask bits, one for each of the interrupt levels.
Offset = A0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00A0h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | MM | ||||||||||||||
R-0h | R/W-0h | ||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-1 | R0 | R | 0h | Please note that if the Multiple Message Capable field is changed from the local management APBbus, then the width of this field also changes correspondingly |
0 | MM | R/W | 0h | Mask bits for MSI interrupts. The Multiple Message Capable field of the MSI Control Register specifies the number of distinct interrupts for the Function, which determines the number of valid mask bits. Please note that if the Multiple Message Capable field is changed from the local management APBbus, then the width of the MSI Mask field also changes correspondingly |
PCIE_CORE_PFn_I_MSI_PENDING_BITS is shown in Figure 12-1292 and described in Table 12-2522.
Return to the Summary Table.
This register contains the MSI pending interrupt bits, one for each of the interrupt
levels.
Offset = A4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00A4h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | MP | ||||||||||||||
R-0h | R/W-0h | ||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-1 | R0 | R | 0h | Please note that if the Multiple Message Capable field is changed from the local management APBbus, then the width of this field also changes correspondingly |
0 | MP | R/W | 0h | Pending bits for MSI interrupts. This field can be written from either the APB interface or the MSI_PENDING_STATUS_IN inputs of the Controller depending on the MSI Pending Status In Mode select Bit in the Local Management space. The Multiple Message Capable field of the MSI Control Register specifies the number of distinct interrupts for the Function, which determines the number of valid pending bits. Please note that if the Multiple Message Capable field is changed from the local management APBbus, then the width of the MSI Pending Bits field also changes correspondingly |
PCIE_CORE_PFn_RSVD_02A_02B is shown in Figure 12-1293 and described in Table 12-2524.
Return to the Summary Table.
Reserved
Offset = A8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00A8h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_MSIX_CTRL is shown in Figure 12-1294 and described in Table 12-2526.
Return to the Summary Table.
This register contains the MSI-X configuration bits, the Capability ID for MSI-X and the
pointer to the next PCI Capability Structure.
Offset = B0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00B0h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
MSIXE | FM | R0 | MSIXTS | ||||
R/W-0h | R/W-0h | R-0h | R/W-0h | ||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
MSIXTS | |||||||
R/W-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
CP | |||||||
R/W-C0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
CID | |||||||
R/W-11h | |||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | MSIXE | R/W | 0h | Set by the configuration program to enable the MSI-X feature. This field can also be written from the local management bus. |
30 | FM | R/W | 0h | This bit serves as a global mask to all the interrupt conditions associated with this Function. When this bit is set, the Controller will not send out MSI-X messages from this Function. This field can also be written from the local management bus. |
29-27 | R0 | R | 0h | Reserved |
26-16 | MSIXTS | R/W | 0h | Specifies the size of the MSI-X Table, that is, the number of interrupt vectors defined for the Function. The programmed value is 1 minus the size of the table [that is, this field is set to 0 if the table size is 1.]. It can be re-written independently for each Function from the local management bus. Please see the define den_db_Fx_MSIX_TABLE_SIZE values [where x is the function number] for default values of each function in the reg_defaults.v files. |
15-8 | CP | R/W | C0h | Contains pointer to the next PCI Capability Structure. This is set to point to the PCI Express Capability Structure at 30 hex. This can be rewritten independently for each Function from the local management bus. |
7-0 | CID | R/W | 11h | Identifies that the capability structure is for MSI-X. This field is set by default to 11 hex. It can be rewritten independently for each Function from the local management bus. |
PCIE_CORE_PFn_I_MSIX_TBL_OFFSET is shown in Figure 12-1295 and described in Table 12-2528.
Return to the Summary Table.
This register is used to specify the location of the MSI-X Table in memory. All the 32
bits of this register can be re-written independently for each Function from the local
management bus.
Offset = B4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00B4h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
TO | |||||||||||||||
R/W-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
TO | BARI | ||||||||||||||
R/W-0h | R/W-0h | ||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-3 | TO | R/W | 0h | Offset of the memory address where the MSI-X Table is located, relative to the selected BAR. The three least significant bits of the address are omitted, as the addresses are QWORD aligned. Please see the define den_db_Fx_MSIX_TABLE_OFFSET values [where x is the function number] for default values of each function in the reg_defaults.v files. |
2-0 | BARI | R/W | 0h | Identifies the BAR corresponding to the memory address range where the MSI-X Table is located [000 = BAR 0, 001 = BAR 1, ... , 101 = BAR 5]. Please see the define den_db_Fx_MSIX_TABLE_BIR values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_MSIX_PENDING_INTRPT is shown in Figure 12-1296 and described in Table 12-2530.
Return to the Summary Table.
This register is used to specify the location of the MSI-X Pending Bit Array (PBA). The
PBA is a structure in memory containing the pending interrupt bits. All the 32 bits of this
register can be rewritten independently for each Function from the local management bus.
Offset = B8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00B8h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
PBAO | |||||||||||||||
R/W-1h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
PBAO | BARI1 | ||||||||||||||
R/W-1h | R/W-0h | ||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-3 | PBAO | R/W | 1h | Offset of the memory address where the PBA is located, relative to the selected BAR. The three least significant bits of the address are omitted, as the addresses are QWORD aligned. Please see the define den_db_Fx_MSIX_PBA_OFFSET values [where x is the function number] for default values of each function in the reg_defaults.v files. |
2-0 | BARI1 | R/W | 0h | Identifies the BAR corresponding to the memory address range where the PBA Structure is located [000 = BAR 0, 001 = BAR 1, ... , 101 = BAR 5]. The value programmed must be the same as the BAR Indicator configured in the MSI-X Table Offset Register.Identifies the BAR corresponding to the memory address range where the PBA Structure is located [000 = BAR 0, 001 = BAR 1, ... , 101 = BAR 5]. The value programmed must be the same as the BAR Indicator configured in the MSI-X Table Offset Register. Please see the define den_db_Fx_MSIX_PBA_BIR values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_RSVD_02F is shown in Figure 12-1297 and described in Table 12-2532.
Return to the Summary Table.
Reserved
Offset = BCh + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00BCh + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_PCIE_CAP_LIST is shown in Figure 12-1298 and described in Table 12-2534.
Return to the Summary Table.
This location identifies the PCI Express device type and its capabilities. It also
contains the Capability ID for the PCI Express Structure and the pointer to the next capability
structure.
Offset = C0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00C0h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | TRS | IMN | SS | DT | PCV | ||||||||||
R-0h | R-0h | R-0h | R-0h | R-0h | R/W-2h | ||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
NCP | CID | ||||||||||||||
R-0h | R-10h | ||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | R0 | R | 0h | Reserved |
30 | TRS | R | 0h | When set to 1, this bit indicates that the device supports routing of Trusted Configuration Requests. Not valid for Endpoints. Hardwired to 0. |
29-25 | IMN | R | 0h | Identifies the MSI or MSI-X interrupt vector for the interrupt message generated corresponding to the status bits in the Slot Status Register, Root Status Register, or this capability structure. This field must be defined based on the chosen interrupt mode - MSI or MSI-X. This field is hardwired to 0. |
24 | SS | R | 0h | Set to 1 when the link connected to a slot. Hardwired to 0. |
23-20 | DT | R | 0h | Indicates the type of device implementing this Function. This field is hardwired to 0 in the EP mode. |
19-16 | PCV | R/W | 2h | Identifies the version number of the capability structure. This field is set to 2 by default to indicate that the Controller is compatible to PCI Express Base Specification Revision 3.0. This field can be modified through local management interface. |
15-8 | NCP | R | 0h | Points to the next PCI capability structure. Set to 0 because this is the last capability structure. |
7-0 | CID | R | 10h | Specifies Capability ID assigned by PCI SIG for this structure. This field is hardwired to 10 hex. |
PCIE_CORE_PFn_I_PCIE_DEV_CAP is shown in Figure 12-1299 and described in Table 12-2536.
Return to the Summary Table.
This register advertises the capabilities of the PCI Express device encompassing this
Function.
Offset = C4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00C4h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R3 | FC | CPLS | CSPLV | ||||
R-0h | R/W-1h | R/W-0h | R/W-0h | ||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
CSPLV | R2 | ||||||
R/W-0h | R-0h | ||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RBER | R1 | AL1SL | AL0SL | ||||
R/W-1h | R-0h | R/W-0h | R/W-4h | ||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
AL0SL | ETFS | PFS | MPS | ||||
R/W-4h | R-0h | R-0h | R/W-1h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-29 | R3 | R | 0h | Reserved |
28 | FC | R/W | 1h | Set when device has Function-Level Reset capability. It is set by default to 1. It can be re-written independently for each Function from the local management bus. |
27-26 | CPLS | R/W | 0h | Specifies the scale used by Slot Power Limit Value. It is set by default to the value define in reg_defaults.h. It can be re-written independently for each Function from the local management bus. |
25-18 | CSPLV | R/W | 0h | Specifies upper limit on power supplied by slot. It is set by default to the value define in reg_defaults.h. It can be re-written independently for each Function from the local management bus. |
17-16 | R2 | R | 0h | Reserved |
15 | RBER | R/W | 1h | Enables role-based error reporting. It is hardwired to 1.It can be re-written independently for each Function from the local management bus. |
14-12 | R1 | R | 0h | Reserved |
11-9 | AL1SL | R/W | 0h | Specifies acceptable latency that the Endpoint can tolerate while transitioning from L1 to L0. It is set by default to the value define in reg_defaults.h. It can be re-written independently for each Function from the local management bus. |
8-6 | AL0SL | R/W | 4h | Specifies acceptable latency that the Endpoint can tolerate while transitioning from L0S to L0. It is set by default to the value define in reg_defaults.h. It can be re-written independently for each Function from the local management bus. |
5 | ETFS | R | 0h | Extended Tag Field not Supported. Hard coded to 0. |
4-3 | PFS | R | 0h | This field is used to extend the tag field by combining unused Function bits with the tag bits. This field is hardwired to 00 to disable this feature. |
2-0 | MPS | R/W | 1h | Specifies maximum payload size supported by the device. |
PCIE_CORE_PFn_I_PCIE_DEV_CTRL_STATUS is shown in Figure 12-1300 and described in Table 12-2538.
Return to the Summary Table.
This register contains control and status bits associated with the device implementing
this Function. All the read-write bits in this register can also be written from the local
management bus. Likewise, bits designated as RW1C can also be cleared by writing a 1 from the
local management bus.
Offset = C8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00C8h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R4 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R4 | TP | APD | URD | FED | NFED | CED | |
R-0h | R-0h | R-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h | |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
FLR | MRRS | ENS | EAP | EPH | ETFE | ||
R/W-0h | R/W-2h | R/W-1h | R-0h | R-0h | R-0h | ||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
MPS | ERO | EURR | EFER | ENFER | ECER | ||
R/W-0h | R/W-1h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | ||
LEGEND: R = Read Only; R/W = Read/Write; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-22 | R4 | R | 0h | Reserved |
21 | TP | R | 0h | Indicates if any of the Non-Posted requests issued by the Function are still pending. |
20 | APD | R | 0h | Set when auxiliary power is detected by the device. This is an unused field. |
19 | URD | R/W1C | 0h | Set to 1 by the Controller when it receives an unsupported request, regardless of whether its reporting is enabled or not. |
18 | FED | R/W1C | 0h | Set to 1 by the Controller when it detects a fatal error, regardless of whether error reporting is enabled or not, and regardless of whether the error is masked. |
17 | NFED | R/W1C | 0h | Set to 1 by the Controller when it detects a non-fatal error, regardless of whether error reporting is enabled or not, and regardless of whether the error is masked. |
16 | CED | R/W1C | 0h | Set to 1 by the Controller when it detects a correctable error, regardless of whether error reporting is enabled or not, and regardless of whether the error is masked. |
15 | FLR | R/W | 0h | Writing a 1 into this bit position generates a Function-Level Reset for the selected Function. This bit reads as 0. |
14-12 | MRRS | R/W | 2h | Specifies the maximum size allowed in read requests generated by the device. |
11 | ENS | R/W | 1h | When set to 1, the device is allowed to set the No Snoop bit in initiated transactions in which cache coherency is not needed. |
10 | EAP | R | 0h | Used only when device used aux power. This field is hardwired to 0. |
9 | EPH | R | 0h | This field is hardwired to 0 as the Controller does not support this feature. |
8 | ETFE | R | 0h | Enables the extension of the tag field from 5 to 8 bits. |
7-5 | MPS | R/W | 0h | Specifies the maximum TLP payload size configured. The device must be able to receive a TLP of this maximum size, and should not generate TLPs larger than this value. The configuration program sets this field based on the maximum payload size in the Device Capabilities Register, and the capability of the other side. |
4 | ERO | R/W | 1h | When set, this bit indicates that the device is allowed to set the Relaxed Ordering bit in the Attributes field of transactions initiated from it, when the transactions do not require Strong Ordering. |
3 | EURR | R/W | 0h | Enables the sending of error messages by the Controller on receiving unsupported requests. |
2 | EFER | R/W | 0h | Enables the sending of ERR_FATAL messages by the Controller on the detection of fatal errors. |
1 | ENFER | R/W | 0h | Enables the sending of ERR_NONFATAL messages by the Controller on the detection of non-fatal errors. |
0 | ECER | R/W | 0h | Enables the sending of ERR_COR messages by the Controller on the detection of correctable errors. |
PCIE_CORE_PFn_I_LINK_CAP is shown in Figure 12-1301 and described in Table 12-2540.
Return to the Summary Table.
This register advertises the link-specific capabilities of the device incorporating the
PCIe Controller.
Offset = CCh + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00CCh + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
PN | |||||||
R/W-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R5 | AOC | LBNC | DLLARC | SDERC | CPM | L1EL | |
R-0h | R/W-1h | R-0h | R-0h | R-0h | R/W-0h | R/W-3h | |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
L1EL | L0SEL | ASPM | MLW | ||||
R/W-3h | R/W-2h | R/W-3h | R-2h | ||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
MLW | MLS | ||||||
R-4h | R-4h | ||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | PN | R/W | 0h | Specifies the port number assigned to the PCI Express link connected to this device. It can be modified from the local management bus by writing into Function 0 from the local management bus and will be same value for all function in multi-function device. |
23 | R5 | R | 0h | Reserved |
22 | AOC | R/W | 1h | Setting this bit indicates that the device supports the ASPM Optionality feature. It can be turned off by writing a 0 to this bit position through the local management bus. |
21 | LBNC | R | 0h | A value of 1b indicates support for the Link Bandwidth Notification status and interrupt mechanisms. Reserved for Endpoint. |
20 | DLLARC | R | 0h | Set to 1 if the device is capable of reporting that the DL Control and Management State Machine has reached the DL_Active state. This bit is hardwired to 0, as this version of the Controller does not support the feature. |
19 | SDERC | R | 0h | Indicates the capability of the device to report a Surprise Down error condition. This bit is hardwired to 0, as this version of the Controller does not support the feature. |
18 | CPM | R/W | 0h | Indicates that the device supports removal of referenc clocks. It is set by default to the value of the define in reg_defaults.h. It can be re-written independently for each function from the local management bus. |
17-15 | L1EL | R/W | 3h | Specifies the exit latency from L1 state. This parameter is dependent on the Physical Layer implementation. It is set by default to the value define in reg_defaults.h. It can be re-written independently for each Function from the local management bus. |
14-12 | L0SEL | R/W | 2h | Specifies the time required for the device to transition from L0S to L0. This parameter is dependent on the Physical Layer implementation. It is set by default to the value define in reg_defaults.h. It can be re-written independently for each Function from the local management bus. |
11-10 | ASPM | R/W | 3h | Indicates the level of ASPM support provided by the device. This field can be re-written independently for each Function from the local management bus. When SRIS is enabled in local management register bit, L0s capability is not supported and is forced low. |
9-4 | MLW | R | 4h | Indicates the maximum number of lanes supported by the device. This field is hardwired based on the setting of the LANE_COUNT_IN strap input. |
3-0 | MLS | R | 4h | Indicates the maximum speed supported by the link. [2.5 GT/s, 5 GT/s, 8 GT/s, 16 GT/s per lane]. This field is hardwired to 0001 [2.5GT/s] when the strap input PCIE_GENERATION_SEL is set to 0, to 0010 [5 GT/s] when the strap is set to 1, and to 0011 [8 GT/s] when the strap input is set to 10,to 0100 [16 GT/s] when the strap input is set to 11. |
PCIE_CORE_PFn_I_LINK_CTRL_STATUS is shown in Figure 12-1302 and described in Table 12-2542.
Return to the Summary Table.
This register contains control and status bits specific to the PCI Express link. All the
read-write bits in this register can also be written from the local management bus.
Offset = D0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00D0h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
LABS | LBMS | DLLA | SCC | LTS | R8 | NLW | |
R/W1C-0h | R/W1C-0h | R-0h | R/W-0h | R-0h | R-0h | R-2h | |
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
NLW | NLS | ||||||
R-4h | R-1h | ||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R15_12 | LABIE | LBMIE | HAWD | ECPM | |||
R-0h | R-0h | R-0h | R/W-0h | R-0h | |||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ES | CCC | RL | LD | RCB | R6 | ASPMC | |
R/W-0h | R/W-0h | R-0h | R-0h | R/W-0h | R-0h | R/W-0h | |
LEGEND: R = Read Only; R/W = Read/Write; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | LABS | R/W1C | 0h | This bit is Set by hardware to indicate that hardware has autonomously changed Link speed or width, without the Port transitioning through DL_Down status, for reasons other than to attempt to correct unreliable Link operation. This triggers an interrupt to be generated through PHY_INTERRUPT_OUT if enabled. Hardwired to 0 if Link Bandwidth Notification Capability is 0. Not applicable to Endpoints where field is hardwired to 0. |
30 | LBMS | R/W1C | 0h | This bit is Set by hardware to indicate that either link training has completed following write to retrain link bit, or when HW has changed link speed or width to attempt to correct unreliable link operation. This triggers an interrupt to be generated through PHY_INTERRUPT_OUT if enabled. Hardwired to 0 if Link Bandwidth Notification Capability is 0. Not applicable to Endpoints where field is hardwired to 0. |
29 | DLLA | R | 0h | Indicates the status of the Data Link Layer. Set to 1 when the DL Control and Management State Machine has reached the DL_Active state. This bit is hardwired to 0 in this version of the Controller. |
28 | SCC | R/W | 0h | This bit indicates that the component uses the same physical reference clock that the platform provides on the connector. If the device uses an independent clock irrespective of the presence of a reference clock on the connector, this bit must be clear. For PF0, this bit can also be written from the local management bus. |
27 | LTS | R | 0h | This read-only bit indicates that the Physical Layer LTSSM is in the Configuration or Recovery state, or that 1b was written to the Retrain Link bit but Link training has not yet begun. Hardware clears this bit when the LTSSM exits the Configuration/Recovery state. Not applicable to Endpoints where field is hardwired to 0. |
26 | R8 | R | 0h | Reserved |
25-20 | NLW | R | 4h | Set at the end of link training to the actual link width negotiated between the two sides. Value is undefined if this regsiters is accessed before link training. |
19-16 | NLS | R | 1h | Negotiated link speed of the device. The only supported speed ids are 2.5 GT/s per lane [0001],5 GT/s per lane [0010],8 GT/s per lane [0011],16 GT/s per lane [0100]. |
15-12 | R15_12 | R | 0h | Reserved |
11 | LABIE | R | 0h | When Set, this bit enables the generation of an interrupt to indicate that the Link Autonomous Bandwidth Status bit has been Set. This enables an interrupt to be generated through PHY_INTERRUPT_OUT if triggered. Hardwired to 0 if Link Bandwidth Notification Capability is 0. Not applicable to Endpoints where field is hardwired to 0. |
10 | LBMIE | R | 0h | When Set, this bit enables the generation of an interrupt to indicate that the Link Bandwidth Management Status bit has been Set. This enables an interrupt to be generated through PHY_INTERRUPT_OUT if triggered. Hardwired to 0 if Link Bandwidth Notification Capability is 0. Not applicable to Endpoints where field is hardwired to 0. |
9 | HAWD | R/W | 0h | When this bit is set, the local application must not request to change the operating width of the link, other than attempting to correct unreliable Link operation by reducing Link width. |
8 | ECPM | R | 0h | When this bit is set to 1, the device may use the CLKREQ# pin on the PCIe connector to power manage the Link clock. This bit is writeable only when the Clock Power Management bit in the Link Capability Register is set to 1. |
7 | ES | R/W | 0h | Set to 1 to extend the sequence of ordered sets transmitted while exiting from the L0S state. |
6 | CCC | R/W | 0h | A value of 0 indicates that the reference clock of this device is asynchronous to that of the upstream device. A value of 1 indicates that the reference clock is common. |
5 | RL | R | 0h | Setting this bit to 1 causes the LTSSM to initiate link training. Reserved for Endpoint mode. This bit always reads as 0 |
4 | LD | R | 0h | Writing a 1 to this bit position causes the LTSSM to go to the Disable Link state. The LTSSM stays in the Disable Link state while this bit is set.Reserved for Endpoint mode. |
3 | RCB | R/W | 0h | Indicates the Read Completion Boundary of the Root Port connected to this Endpoint [0 = 64 bytes, 1 = 128 bytes]. This field can be written from the APB bus by setting [21] bit high of the pcie_mgmt_APB_ADDR during a local management register write. |
2 | R6 | R | 0h | Reserved |
1-0 | ASPMC | R/W | 0h | Controls the level of ASPM support on the PCI Express link associated with this Function. The valid setting are 00: ASPM disabled 01: L0s entry enabled, L1 disabled 10: L1 entry enabled, L0s disabled 11: Both L0s and L1 enabled. |
PCIE_CORE_PFn_RSVD_035 is shown in Figure 12-1303 and described in Table 12-2544.
Return to the Summary Table.
Reserved
Offset = D4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00D4h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_RSVD_036 is shown in Figure 12-1304 and described in Table 12-2546.
Return to the Summary Table.
Reserved
Offset = D8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00D8h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_RSVD_037_038 is shown in Figure 12-1305 and described in Table 12-2548.
Return to the Summary Table.
Reserved
Offset = DCh + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00DCh + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_PCIE_DEV_CAP_2 is shown in Figure 12-1306 and described in Table 12-2550.
Return to the Summary Table.
This register advertises the capabilities of the PCI Express device encompassing this
Function.
Offset = E4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00E4h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R14 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
MEEP | EEPS | EXFS | OPFFS | T10RS | T10CS | ||
R/W-1h | R/W-1h | R-1h | R/W-1h | R-0h | R/W-1h | ||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R13 | RESERVED | TCS | LMS | R12 | BAOCS128 | BAOCS64 | |
R-0h | R/W-X | R-0h | R/W-1h | R-0h | R-0h | R-0h | |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
BAOCS32 | OPRS | AFS | CTDS | CTR | |||
R-0h | R-0h | R-0h | R/W-1h | R/W-2h | |||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | R14 | R | 0h | Reserved |
23-22 | MEEP | R/W | 1h | Indicates the maximum number of End-End TLP Prefixes supported by the Function. The supported values are: 01b 1 End-End TLP Prefix 10b 2 End-End TLP Prefixes |
21 | EEPS | R/W | 1h | Indicates whether the Function supports End-End TLP Prefixes. A 1 in this field indicates that the Function supports receiving TLPs containing End-End TLP Prefixes. |
20 | EXFS | R | 1h | Indicates that the Function supports the 3-bit definition of the Fmt field in the TLP header. This bit is hardwired to 1 for all Functions. |
19-18 | OPFFS | R/W | 1h | A 1 in this bit position indicates that the Function supports the Optimized Buffer Flush/Fill [OBFF] capability using message signaling. |
17 | T10RS | R | 0h | If set function supports 1-bit requester capability otherwise, the function does not. This bit can be disabled using local management register. |
16 | T10CS | R/W | 1h | If set function supports 1-bit completer capability otherwise, the function does not. This field can be modified using local management interface. |
15-14 | R13 | R | 0h | Reserved |
13 | RESERVED | R/W | X | |
12 | TCS | R | 0h | Hardwired to 0. |
11 | LMS | R/W | 1h | A 1 in this bit position indicates that the Function supports the Latency Tolerance Reporting [LTR] Capability. This bit is set to 1 by default, but can be turned off for all Physical Functions by writing into PF 0. |
10 | R12 | R | 0h | Reserved |
9 | BAOCS128 | R | 0h | Hardwired to 0. |
8 | BAOCS64 | R | 0h | Hardwired to 0. |
7 | BAOCS32 | R | 0h | Hardwired to 0. |
6 | OPRS | R | 0h | Atomic OP routing supported. |
5 | AFS | R | 0h | ARI forwarding supported. |
4 | CTDS | R/W | 1h | A 1 in this field indicates that the associated Function supports the capability to turn off its Completion timeout. This bit is set to 1 by default, but can be re-written independently for each Function from the local management bus. |
3-0 | CTR | R/W | 2h | Specifies the Completion Timeout values supported by the device. This field is set by default to 0010 [10 ms - 250 ms]. The actual timeout values are in two programmable local management registers, which allow the timeout settings of the two sub-ranges within Range B to be programmed independently. |
PCIE_CORE_PFn_I_PCIE_DEV_CTRL_STATUS_2 is shown in Figure 12-1307 and described in Table 12-2552.
Return to the Summary Table.
This register contains control and status bits associated with the device implementing
this Function.
Offset = E8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00E8h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R18 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R18 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R18 | OBFFE | T10RE | R17 | LTRME | IDOCE | IDORE | |
R-0h | R/W-0h | R-0h | R-0h | R/W-0h | R/W-0h | R/W-0h | |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R16 | AORE | AFE | CTD | CTV | |||
R-0h | R-0h | R-0h | R/W-0h | R/W-0h | |||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-15 | R18 | R | 0h | Reserved |
14-13 | OBFFE | R/W | 0h | Enables the Optimized Buffer Flush/Fill [OBFF] capability in the device. This field is implemented only in PF 0. Valid settings are 00 [disabled], 01 [Variation A] and 10 [Variation B]. This field can also be written from the local management bus. RW if OBFF capability is supported, RO otherwise. |
12 | T10RE | R | 0h | 10bit TAGs generation are not supported in this configuration. |
11 | R17 | R | 0h | Reserved |
10 | LTRME | R/W | 0h | This must be set to 1 to enable the Latency Tolerance Reporting Mechanism. This bit is implemented only in PF 0. Its default value is 1, but can be modified from the local management bus. This bit is read-only in PF 1. |
9 | IDOCE | R/W | 0h | When this bit is 1, the Function is allowed to set the ID-based Ordering [IDO] Attribute bit in the Completions it generates. |
8 | IDORE | R/W | 0h | When this bit is 1, the Function is allowed to set the ID-based Ordering [IDO] Attribute bit in the requests it generates. |
7 | R16 | R | 0h | Reserved |
6 | AORE | R | 0h | This bit must be set to enable the generation of Atomic Op Requests from the Function. If the client logic attempts to send an Atomic Op for a Function for which this bit is not set, logic in the Controller will nullify the TLP on its way to the link. |
5 | AFE | R | 0h | ARI forwarding enable |
4 | CTD | R/W | 0h | Setting this bit disables Completion Timeout in the device. This bit can also be written from the local management bus. |
3-0 | CTV | R/W | 0h | Specifies the Completion Timeout value for the device. Allowable values are 0101 [sub-range 1] and 0110 [sub-range 2]. The corresponding timeout values are stored in the local management registers Completion Timeout Interval Registers 0 and 1, respectively. Value of 0 selects completion timeout from Completion-Timeout-Interval-Registers-0 in local management register. |
PCIE_CORE_PFn_I_LINK_CAP_2_REG is shown in Figure 12-1308 and described in Table 12-2554.
Return to the Summary Table.
This register advertises the supported link speeds of the Controller.
Offset = ECh + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00ECh + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R31 | R25 | TWRTPDS | |||||
R-0h | R-0h | R/W-1h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RTPDS | R3 | LSORSSV | |||||
R/W-1h | R-0h | R/W-0h | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R2 | LSOGSSV | R1 | |||||
R-0h | R/W-0h | R-0h | |||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R1 | SLSV | RESERVED | |||||
R-0h | R/W-Fh | R/W-X | |||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | R31 | R | 0h | Indicates support for the optional Device Readiness Status [DRS] capability. This capability is currently not supported in the Controller. |
30-25 | R25 | R | 0h | Reserved |
24 | TWRTPDS | R/W | 1h | When set to 1b, this bit indicates that the associated Port supports detection and reporting of two Retimers presence. This bit is valid for both Downstream Ports and Upstream Ports. |
23 | RTPDS | R/W | 1h | When set to 1b, this bit indicates that the associated Port supports detection and reporting of Retimer presence. This bit is valid for both Downstream Ports and Upstream Ports. |
22-20 | R3 | R | 0h | Reserved |
19-16 | LSORSSV | R/W | 0h | If this field is non-zero, it indicates that the Port, when operating at the indicated speed[s] supports SRIS and also supports receiving SKP OS at the rate defined for SRNS while running in SRIS. |
15-13 | R2 | R | 0h | Reserved |
12-9 | LSOGSSV | R/W | 0h | If this field is non-zero, it indicates that the Port, when operating at the indicated speed[s] supports SRIS and also supports software control of the SKP Ordered Set transmission scheduling rate. |
8-5 | R1 | R | 0h | Reserved |
4-1 | SLSV | R/W | Fh | This field indicates the supported link speeds of the Controller. For each bit, a value of 1 indicates that the corresponding link speed is supported, while a value of 0 indicates that the corresponding speed is not supported. The bits corresponding to various link speeds are: Bit 1 = Link Speed 2.5 GT/s, Bit 2 = Link Speed 5 GT/s, Bit 3 = Link Speed 8 GT/s, Bit 4 = Link Speed 16 GT/s. This field is hardwired to 0001 [2.5 GT/s] when the PCIE_GENERATION_SEL strap pins of the Controller are set to 0, 0011 [2.5 and 5 GT/s] when the strap is set to 1 , and 0111 [2.5, 5, and 8 GT/s] when the strap pin is set to 10 , and 1111 [2.5, 5, 8 GT/s and 16 GT/s] when the strap pin is set to 11 For PF0, this field can be written through the LM interface. |
0 | RESERVED | R/W | X |
PCIE_CORE_PFn_I_LINK_CTRL_STATUS_2 is shown in Figure 12-1309 and described in Table 12-2556.
Return to the Summary Table.
This register contains control and status bits specific to the PCI Express link. All the
fields marked RW or RW(STICKY) can also be written from the local management bus.
Offset = F0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00F0h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
DMR | DCP | R21 | |||||
R-0h | R-0h | R-0h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
TWRTP | RTP | LE | EP3S | EP2S | EP1S | EQC | CDEL |
R-0h | R-0h | R/W-0h | R-0h | R-0h | R-0h | R-0h | R-1h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
CDE | CS | EMC | TM | ||||
R/W-0h | R/W-0h | R/W-0h | R/W-0h | ||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
TM | SDE | HASD | EC | TLS | |||
R/W-0h | R-0h | R/W-0h | R/W-0h | R/W-4h | |||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | DMR | R | 0h | DRS is not supported by the Controller and hence this field is not implemented. |
30-28 | DCP | R | 0h | DRS is not supported by the Controller and hence this field is not implemented. |
27-24 | R21 | R | 0h | Reserved |
23 | TWRTP | R | 0h | When set to 1b, this bit indicates that two Retimers were present during the most recent Link negotiation. |
22 | RTP | R | 0h | When set to 1b, this bit indicates that a Retimer was present during the most recent Link negotiation. |
21 | LE | R/W | 0h | This bit is set by Controller hardware to request the 8.0 GT/s link equalization process to be performed on the Link. Controller hardware sets this bit, if a link equalization problem is detected at the end of equalization at 8GT/s. Additionally, the Client Firmware may set this bit while requesting equalization through Local Management EP 8GTs Request Equalization Retrain Link bit. This bit is cleared by writing a 1 to this bit position by the host, or writing a 0 from the LMI. STICKY. |
20 | EP3S | R | 0h | This bit, when set to 1, indicates that the Phase 3 of the Transmitter Equalization procedure has completed successfully for 8.0 GT/s. STICKY. |
19 | EP2S | R | 0h | This bit, when set to 1, indicates that the Phase 2 of the Transmitter Equalization procedure has completed successfully for 8.0 GT/s. STICKY. |
18 | EP1S | R | 0h | This bit, when set to 1, indicates that the Phase 1 of the Transmitter Equalization procedure has completed successfully for 8.0 GT/s. STICKY. |
17 | EQC | R | 0h | This bit, when set to 1, indicates that the Transmitter Equalization procedure has completed for 8.0 GT/s. STICKY. |
16 | CDEL | R | 1h | This status bit indicates the current operating de-emphasis level of the transmitter [0 = -6 dB, 1 = -3.5 dB].This field is undefined when link is not at Gen2 speed. |
15-12 | CDE | R/W | 0h | This bit sets the de-emphasis level [for 5 GT/s operation] or the Transmitter Preset level [for 8 GT/s or 16 GT/s operation] when the LTSSM enters the Polling.Compliance state because of software setting the Enter Compliance bit in this register. It is used only when the link is running at 5 GT/s or 8 GT/s or 16 GT/s. At 5 GT/s, the only valid setting are 0 [-6 dB] and 1 [-3.5 dB]. STICKY. |
11 | CS | R/W | 0h | When this bit is set to 1, the device will transmit SKP ordered sets between compliance patterns. STICKY. |
10 | EMC | R/W | 0h | This field is intended for debug and compliance testing purposes only. If this bit is set to 1, the device will transmit the Modified Compliance Pattern when the LTSSM enters the Polling. Compliance substate. Note: Setting this bit alone will not cause the LTSSM to enter Polling.Compliance. The Enter Compliance bit must also be set and a Hot Reset needs to be initiated by Host to enter Polling.Compliance. STICKY. |
9-7 | TM | R/W | 0h | This field is intended for debug and compliance testing purposes only. It controls the non-de-emphasized voltage level at the transmitter outputs. Its encodings are: 000: Normal operating range. 001: 800 - 1200 mV for full swing and 400 - 700 mV for half swing. 010 - 111: See PCI Express Base Specification 2.0. This field is reset to 0 when the LTSSM enters the Polling.Configuration substate during link training. STICKY. |
6 | SDE | R | 0h | This bit selects the de-emphasis level when the Controller is operating at 5 GT/s [0 = -6 dB, 1 = -3.5 dB]. This is reserved for Endpoints. |
5 | HASD | R/W | 0h | When this bit is set, the LTSSM is prevented from changing the operating speed of the link, other than reducing the speed to correct unreliable operation of the link. STICKY |
4 | EC | R/W | 0h | This bit is used to force the Endpoint device to enter the Compliance mode. Software sets this bit to 1 and initiates a hot reset to force the device into the Compliance mode. The target speed for the Compliance mode is determined by the Target Link Speed field of this register. STICKY. |
3-0 | TLS | R/W | 4h | For an upstream component, this field sets an upper limit on Link operational speed during reconfiguration. Additionally for both upstream and downstream components, this field sets the target speed when the software forces the link into Compliance mode by setting the Enter Compliance bit in this register [0001 = 2.5 GT/s, 0010 = 5 GT/s, 0011 = 8 GT/s, 0100 = 16 GT/s]. The default value of this field is 0001 [2.5 GT/s] when the PCIE_GENERATION_SEL strap pins of the Controller are set to 0, 0010 [5 GT/s] when the strap is set to 1, 0011 [8 GT/s] when the strap pin is set to 10 , and 0100 [16 GT/s] when the strap pin is set to 11. These bits are STICKY. |
PCIE_CORE_PFn_RSVD_03D_03F is shown in Figure 12-1310 and described in Table 12-2558.
Return to the Summary Table.
Reserved
Offset = F4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 00F4h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_AER_ENHANCED_CAP_HDR is shown in Figure 12-1311 and described in Table 12-2560.
Return to the Summary Table.
This is the first register in the PCI Express Advanced Error Reporting Capability
Structure. This register contains the PCI Express Extended Capability ID, the capability
version, and the pointer to the next capability structure.
Offset = 100h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0100h + formula |
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 |
NCO | CV | PEECI | |||||||||||||||||||||||||||||
R/W-140h | R/W-2h | R-1h | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 140h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 2h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 4'h2, but can be modified from the local management bus. |
15-0 | PEECI | R | 1h | This field is hardwired to the Capability ID assigned by PCI SIG to the PCI Express AER Extended Capability Structure [0001 hex]. |
PCIE_CORE_PFn_I_UNCORR_ERR_STATUS is shown in Figure 12-1312 and described in Table 12-2562.
Return to the Summary Table.
This register provides the status of the various uncorrectable errors detected by the
PCI Express Controller. Software may clear any error bit by writing a 1 into the corresponding bit
position. The states of the bits in the Uncorrectable Error Mask Register have no effect on the
status bits of this register. The setting of an uncorrectable error status bit causes the Controller
to generate an ERR_FATAL message if the corresponding severity bit of the Uncorrectable Error
Severity Register is 1. If the severity bit is 0, however, there are two separate ways the error
could be processed: (i) In certain cases, the uncorrectable error is treated as an Advisory
Non-Fatal Error. These cases are treated as similar to correctable errors, causing the Controller to
generate an ERR_COR message instead of an ERR_NONFATAL message. For details on these special
cases, refer to Section 6.2.3.2.4 of the PCI Express Base Specifications, Version 1.1. (ii) In
all other cases, the Controller sends an ERR_NONFATAL message when the error is detected. In all
cases, the sending of the error message can be suppressed by setting the bit corresponding to
the error type in the Uncorrectable Error Mask Register. For errors that are not
Function-specific, the error status bus is set in the registers belonging to all the Functions
associated with the link, but only a single message is generated for the entire link. In the
case of certain errors detected by the Transaction Layer, the associated TLP header is logged in
the Header Log Registers. All the RW1C bits can also be cleared from the local management bus by
writing a 1 into the bit position.
Offset = 104h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0104h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R3 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R3 | UIE | R2 | URES | EES | MTS | ROS | UCS |
R-0h | R/W1C-0h | R-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
CAS | CTS | FCPES | PTS | R1 | |||
R/W1C-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h | R-0h | |||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R1 | SDES | DLPES | R0 | LTE | |||
R-0h | R/W1C-0h | R/W1C-0h | R-0h | R/W1C-0h | |||
LEGEND: R = Read Only; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-23 | R3 | R | 0h | N/A |
22 | UIE | R/W1C | 0h | This bit is set when the Controller has detected an internal uncorrectable error [HAL parity error or an uncorrectable ECC error while reading from any of the RAMs]. This bit is also set in response to the client signaling an internal error through the input UNCORRECTABLE_ERROR_IN. This error is not Function-specific. This error is considered fatal by default, and is reported by sending an ERR_FATAL message. STICKY. |
21 | R2 | R | 0h | Reserved |
20 | URES | R/W1C | 0h | This bit is set when the Controller has received a request from the link that it does not support. This error is not Function-specific. This error is considered non-fatal by default. In the special case described in Sections 6.2.3.2.4.1 of the PCI Express Specifications, the error is reported by sending an ERR_COR message. In all other cases, the error is reported by sending an ERR_NONFATAL message. The header of the received request that caused the error is logged in the Header Log Registers. STICKY. |
19 | EES | R/W1C | 0h | This bit is set when the Controller has detected an ECRC error in a received TLP. This error is not Function-specific. The header of the received TLP with error is logged in the Header Log Registers. STICKY. |
18 | MTS | R/W1C | 0h | This bit is set when the Controller receives a malformed TLP from the link. This error is not Function-specific. This error is considered fatal by default, and is reported by sending an ERR_FATAL message. The header of the received TLP with error is logged in the Header Log Registers. STICKY. |
17 | ROS | R/W1C | 0h | This bit is set when the Controller receives a TLP in violation of the receive credit currently available. This error is not Function-specific. STICKY. |
16 | UCS | R/W1C | 0h | This bit is set when the Controller has received an unexpected Completion packet from the link. This error is not Function-specific. STICKY. |
15 | CAS | R/W1C | 0h | This bit is set when the Controller has returned the Completer Abort [CA] status to a request received from the link. This error is Function-specific. The header of the received request that caused the error is logged in the Header Log Registers. STICKY. |
14 | CTS | R/W1C | 0h | This bit is set when the completion timer associated with an outstanding request times out. This error is Function-specific. This error is considered non-fatal by default. STICKY. |
13 | FCPES | R/W1C | 0h | This bit is set when certain violations of the flow control protocol are detected by the Controller. Controller reports FCPE upon the following conditions: [i] InitFC/UpdateFC DLLP received which issues more than 2047 cumulative outstanding unused credits to the Transmitter for data payload or 127 for header. [ii] InitFC_P is received with Payload Credits less than 128B, Or [iii]InitFC_CPL is received with Payload Credits less than 128B. This error is not Function-specific STICKY. |
12 | PTS | R/W1C | 0h | This bit is set when the Controller receives a poisoned TLP from the link. This error is Function-specific. This error is considered non-fatal by default. The error is reported by sending an ERR_NONFATAL message. The header of the received TLP with error is logged in the Header Log Registers. STICKY. |
11-6 | R1 | R | 0h | Reserved |
5 | SDES | R/W1C | 0h | This error status indicates Link up to Link down event. So Status bit is set upon LINK_DOWN_RESET_OUT event. This field is applicable to RC only and not for EP as per PCIE spec. |
4 | DLPES | R/W1C | 0h | This bit is set when the Controller receives an Ack or Nak DLLP whose sequence number does not correspond to that of an unacknowledged TLP or that of the last acknowledged TLP [for details, refer to PCI Express Base Specification 1.1, Section 3.5.2]. This error is not Function-specific, and is reported by Function 0. STICKY. |
3-1 | R0 | R | 0h | Reserved |
0 | LTE | R/W1C | 0h | This error indicates that link training is not successful and transition back to detect state. This Status bit is set on any LTSSM transition from Configuration to Detect or Recovery to Detect. This field is applicable to RC only and not for EP as per PCIE spec. |
PCIE_CORE_PFn_I_UNCORR_ERR_MASK is shown in Figure 12-1313 and described in Table 12-2564.
Return to the Summary Table.
The mask bits in this register control the reporting of uncorrectable errors. For each
error type in the Uncorrectable Error Status Register, there is a corresponding bit in this
register to mask its reporting. Setting the mask bit has the following effects: (i) The
occurrence of the error is not reported to the Root Complex (by a PCI Express error message).
(ii) The header of the TLP in which the error was detected is not logged in the Header Log
Registers. (iii) The First Error Pointer in the Advanced Error Capabilities and Control Register
is not updated on detection of the error. The individual bits of the mask register are described
below. The bits marked RW can also be written from the local management bus.
Offset = 108h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0108h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R7 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R7 | UIEM | R6 | UREM | EEM | MTM | ROM | UCM |
R-0h | R/W-1h | R-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
CAM | CTM | FCPEM | PTM | R5 | |||
R/W-0h | R/W-0h | R/W-0h | R/W-0h | R-0h | |||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R5 | SDESM | DLPEM | R4 | LTEM | |||
R-0h | R/W-0h | R/W-0h | R-0h | R/W-0h | |||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-23 | R7 | R | 0h | Reserved |
22 | UIEM | R/W | 1h | This bit is set to mask the reporting of internal errors. STICKY. |
21 | R6 | R | 0h | Reserved |
20 | UREM | R/W | 0h | This bit is set to mask the reporting of unexpected requests received from the link. STICKY. |
19 | EEM | R/W | 0h | This bit is set to mask the reporting of ECRC errors. STICKY. |
18 | MTM | R/W | 0h | This bit is set to mask the reporting of malformed TLPs received from the link. STICKY. |
17 | ROM | R/W | 0h | This bit is set to mask the reporting of violations of receive credit. STICKY. |
16 | UCM | R/W | 0h | This bit is set to mask the reporting of unexpected Completions received by the Controller. STICKY. |
15 | CAM | R/W | 0h | This bit is set to mask the reporting of the Controller sending a Completer Abort. STICKY. |
14 | CTM | R/W | 0h | This bit is set to mask the reporting of Completion Timeouts. STICKY. |
13 | FCPEM | R/W | 0h | This bit is set to mask the reporting of Flow Control Protocol Errors. STICKY. |
12 | PTM | R/W | 0h | This bit is set to mask the reporting of a Poisoned TLP. STICKY. |
11-6 | R5 | R | 0h | Reserved |
5 | SDESM | R/W | 0h | This bit is set to mask the reporting of Surprise Down Error Status Mask. STICKY. This field is applicable to RC only and not for EP as per PCIE spec. |
4 | DLPEM | R/W | 0h | This bit is set to mask the reporting of Data Link Protocol Errors. STICKY. |
3-1 | R4 | R | 0h | Reserved |
0 | LTEM | R/W | 0h | This bit is set to mask the reporting of Link Training Error Mask. STICKY. This field is applicable to RC only and not for EP as per PCIE-spec. |
PCIE_CORE_PFn_I_UNCORR_ERR_SEVERITY is shown in Figure 12-1314 and described in Table 12-2566.
Return to the Summary Table.
The setting of this register determines whether an uncorrectable error is reported as a
fatal error on non-fatal error to the Root Complex. If a severity bit of this register is 0, the
corresponding error is reported by the Controller using an ERR_NONFATAL message. Otherwise, it is
reported using an ERR_FATAL message. The bits marked RW can also be written from the local
management bus.
Offset = 10Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 010Ch + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R12 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R12 | UIES | R11 | URES | EES | MTS | ROS | UCS |
R-0h | R/W-1h | R-0h | R/W-0h | R/W-0h | R/W-1h | R/W-1h | R/W-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
CAS | CTS | FCPES | PTS | R10 | |||
R/W-0h | R/W-0h | R/W-1h | R/W-0h | R-0h | |||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R10 | SDES | DLPER | R8 | LTES | |||
R-0h | R/W-1h | R/W-1h | R-0h | R/W-0h | |||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-23 | R12 | R | 0h | Reserved |
22 | UIES | R/W | 1h | Severity of internal errors [0 = Non-Fatal, 1 = Fatal]. STICKY. |
21 | R11 | R | 0h | Reserved |
20 | URES | R/W | 0h | Severity of unexpected requests received from the link [0 = Non-Fatal, 1 = Fatal]. STICKY. |
19 | EES | R/W | 0h | Severity of ECRC errors [0 = Non-Fatal, 1 = Fatal]. STICKY. |
18 | MTS | R/W | 1h | Severity of malformed TLPs received from the link [0 = Non- Fatal, 1 = Fatal]. STICKY. |
17 | ROS | R/W | 1h | Severity of receive credit violations [0 = Non-Fatal, 1 = Fatal]. STICKY. |
16 | UCS | R/W | 0h | Severity of unexpected Completions received by the Controller [0 = Non-Fatal, 1 = Fatal]. STICKY. |
15 | CAS | R/W | 0h | Severity of sending a Completer Abort [0 = Non-Fatal, 1 = Fatal]. STICKY. |
14 | CTS | R/W | 0h | Severity of Completion Timeouts [0 = Non-Fatal, 1 = Fatal]. STICKY. |
13 | FCPES | R/W | 1h | Severity of Flow Control Protocol Errors [0 = Non-Fatal, 1 = Fatal]. STICKY. |
12 | PTS | R/W | 0h | Severity of a Poisoned TLP error [0 = Non-Fatal, 1 = Fatal]. STICKY. |
11-6 | R10 | R | 0h | Reserved |
5 | SDES | R/W | 1h | Severity of Surprise Down Error Severity [0 = Non-Fatal, 1 = Fatal]. STICKY. This field is applicable to RC only and not for EP as per PCIE spec. |
4 | DLPER | R/W | 1h | Severity of Data Link Protocol Errors [0 = Non-Fatal, 1 = Fatal]. STICKY. |
3-1 | R8 | R | 0h | Reserved |
0 | LTES | R/W | 0h | Severity of Link Training Error [0 = Non-Fatal, 1 = Fatal]. STICKY. This field is applicable to RC only and not for EP as per PCIE spec. |
PCIE_CORE_PFn_I_CORR_ERR_STATUS is shown in Figure 12-1315 and described in Table 12-2568.
Return to the Summary Table.
This register provides the status of the various correctable errors detected by the PCI
Express Controller. Software may clear any error bit by writing a 1 into the corresponding bit
position. The states of the bits in the Correctable Error Mask Register have no effect on the
status bits of this register. The setting of a correctable error status bit causes the Controller to
generate an ERR_COR error message to the Root Complex if the error is not masked in the
Correctable Error Mask Register. For errors that are not Function-specific, the error status bus
is set in the registers belonging to all the Functions associated with the link, but only a
single message is generated for the entire link. Header logging of received TLPs does not apply
to correctable errors. All the RW1C bits can also be cleared from the local management bus by
writing a 1 into the bit position.
Offset = 110h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0110h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R14 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R14 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
HLOS | CIES | ANFES | RTTS | R13 | RNRS | ||
R/W1C-0h | R/W1C-0h | R/W1C-0h | R/W1C-0h | R-0h | R/W1C-0h | ||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
BDS | BTS | R12 | RES | ||||
R/W1C-0h | R/W1C-0h | R-0h | R/W1C-0h | ||||
LEGEND: R = Read Only; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | R14 | R | 0h | Reserved |
15 | HLOS | R/W1C | 0h | This bit is set on a Header Log Register overflow, that is, when the header could not be logged in the Header Log Register because it is occupied by a previous header. STICKY. |
14 | CIES | R/W1C | 0h | This bit is set when the Controller has detected an internal correctable error condition [a correctable ECC error while reading from any of the RAMs]. This bit is also set in response to the client signaling an internal error through the input CORRECTABLE_ERROR_IN. This error is not Function-specific. STICKY. |
13 | ANFES | R/W1C | 0h | This bit is set when an uncorrectable error occurs, which is determined to belong to one of the special cases described in Section 6.2.3.2.4 of the PCI Express 2.0 Specifications. This causes the Controller to generate an ERR_COR message in place of an ERR_NONFATAL message. STICKY. |
12 | RTTS | R/W1C | 0h | This bit is set when the replay timer in the Data Link Layer of the Controller times out, causing the Controller to retransmit a TLP. This error is not Function-specific. STICKY. |
11-9 | R13 | R | 0h | Reserved |
8 | RNRS | R/W1C | 0h | This bit is set when the replay count rolls over after three re-transmissions of a TLP at the Data Link Layer of the Controller. This error is not Function-specific STICKY. |
7 | BDS | R/W1C | 0h | This bit is set when an LCRC error is detected in a received DLLP, and no errors were detected by the Physical Layer. This error is not Function-specific. STICKY. |
6 | BTS | R/W1C | 0h | This bit is set when an error is detected in a received TLP by the Data Link Layer of the Controller. The conditions causing this error are: [i] An LCRC error [ii] The packet terminates with EDB symbol, but its LCRC field does not equal the inverted value of the calculated CRC. This error is not Function-specific. STICKY. |
5-1 | R12 | R | 0h | Reserved |
0 | RES | R/W1C | 0h | This bit is set when an error is detected in the receive side of the Physical Layer of the Controller [e.g. a bit error or coding violation]. This bit is set upon any of the following errors: [1] PHY reported 8B10B error, Disparity Error, Elastic Buffer Overflow Error, Underflow Error [2] GEN3 TLP, DLLP Framing Errors [3] OS Block Received Without EDS [4] Data Block Received After EDS [5] Illegal OS Block After EDS [6] OS Block Received After SKIP OS [7] OS Block Received After SDS [8] Sync Header Error [9] Loss of Gen3 Block Alignment This error is not Function-specific. STICKY. |
PCIE_CORE_PFn_I_CORR_ERR_MASK is shown in Figure 12-1316 and described in Table 12-2570.
Return to the Summary Table.
The mask bits in this register control the reporting of correctable errors. For each
error type in the Correctable Error Status Register, there is a corresponding bit in this
register to mask its reporting. When a mask bit is set, the occurrence of the error is not
reported to the Root Complex (by a PCI Express error message). The individual bits of the mask
register are described below. The bits marked RW can also be written from the local management
bus.
Offset = 114h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0114h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R17 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R17 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
HLOM | CIEM | ANFEM | RTTM | R16 | RNRM | ||
R/W-1h | R/W-1h | R/W-1h | R/W-0h | R-0h | R/W-0h | ||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
BDM | BTM | R15 | REM | ||||
R/W-0h | R/W-0h | R-0h | R/W-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | R17 | R | 0h | Reserved |
15 | HLOM | R/W | 1h | This bit, when set, masks the generation of error messages in response to a Header Log register overflow. STICKY. |
14 | CIEM | R/W | 1h | This bit, when set, masks the generation of error messages in response to a corrected internal error condition. STICKY. |
13 | ANFEM | R/W | 1h | This bit, when set, masks the generation of error messages in response to an uncorrectable error occur, which is determined to belong to one of the special cases [as described in Section 6.2.3.2.4 of the PCI Express 2.0 Specifications]. STICKY. |
12 | RTTM | R/W | 0h | This bit, when set, masks the generation of error messages in response to a Replay Timer timeout event. STICKY. |
11-9 | R16 | R | 0h | Reserved |
8 | RNRM | R/W | 0h | This bit, when set, masks the generation of error messages in response to a Replay Number Rollover event. STICKY. |
7 | BDM | R/W | 0h | This bit, when set, masks the generation of error messages in response to a 'Bad DLLP' received. STICKY. |
6 | BTM | R/W | 0h | This bit, when set, masks the generation of error messages in response to a 'Bad TLP' received. STICKY. |
5-1 | R15 | R | 0h | Reserved |
0 | REM | R/W | 0h | This bit, when set, masks the generation of error messages in response to the Physical Layer errors STICKY. |
PCIE_CORE_PFn_I_ADVCD_ERR_CAP_CTRL is shown in Figure 12-1317 and described in Table 12-2572.
Return to the Summary Table.
This register contains a pointer to the first error that is reported in the
Uncorrectable Error Status Register, and bits to enable ECRC generation and checking.
Offset = 118h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0118h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R18 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R18 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R18 | TPLP | MHRE | MHRC | EEC | |||
R-0h | R-0h | R-0h | R-0h | R/W-0h | |||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ECC | EEG | EGC | FER | ||||
R/W-1h | R/W-0h | R/W-1h | R-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-12 | R18 | R | 0h | Reserved |
11 | TPLP | R | 0h | If Set and the First Error Pointer is valid, indicates that the TLP Prefix Log register contains valid information. If Clear or if First Error Pointer is invalid, the TLP Prefix Log register is undefined. Default value of this bit is 0. This bit is RsvdP if the End-End TLP Prefix Supported bit is CIf Set and the First Error Pointer is valid, indicates that the TLP Prefix Log register contains valid information. If Clear or if First Error Pointer is invalid, the TLP Prefix Log register is undefined. |
10 | MHRE | R | 0h | Setting this bit enables the Function to log multiple error headers in its Header Log Registers. It is hardwired to 0 |
9 | MHRC | R | 0h | This bit is set when the Function has the capability to log more than one error header in its Header Log Registers. It is hardwired to 0. |
8 | EEC | R/W | 0h | Setting this bit enables ECRC checking on the receive side of the Controller. This bit is writable from the local management bus. STICKY. |
7 | ECC | R/W | 1h | This read-only bit indicates to the software that the device is capable of checking ECRC in packets received from the link. This bit is writable from the local management bus. |
6 | EEG | R/W | 0h | Setting this bit enables the ECRC generation on the transmit side of the Controller. This bit is writable from the local management bus. STICKY. |
5 | EGC | R/W | 1h | This read-only bit indicates to the software that the device is capable of generating ECRC in packets transmitted on the link. This bit is writable from the local management bus. |
4-0 | FER | R | 0h | This is a 5-bit pointer to the bit position in the Uncorrectable Error Status Register corresponding to the error that was detected first. When there are multiple bits set in the Uncorrectable Error Status Register, this field informs the software which error was observed first. To prevent the field from being overwritten before software was able to read it, this field is not updated while the status bit pointed by it in the Uncorrectable Error Status Register remains set. After the software clears this status bit, a subsequent error condition that sets any bit in the Uncorrectable Error Status Register will update the First Error Pointer. Any uncorrectable error type, including the special cases where the error is reported using an ERR_COR message, will set the First Error Pointer [assuming the software has reset the error pointed by it in the Uncorrectable Error Status Register]. STICKY. |
PCIE_CORE_PFn_I_HDR_LOG_0 is shown in Figure 12-1318 and described in Table 12-2574.
Return to the Summary Table.
This is the first of a set of four registers used to capture the header of a TLP
received by the Controller from the link upon detection of an uncorrectable error. When multiple
bits are set in the Uncorrectable Error Status Register, the captured header corresponds to
the error that was detected first, that is, the error pointed by the First Error Pointer. To
prevent the captured header from being over-written before software was able to read it, this
register is not updated while the status bit pointed by the First Error Pointer in the
Uncorrectable Error Status Register remains set. After the software clears this status bit, a
subsequent error condition that sets any bit in the Uncorrectable Error Status Register will
also cause the Header Log Registers to be updated. The doublewords of the TLP header are
stored in the Header Log Registers with their bytes transposed. That is, the byte containing
the Type/Format fields of the header is stored at bit positions 31:24 of the Header Log
Register 0.
Offset = 11Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 011Ch + formula |
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 |
HD0 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | HD0 | R | 0h | First DWORD of captured TLP header STICKY. |
PCIE_CORE_PFn_I_HDR_LOG_1 is shown in Figure 12-1319 and described in Table 12-2576.
Return to the Summary Table.
This register contains the second DWORD of the captured TLP header. The bytes are
stored in transposed order.
Offset = 120h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0120h + formula |
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 |
HD1 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | HD1 | R | 0h | Second DWORD of captured TLP header STICKY. |
PCIE_CORE_PFn_I_HDR_LOG_2 is shown in Figure 12-1320 and described in Table 12-2578.
Return to the Summary Table.
This register contains the third DWORD of the captured TLP header. The bytes are
stored in transposed order.
Offset = 124h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0124h + formula |
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 |
HD2 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | HD2 | R | 0h | Third DWORD of captured TLP header STICKY. |
PCIE_CORE_PFn_I_HDR_LOG_3 is shown in Figure 12-1321 and described in Table 12-2580.
Return to the Summary Table.
If the captured TLP header is 4 DWORDs long, this register contains its fourth DWORD. If
the captured header is a 3-DWORD header, this register is unused. The bytes of the DWORD are
stored in this register in transposed order.
Offset = 128h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0128h + formula |
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 |
HD3 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | HD3 | R | 0h | Fourth DWORD of captured TLP header STICKY. |
PCIE_CORE_PFn_RSVD_04B_04D is shown in Figure 12-1322 and described in Table 12-2582.
Return to the Summary Table.
Reserved
Offset = 12Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 012Ch + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_TLP_PRE_LOG_0 is shown in Figure 12-1323 and described in Table 12-2584.
Return to the Summary Table.
First TLP Prefix (if present) associated with the TLP whose header is in the Header Log Register.
The bytes are in transposed order.
Offset = 138h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0138h + formula |
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 |
HD1 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | HD1 | R | 0h | First TLP Prefix of captured TLP STICKY. |
PCIE_CORE_PFn_I_ARI_EXT_CAP_HDR is shown in Figure 12-1324 and described in Table 12-2586.
Return to the Summary Table.
This register is used to enable
the Alternate Routing ID interpretation. This register contains the PCI Express Extended
Capability ID, the capability version, and the pointer to the next capability structure.
Offset = 140h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0140h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
ARINCO | ARICV | ||||||||||||||
R/W-150h | R/W-1h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
PECID | |||||||||||||||
R-Eh | |||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | ARINCO | R/W | 150h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | ARICV | R/W | 1h | Specifies the SIG-assigned value for the version of the capability structure. This field is set to 1 by default, but can be modified independently for each Function from the local management bus |
15-0 | PECID | R | Eh | This field is hardwired to the Capability ID assigned by PCI-SIG to the ARI Extended Capability [000E hex]. |
PCIE_CORE_PFn_I_ARI_CAP_AND_CTRL is shown in Figure 12-1325 and described in Table 12-2588.
Return to the Summary Table.
This location contains the ARI Capability Register and the ARI Control Register. The
individual fields are described below.
Offset = 144h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0144h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
ACR | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
ACR | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
NF | |||||||
R/W-1h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | AFGC | MFGC | |||||
R/W-X | R-0h | R-0h | |||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | ACR | R | 0h | ARI Control Register not implemented in this Controller. This field is hardwired to 0. |
15-8 | NF | R/W | 1h | Points to the next Physical Function in the device. This field is set by default to point to the next Physical Function, 0 for last Function. It can be rewritten from the local management bus. |
7-2 | RESERVED | R/W | X | |
1 | AFGC | R | 0h | Relevant only when ACS Capability is supported. This field is hardwired to 0. |
0 | MFGC | R | 0h | Set when device supports arbitration at the Function Group-level. This field is hardwired to 0. |
PCIE_CORE_PFn_RSVD_052_053 is shown in Figure 12-1326 and described in Table 12-2590.
Return to the Summary Table.
Reserved
Offset = 148h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0148h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_DEV_SER_NUM_CAP_HDR is shown in Figure 12-1327 and described in Table 12-2592.
Return to the Summary Table.
This register contains the PCI Express Extended Capability ID for Device Serial Number
Capability, the capability version, and the pointer to the next capability structure.
Offset = 150h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0150h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
SNNCO | DSNCV | ||||||||||||||
R/W-160h | R/W-1h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
PECID | |||||||||||||||
R-3h | |||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | SNNCO | R/W | 160h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | DSNCV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified from the local management bus by writing into Function 0 from the local management bus. |
15-0 | PECID | R | 3h | This field is hardwired to the Capability ID assigned by PCI SIG to the PCI Express Device Serial Number Capability [0001 hex]. |
PCIE_CORE_PFn_I_DEV_SER_NUM_0 is shown in Figure 12-1328 and described in Table 12-2594.
Return to the Summary Table.
This read-only register stored the first 32 bits of the device's serial number. Its
setting is common for all the Physical Functions, and can be modified by writing into this
register in Function 0 from the local management bus.
Offset = 154h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0154h + formula |
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 |
DSND0 | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | DSND0 | R/W | 0h | This field contains the first 32 bits of the device's serial number. |
PCIE_CORE_PFn_I_DEV_SER_NUM_1 is shown in Figure 12-1329 and described in Table 12-2596.
Return to the Summary Table.
This read-only register stored the last 32 bits of the device's serial number. Its
setting is common for all the Physical Functions, and can be modified by writing into this
register in Function 0 from the local management bus.
Offset = 158h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0158h + formula |
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 |
DSND1 | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | DSND1 | R/W | 0h | This field contains the last 32 bits of the device's serial number. |
PCIE_CORE_PFn_RSVD_057 is shown in Figure 12-1330 and described in Table 12-2598.
Return to the Summary Table.
Reserved
Offset = 15Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 015Ch + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_PWR_BDGTG_ENHC_CAP_HDR is shown in Figure 12-1331 and described in Table 12-2600.
Return to the Summary Table.
This register contains the PCI Express Extended Capability ID for Power Budgeting
Capability, its capability version, and the pointer to the next capability structure.
Offset = 160h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0160h + formula |
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 |
PBNCO | PCV | PECID | |||||||||||||||||||||||||||||
R/W-1B8h | R/W-1h | R-4h | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | PBNCO | R/W | 1B8h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | PCV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified from the local management bus by writing into Function 0 from the local management bus. |
15-0 | PECID | R | 4h | This field is hardwired to the Capability ID assigned by PCI SIG to the PCI Express Power Budgeting Capability [0004 hex]. |
PCIE_CORE_PFn_I_PWR_BDGTG_DATA_SEL is shown in Figure 12-1332 and described in Table 12-2602.
Return to the Summary Table.
This register is used to select the specific word of specific power-budgeting data
returned on a read from the Power Budgeting Data Register. This version of the Controller stores power
budgeting data for three distinct power states (D0, D1 and D3hot ) for each Physical Function,
which can be read from the Power Budgeting Data Register by indexing through this register, as
described below.
Offset = 164h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0164h + formula |
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 |
R0 | PBDN | ||||||||||||||||||||||||||||||
R-0h | R/W-0h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-8 | R0 | R | 0h | N/A |
7-0 | PBDN | R/W | 0h | This field selects the power budgeting data read from the Power Budgeting Data Register. Its settings are: 00: Selects power budgeting data for power state D0 MAX for the associated PF. 01: Selects power budgeting data for power state D0 SUSTAINED for the associated PF. 10: Selects power budgeting data for power state D3hot for the associated PF. 11: Selects power budgeting data for power state D1 for the associated PF. Others: Not a valid setting. A read from the Power Budgeting Data Register returns all zeroes. |
PCIE_CORE_PFn_I_PWR_BDGTG_DATA_REGISTER is shown in Figure 12-1333 and described in Table 12-2604.
Return to the Summary Table.
This read-only register returns the DWORD of Power Budgeting Data selected by the Data Select
register. Each DWORD of the Power Budgeting Data describes the power usage of the device in a
particular operating condition. All the fields can be modified independently for each PF by writing from the
local management bus.
Offset = 168h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0168h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R1 | PR | TYPE | |||||||||||||
R-0h | R/W-2h | R/W-7h | |||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
TYPE | PS | PSS | DS | BP | |||||||||||
R/W-7h | R/W-0h | R/W-0h | R/W-0h | R/W-F0h | |||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-21 | R1 | R | 0h | Reserved |
20-18 | PR | R/W | 2h | Specifies the power rail corresponding to the power management data in this register. |
17-15 | TYPE | R/W | 7h | Specifies the operation condition for which the data applies. |
14-13 | PS | R/W | 0h | Specifies the power management state of the Function, for which this power management data applies. |
12-10 | PSS | R/W | 0h | Specifies the power management sub-state of the selected power state |
9-8 | DS | R/W | 0h | Scale factor applicable to the Base Power field. |
7-0 | BP | R/W | F0h | Specifies base power[in watts] of the selected power state |
PCIE_CORE_PFn_I_PWR_BDGT_CAP is shown in Figure 12-1334 and described in Table 12-2606.
Return to the Summary Table.
This register specifies whether the device power specified by this Capability Structure
is included in the system power budget.
Offset = 16Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 016Ch + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R4 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R4 | SA | ||||||||||||||
R-0h | R/W-0h | ||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-1 | R4 | R | 0h | Reserved |
0 | SA | R/W | 0h | This bit is set to indicate that the device power specified by this Power Management Capability Structure is included in the system power budget. When this bit set, the software must exclude the device power reported by this Capability Structure from power calculations, when making power budgeting decisions. This bit is set to 0 by default, but its setting can be modified individually for each PF from the local management bus. |
PCIE_CORE_PFn_RSVD_05C_05F is shown in Figure 12-1335 and described in Table 12-2608.
Return to the Summary Table.
Reserved
Offset = 170h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0170h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_RESIZE_BAR_EXT_CAP_HDR is shown in Figure 12-1336 and described in Table 12-2610.
Return to the Summary Table.
This register contains the PCI Express Extended Capability ID for the Resizable BAR
Capability, its capability version, and the pointer to the next capability structure. This
register is enabled only when the Resizable BAR Capability is enabled for the Physical Function
by setting the Enable Resizable BAR Capability bit (bit 31) of the associated Physical Function
BAR Configuration Register (Section 8.4.2.24). When the Resizable BAR Capability is not enabled,
a read from this location returns all zeroes.
Offset = 180h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0180h + formula |
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 |
NCO | CV | PECID | |||||||||||||||||||||||||||||
R-0h | R-0h | R-0h | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R | 0h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R | 0h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified from the local management bus. |
15-0 | PECID | R | 0h | This field is hardwired to the Capability ID assigned by PCI SIG to the Resizable BAR Capability [0015 hex]. |
PCIE_CORE_PFn_I_RESIZE_BAR_CAP_0 is shown in Figure 12-1337 and described in Table 12-2612.
Return to the Summary Table.
This register advertises the available aperture settings of the first memory BAR of the
associated Physical Function. This register is active only when the Resizable BAR Capability
is enabled for the Physical Function by setting the Enable Resizable BAR Capability (bit 31) of
the associated Physical Function BAR Configuration Register 1. When the Resizable BAR Capability
is not enabled, a read from this location returns all zeros. When the Resizable BAR Capability
is enabled, any of the bits 4-22 can be modified from the local management bus.
Offset = 184h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0184h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R1 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
A512G | A256G | A128G | A64G | A32G | A16G | A8G | A4G |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
A2G | A1G | A512M | A256M | A128M | A64M | A32M | A16M |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
A8M | A4M | A2M | A1M | R0 | |||
R-0h | R-0h | R-0h | R-0h | R-0h | |||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | R1 | R | 0h | Reserved |
23 | A512G | R | 0h | Indicates that the BAR aperture can be set to 512G. |
22 | A256G | R | 0h | Indicates that the BAR aperture can be set to 256G. |
21 | A128G | R | 0h | Indicates that the BAR aperture can be set to 128G. |
20 | A64G | R | 0h | Indicates that the BAR aperture can be set to 64G. |
19 | A32G | R | 0h | Indicates that the BAR aperture can be set to 32G. |
18 | A16G | R | 0h | Indicates that the BAR aperture can be set to 16G. |
17 | A8G | R | 0h | Indicates that the BAR aperture can be set to 8G. |
16 | A4G | R | 0h | Indicates that the BAR aperture can be set to 4G. |
15 | A2G | R | 0h | Indicates that the BAR aperture can be set to 2G. |
14 | A1G | R | 0h | Indicates that the BAR aperture can be set to 1G. |
13 | A512M | R | 0h | Indicates that the BAR aperture can be set to 512M. |
12 | A256M | R | 0h | Indicates that the BAR aperture can be set to 256M. |
11 | A128M | R | 0h | Indicates that the BAR aperture can be set to 128M. |
10 | A64M | R | 0h | Indicates that the BAR aperture can be set to 64M. |
9 | A32M | R | 0h | Indicates that the BAR aperture can be set to 32M. |
8 | A16M | R | 0h | Indicates that the BAR aperture can be set to 16M. |
7 | A8M | R | 0h | Indicates that the BAR aperture can be set to 8M. |
6 | A4M | R | 0h | Indicates that the BAR aperture can be set to 4M. |
5 | A2M | R | 0h | Indicates that the BAR aperture can be set to 2M. |
4 | A1M | R | 0h | Indicates that the BAR aperture can be set to 1M. |
3-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PFn_I_RESIZE_BAR_CTRL_0 is shown in Figure 12-1338 and described in Table 12-2614.
Return to the Summary Table.
This register controls the aperture setting of the first memory BAR of the associated
Physical Function, and also has a field that specifies the number of resizable BARs configurable
through the Resizable BAR Capability Structure. This register is active only when the Resizable
BAR Capability is enabled for the Physical Function by setting the Enable Resizable BAR Capability
bit (bit 31) of the associated Physical Function BAR Configuration Register. When the Resizable BAR
Capability is not enabled, a read from this location returns all zeroes. When the Resizable BAR
Capability is enabled, all valid fields of this register can be modified from the local
management bus.
Offset = 188h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0188h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R3 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R3 | BARS | RBARC | R2 | BARI | |||||||||||
R-0h | R-0h | R-0h | R-0h | R-0h | |||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-13 | R3 | R | 0h | Reserved |
12-8 | BARS | R | 0h | When the Resizable BAR Capability is enabled for the Physical Function, this field controls the BAR aperture for the first BAR of the PF [0 = 1M, 1 = 2M, ... , 12 = 4G]. This field can be modified independently for each PF from the local management bus. |
7-5 | RBARC | R | 0h | Specifies the number of BARs that can be configured through the Resizable BAR Capability Structure for this PF. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_COUNT values [where x is the function number] for default values of each function in the reg_defaults.v files. |
4-3 | R2 | R | 0h | Reserved |
2-0 | BARI | R | 0h | Specifies the index of the BAR controlled by this register. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_CONTROL_REG0_BAR_INDEX values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_RESIZE_BAR_CAP_1 is shown in Figure 12-1339 and described in Table 12-2616.
Return to the Summary Table.
This register advertises the available aperture settings of the first memory BAR of the
associated Physical Function. This register is active only when the Resizable BAR Capability
is enabled for the Physical Function by setting the Enable Resizable BAR Capability (bit 31) of
the associated Physical Function BAR Configuration Register 1. When the Resizable BAR Capability
is not enabled, a read from this location returns all zeros. When the Resizable BAR Capability
is enabled, any of the bits 4-22 can be modified from the local management bus.
Offset = 18Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 018Ch + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R1 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
A512G | A256G | A128G | A64G | A32G | A16G | A8G | A4G |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
A2G | A1G | A512M | A256M | A128M | A64M | A32M | A16M |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
A8M | A4M | A2M | A1M | R0 | |||
R-0h | R-0h | R-0h | R-0h | R-0h | |||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | R1 | R | 0h | Reserved |
23 | A512G | R | 0h | Indicates that the BAR aperture can be set to 512G. |
22 | A256G | R | 0h | Indicates that the BAR aperture can be set to 256G. |
21 | A128G | R | 0h | Indicates that the BAR aperture can be set to 128G. |
20 | A64G | R | 0h | Indicates that the BAR aperture can be set to 64G. |
19 | A32G | R | 0h | Indicates that the BAR aperture can be set to 32G. |
18 | A16G | R | 0h | Indicates that the BAR aperture can be set to 16G. |
17 | A8G | R | 0h | Indicates that the BAR aperture can be set to 8G. |
16 | A4G | R | 0h | Indicates that the BAR aperture can be set to 4G. |
15 | A2G | R | 0h | Indicates that the BAR aperture can be set to 2G. |
14 | A1G | R | 0h | Indicates that the BAR aperture can be set to 1G. |
13 | A512M | R | 0h | Indicates that the BAR aperture can be set to 512M. |
12 | A256M | R | 0h | Indicates that the BAR aperture can be set to 256M. |
11 | A128M | R | 0h | Indicates that the BAR aperture can be set to 128M. |
10 | A64M | R | 0h | Indicates that the BAR aperture can be set to 64M. |
9 | A32M | R | 0h | Indicates that the BAR aperture can be set to 32M. |
8 | A16M | R | 0h | Indicates that the BAR aperture can be set to 16M. |
7 | A8M | R | 0h | Indicates that the BAR aperture can be set to 8M. |
6 | A4M | R | 0h | Indicates that the BAR aperture can be set to 4M. |
5 | A2M | R | 0h | Indicates that the BAR aperture can be set to 2M. |
4 | A1M | R | 0h | Indicates that the BAR aperture can be set to 1M. |
3-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PFn_I_RESIZE_BAR_CTRL_1 is shown in Figure 12-1340 and described in Table 12-2618.
Return to the Summary Table.
This register controls the aperture setting of the first memory BAR of the associated
Physical Function, and also has a field that specifies the number of resizable BARs configurable
through the Resizable BAR Capability Structure. This register is active only when the Resizable
BAR Capability is enabled for the Physical Function by setting the Enable Resizable BAR Capability
bit (bit 31) of the associated Physical Function BAR Configuration Register. When the Resizable BAR
Capability is not enabled, a read from this location returns all zeroes. When the Resizable BAR
Capability is enabled, all valid fields of this register can be modified from the local
management bus.
Offset = 190h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0190h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R3 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R3 | BARS | RBARC | R2 | BARI | |||||||||||
R-0h | R-0h | R-0h | R-0h | R-0h | |||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-13 | R3 | R | 0h | Reserved |
12-8 | BARS | R | 0h | When the Resizable BAR Capability is enabled for the Physical Function, this field controls the BAR aperture for the first BAR of the PF [0 = 1M, 1 = 2M, ... , 12 = 4G]. This field can be modified independently for each PF from the local management bus. |
7-5 | RBARC | R | 0h | Specifies the number of BARs that can be configured through the Resizable BAR Capability Structure for this PF. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_COUNT values [where x is the function number] for default values of each function in the reg_defaults.v files. |
4-3 | R2 | R | 0h | Reserved |
2-0 | BARI | R | 0h | Specifies the index of the BAR controlled by this register. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_CONTROL_REG0_BAR_INDEX values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_RESIZE_BAR_CAP_2 is shown in Figure 12-1341 and described in Table 12-2620.
Return to the Summary Table.
This register advertises the available aperture settings of the first memory BAR of the
associated Physical Function. This register is active only when the Resizable BAR Capability
is enabled for the Physical Function by setting the Enable Resizable BAR Capability (bit 31) of
the associated Physical Function BAR Configuration Register 1. When the Resizable BAR Capability
is not enabled, a read from this location returns all zeros. When the Resizable BAR Capability
is enabled, any of the bits 4-22 can be modified from the local management bus.
Offset = 194h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0194h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R1 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
A512G | A256G | A128G | A64G | A32G | A16G | A8G | A4G |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
A2G | A1G | A512M | A256M | A128M | A64M | A32M | A16M |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
A8M | A4M | A2M | A1M | R0 | |||
R-0h | R-0h | R-0h | R-0h | R-0h | |||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | R1 | R | 0h | Reserved |
23 | A512G | R | 0h | Indicates that the BAR aperture can be set to 512G. |
22 | A256G | R | 0h | Indicates that the BAR aperture can be set to 256G. |
21 | A128G | R | 0h | Indicates that the BAR aperture can be set to 128G. |
20 | A64G | R | 0h | Indicates that the BAR aperture can be set to 64G. |
19 | A32G | R | 0h | Indicates that the BAR aperture can be set to 32G. |
18 | A16G | R | 0h | Indicates that the BAR aperture can be set to 16G. |
17 | A8G | R | 0h | Indicates that the BAR aperture can be set to 8G. |
16 | A4G | R | 0h | Indicates that the BAR aperture can be set to 4G. |
15 | A2G | R | 0h | Indicates that the BAR aperture can be set to 2G. |
14 | A1G | R | 0h | Indicates that the BAR aperture can be set to 1G. |
13 | A512M | R | 0h | Indicates that the BAR aperture can be set to 512M. |
12 | A256M | R | 0h | Indicates that the BAR aperture can be set to 256M. |
11 | A128M | R | 0h | Indicates that the BAR aperture can be set to 128M. |
10 | A64M | R | 0h | Indicates that the BAR aperture can be set to 64M. |
9 | A32M | R | 0h | Indicates that the BAR aperture can be set to 32M. |
8 | A16M | R | 0h | Indicates that the BAR aperture can be set to 16M. |
7 | A8M | R | 0h | Indicates that the BAR aperture can be set to 8M. |
6 | A4M | R | 0h | Indicates that the BAR aperture can be set to 4M. |
5 | A2M | R | 0h | Indicates that the BAR aperture can be set to 2M. |
4 | A1M | R | 0h | Indicates that the BAR aperture can be set to 1M. |
3-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PFn_I_RESIZE_BAR_CTRL_2 is shown in Figure 12-1342 and described in Table 12-2622.
Return to the Summary Table.
This register controls the aperture setting of the first memory BAR of the associated
Physical Function, and also has a field that specifies the number of resizable BARs configurable
through the Resizable BAR Capability Structure. This register is active only when the Resizable
BAR Capability is enabled for the Physical Function by setting the Enable Resizable BAR Capability
bit (bit 31) of the associated Physical Function BAR Configuration Register. When the Resizable BAR
Capability is not enabled, a read from this location returns all zeroes. When the Resizable BAR
Capability is enabled, all valid fields of this register can be modified from the local
management bus.
Offset = 198h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0198h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R3 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R3 | BARS | RBARC | R2 | BARI | |||||||||||
R-0h | R-0h | R-0h | R-0h | R-0h | |||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-13 | R3 | R | 0h | Reserved |
12-8 | BARS | R | 0h | When the Resizable BAR Capability is enabled for the Physical Function, this field controls the BAR aperture for the first BAR of the PF [0 = 1M, 1 = 2M, ... , 12 = 4G]. This field can be modified independently for each PF from the local management bus. |
7-5 | RBARC | R | 0h | Specifies the number of BARs that can be configured through the Resizable BAR Capability Structure for this PF. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_COUNT values [where x is the function number] for default values of each function in the reg_defaults.v files. |
4-3 | R2 | R | 0h | Reserved |
2-0 | BARI | R | 0h | Specifies the index of the BAR controlled by this register. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_CONTROL_REG0_BAR_INDEX values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_RESIZE_BAR_CAP_3 is shown in Figure 12-1343 and described in Table 12-2624.
Return to the Summary Table.
This register advertises the available aperture settings of the first memory BAR of the
associated Physical Function. This register is active only when the Resizable BAR Capability
is enabled for the Physical Function by setting the Enable Resizable BAR Capability (bit 31) of
the associated Physical Function BAR Configuration Register 1. When the Resizable BAR Capability
is not enabled, a read from this location returns all zeros. When the Resizable BAR Capability
is enabled, any of the bits 4-22 can be modified from the local management bus.
Offset = 19Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 019Ch + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R1 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
A512G | A256G | A128G | A64G | A32G | A16G | A8G | A4G |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
A2G | A1G | A512M | A256M | A128M | A64M | A32M | A16M |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
A8M | A4M | A2M | A1M | R0 | |||
R-0h | R-0h | R-0h | R-0h | R-0h | |||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | R1 | R | 0h | Reserved |
23 | A512G | R | 0h | Indicates that the BAR aperture can be set to 512G. |
22 | A256G | R | 0h | Indicates that the BAR aperture can be set to 256G. |
21 | A128G | R | 0h | Indicates that the BAR aperture can be set to 128G. |
20 | A64G | R | 0h | Indicates that the BAR aperture can be set to 64G. |
19 | A32G | R | 0h | Indicates that the BAR aperture can be set to 32G. |
18 | A16G | R | 0h | Indicates that the BAR aperture can be set to 16G. |
17 | A8G | R | 0h | Indicates that the BAR aperture can be set to 8G. |
16 | A4G | R | 0h | Indicates that the BAR aperture can be set to 4G. |
15 | A2G | R | 0h | Indicates that the BAR aperture can be set to 2G. |
14 | A1G | R | 0h | Indicates that the BAR aperture can be set to 1G. |
13 | A512M | R | 0h | Indicates that the BAR aperture can be set to 512M. |
12 | A256M | R | 0h | Indicates that the BAR aperture can be set to 256M. |
11 | A128M | R | 0h | Indicates that the BAR aperture can be set to 128M. |
10 | A64M | R | 0h | Indicates that the BAR aperture can be set to 64M. |
9 | A32M | R | 0h | Indicates that the BAR aperture can be set to 32M. |
8 | A16M | R | 0h | Indicates that the BAR aperture can be set to 16M. |
7 | A8M | R | 0h | Indicates that the BAR aperture can be set to 8M. |
6 | A4M | R | 0h | Indicates that the BAR aperture can be set to 4M. |
5 | A2M | R | 0h | Indicates that the BAR aperture can be set to 2M. |
4 | A1M | R | 0h | Indicates that the BAR aperture can be set to 1M. |
3-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PFn_I_RESIZE_BAR_CTRL_3 is shown in Figure 12-1344 and described in Table 12-2626.
Return to the Summary Table.
This register controls the aperture setting of the first memory BAR of the associated
Physical Function, and also has a field that specifies the number of resizable BARs configurable
through the Resizable BAR Capability Structure. This register is active only when the Resizable
BAR Capability is enabled for the Physical Function by setting the Enable Resizable BAR Capability
bit (bit 31) of the associated Physical Function BAR Configuration Register. When the Resizable BAR
Capability is not enabled, a read from this location returns all zeroes. When the Resizable BAR
Capability is enabled, all valid fields of this register can be modified from the local
management bus.
Offset = 1A0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01A0h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R3 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R3 | BARS | RBARC | R2 | BARI | |||||||||||
R-0h | R-0h | R-0h | R-0h | R-0h | |||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-13 | R3 | R | 0h | Reserved |
12-8 | BARS | R | 0h | When the Resizable BAR Capability is enabled for the Physical Function, this field controls the BAR aperture for the first BAR of the PF [0 = 1M, 1 = 2M, ... , 12 = 4G]. This field can be modified independently for each PF from the local management bus. |
7-5 | RBARC | R | 0h | Specifies the number of BARs that can be configured through the Resizable BAR Capability Structure for this PF. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_COUNT values [where x is the function number] for default values of each function in the reg_defaults.v files. |
4-3 | R2 | R | 0h | Reserved |
2-0 | BARI | R | 0h | Specifies the index of the BAR controlled by this register. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_CONTROL_REG0_BAR_INDEX values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_RESIZE_BAR_CAP_4 is shown in Figure 12-1345 and described in Table 12-2628.
Return to the Summary Table.
This register advertises the available aperture settings of the first memory BAR of the
associated Physical Function. This register is active only when the Resizable BAR Capability
is enabled for the Physical Function by setting the Enable Resizable BAR Capability (bit 31) of
the associated Physical Function BAR Configuration Register 1. When the Resizable BAR Capability
is not enabled, a read from this location returns all zeros. When the Resizable BAR Capability
is enabled, any of the bits 4-22 can be modified from the local management bus.
Offset = 1A4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01A4h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R1 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
A512G | A256G | A128G | A64G | A32G | A16G | A8G | A4G |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
A2G | A1G | A512M | A256M | A128M | A64M | A32M | A16M |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
A8M | A4M | A2M | A1M | R0 | |||
R-0h | R-0h | R-0h | R-0h | R-0h | |||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | R1 | R | 0h | Reserved |
23 | A512G | R | 0h | Indicates that the BAR aperture can be set to 512G. |
22 | A256G | R | 0h | Indicates that the BAR aperture can be set to 256G. |
21 | A128G | R | 0h | Indicates that the BAR aperture can be set to 128G. |
20 | A64G | R | 0h | Indicates that the BAR aperture can be set to 64G. |
19 | A32G | R | 0h | Indicates that the BAR aperture can be set to 32G. |
18 | A16G | R | 0h | Indicates that the BAR aperture can be set to 16G. |
17 | A8G | R | 0h | Indicates that the BAR aperture can be set to 8G. |
16 | A4G | R | 0h | Indicates that the BAR aperture can be set to 4G. |
15 | A2G | R | 0h | Indicates that the BAR aperture can be set to 2G. |
14 | A1G | R | 0h | Indicates that the BAR aperture can be set to 1G. |
13 | A512M | R | 0h | Indicates that the BAR aperture can be set to 512M. |
12 | A256M | R | 0h | Indicates that the BAR aperture can be set to 256M. |
11 | A128M | R | 0h | Indicates that the BAR aperture can be set to 128M. |
10 | A64M | R | 0h | Indicates that the BAR aperture can be set to 64M. |
9 | A32M | R | 0h | Indicates that the BAR aperture can be set to 32M. |
8 | A16M | R | 0h | Indicates that the BAR aperture can be set to 16M. |
7 | A8M | R | 0h | Indicates that the BAR aperture can be set to 8M. |
6 | A4M | R | 0h | Indicates that the BAR aperture can be set to 4M. |
5 | A2M | R | 0h | Indicates that the BAR aperture can be set to 2M. |
4 | A1M | R | 0h | Indicates that the BAR aperture can be set to 1M. |
3-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PFn_I_RESIZE_BAR_CTRL_4 is shown in Figure 12-1346 and described in Table 12-2630.
Return to the Summary Table.
This register controls the aperture setting of the first memory BAR of the associated
Physical Function, and also has a field that specifies the number of resizable BARs configurable
through the Resizable BAR Capability Structure. This register is active only when the Resizable
BAR Capability is enabled for the Physical Function by setting the Enable Resizable BAR Capability
bit (bit 31) of the associated Physical Function BAR Configuration Register. When the Resizable BAR
Capability is not enabled, a read from this location returns all zeroes. When the Resizable BAR
Capability is enabled, all valid fields of this register can be modified from the local
management bus.
Offset = 1A8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01A8h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R3 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R3 | BARS | RBARC | R2 | BARI | |||||||||||
R-0h | R-0h | R-0h | R-0h | R-0h | |||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-13 | R3 | R | 0h | Reserved |
12-8 | BARS | R | 0h | When the Resizable BAR Capability is enabled for the Physical Function, this field controls the BAR aperture for the first BAR of the PF [0 = 1M, 1 = 2M, ... , 12 = 4G]. This field can be modified independently for each PF from the local management bus. |
7-5 | RBARC | R | 0h | Specifies the number of BARs that can be configured through the Resizable BAR Capability Structure for this PF. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_COUNT values [where x is the function number] for default values of each function in the reg_defaults.v files. |
4-3 | R2 | R | 0h | Reserved |
2-0 | BARI | R | 0h | Specifies the index of the BAR controlled by this register. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_CONTROL_REG0_BAR_INDEX values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_RESIZE_BAR_CAP_5 is shown in Figure 12-1347 and described in Table 12-2632.
Return to the Summary Table.
This register advertises the available aperture settings of the first memory BAR of the
associated Physical Function. This register is active only when the Resizable BAR Capability
is enabled for the Physical Function by setting the Enable Resizable BAR Capability (bit 31) of
the associated Physical Function BAR Configuration Register 1. When the Resizable BAR Capability
is not enabled, a read from this location returns all zeros. When the Resizable BAR Capability
is enabled, any of the bits 4-22 can be modified from the local management bus.
Offset = 1ACh + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01ACh + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R1 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
A512G | A256G | A128G | A64G | A32G | A16G | A8G | A4G |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
A2G | A1G | A512M | A256M | A128M | A64M | A32M | A16M |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
A8M | A4M | A2M | A1M | R0 | |||
R-0h | R-0h | R-0h | R-0h | R-0h | |||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | R1 | R | 0h | Reserved |
23 | A512G | R | 0h | Indicates that the BAR aperture can be set to 512G. |
22 | A256G | R | 0h | Indicates that the BAR aperture can be set to 256G. |
21 | A128G | R | 0h | Indicates that the BAR aperture can be set to 128G. |
20 | A64G | R | 0h | Indicates that the BAR aperture can be set to 64G. |
19 | A32G | R | 0h | Indicates that the BAR aperture can be set to 32G. |
18 | A16G | R | 0h | Indicates that the BAR aperture can be set to 16G. |
17 | A8G | R | 0h | Indicates that the BAR aperture can be set to 8G. |
16 | A4G | R | 0h | Indicates that the BAR aperture can be set to 4G. |
15 | A2G | R | 0h | Indicates that the BAR aperture can be set to 2G. |
14 | A1G | R | 0h | Indicates that the BAR aperture can be set to 1G. |
13 | A512M | R | 0h | Indicates that the BAR aperture can be set to 512M. |
12 | A256M | R | 0h | Indicates that the BAR aperture can be set to 256M. |
11 | A128M | R | 0h | Indicates that the BAR aperture can be set to 128M. |
10 | A64M | R | 0h | Indicates that the BAR aperture can be set to 64M. |
9 | A32M | R | 0h | Indicates that the BAR aperture can be set to 32M. |
8 | A16M | R | 0h | Indicates that the BAR aperture can be set to 16M. |
7 | A8M | R | 0h | Indicates that the BAR aperture can be set to 8M. |
6 | A4M | R | 0h | Indicates that the BAR aperture can be set to 4M. |
5 | A2M | R | 0h | Indicates that the BAR aperture can be set to 2M. |
4 | A1M | R | 0h | Indicates that the BAR aperture can be set to 1M. |
3-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PFn_I_RESIZE_BAR_CTRL_5 is shown in Figure 12-1348 and described in Table 12-2634.
Return to the Summary Table.
This register controls the aperture setting of the first memory BAR of the associated
Physical Function, and also has a field that specifies the number of resizable BARs configurable
through the Resizable BAR Capability Structure. This register is active only when the Resizable
BAR Capability is enabled for the Physical Function by setting the Enable Resizable BAR Capability
bit (bit 31) of the associated Physical Function BAR Configuration Register. When the Resizable BAR
Capability is not enabled, a read from this location returns all zeroes. When the Resizable BAR
Capability is enabled, all valid fields of this register can be modified from the local
management bus.
Offset = 1B0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01B0h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R3 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R3 | BARS | RBARC | R2 | BARI | |||||||||||
R-0h | R-0h | R-0h | R-0h | R-0h | |||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-13 | R3 | R | 0h | Reserved |
12-8 | BARS | R | 0h | When the Resizable BAR Capability is enabled for the Physical Function, this field controls the BAR aperture for the first BAR of the PF [0 = 1M, 1 = 2M, ... , 12 = 4G]. This field can be modified independently for each PF from the local management bus. |
7-5 | RBARC | R | 0h | Specifies the number of BARs that can be configured through the Resizable BAR Capability Structure for this PF. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_COUNT values [where x is the function number] for default values of each function in the reg_defaults.v files. |
4-3 | R2 | R | 0h | Reserved |
2-0 | BARI | R | 0h | Specifies the index of the BAR controlled by this register. This field can be modified independently for each PF from the local management bus. Please see the define den_db_Fx_RESIZABLE_BAR_CONTROL_REG0_BAR_INDEX values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PF0_I_LTR_EXT_CAP_HDR is shown in Figure 12-1349 and described in Table 12-2636.
Return to the Summary Table.
This register contains the PCI Express Extended Capability ID for the Latency Tolerance
Reporting (LTR) Capability, its capability version, and the pointer to the next capability
structure. This register is implemented only for Physical Function 0. A read from this address
of other Physical Functions configuration space returns all zeroes.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01B8h |
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 |
NCO | CV | PECID | |||||||||||||||||||||||||||||
R/W-1C0h | R/W-1h | R-18h | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 1C0h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified from the local management bus. |
15-0 | PECID | R | 18h | This field is hardwired to the Capability ID assigned by PCI SIG to the Latency Tolerance Reporting Capability [0018 hex]. |
PCIE_CORE_PF0_I_LTR_SNOOP_LAT is shown in Figure 12-1350 and described in Table 12-2638.
Return to the Summary Table.
This register contains the maximum snoop latency and the maximum no-snoop latency that
the device is allowed to request in an LTR message it originates.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01BCh |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R1 | MNSLS | MNSL | |||||||||||||
R-0h | R/W-0h | R/W-0h | |||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | MSLS | MSL | |||||||||||||
R-0h | R/W-0h | R/W-0h | |||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-29 | R1 | R | 0h | Reserved |
28-26 | MNSLS | R/W | 0h | Specifies the scale value for the Max No-Snoop Latency. When the setting of this field is non-zero, the actual snoop latency is determined by multiplying the Max No-Snoop Latency by the following scale factors: 001: 32 ns, 010: 1024 ns, 011: 32,768 ns, 100: 1,047,576 ns, 101: 33,554,432 ns, 110- 111: Reserved |
25-16 | MNSL | R/W | 0h | When multiplied by the value of the Max No-Snoop Latency Scale, this field defines the maximum no-snoop value the device is permitted to request in an LTR message. This field can be written independently for each Physical Function from the local management bus. |
15-13 | R0 | R | 0h | Reserved |
12-10 | MSLS | R/W | 0h | Specifies the scale value for the Max Snoop Latency. When the setting of this field is non-zero, the actual snoop latency is determined by multiplying the Max Snoop Latency by the following scale factors: 001: 32 ns, 010: 1024 ns, 011: 32,768 ns, 100: 1,047,576 ns, 101: 33,554,432 ns, 110- 111: Reserved |
9-0 | MSL | R/W | 0h | When multiplied by the value of the Max Snoop Latency Scale, this field defines the maximum snoop value the device is permitted to request in an LTR message. This field can be written independently for each Physical Function from the local management bus. |
PCIE_CORE_PFn_I_DPA_EXT_CAP_HEADER_REG is shown in Figure 12-1351 and described in Table 12-2640.
Return to the Summary Table.
This location contains the PCI Express Extended Capability ID for DPA Capability and the
offset to the next capability block.
Offset = 1C0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01C0h + formula |
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 |
NCO | CV | PECID | |||||||||||||||||||||||||||||
R/W-200h | R/W-1h | R-16h | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 200h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified from the local management bus. |
15-0 | PECID | R | 16h | This field is hardwired to the Capability ID assigned by PCI SIG to the Dynamic Power Allocation Reporting Capability |
PCIE_CORE_PFn_I_DPA_CAP_REG is shown in Figure 12-1352 and described in Table 12-2642.
Return to the Summary Table.
This register contains the DPA capability parameters for the associated Function.
Offset = 1C4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01C4h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
TLV1 | TLV0 | ||||||||||||||
R/W-8h | R/W-10h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R2 | PAS | R1 | TLU | R0 | MNS | ||||||||||
R-0h | R/W-0h | R-0h | R/W-0h | R-0h | R/W-7h | ||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | TLV1 | R/W | 8h | Specifies the second of the two transition latency values for the substates. The unit of latency is specified by the Transition Latency Unit field of this register. Please see the define den_db_Fx_DPA_CAPABILITY_REG_TRANSITION_VALUE1 values [where x is the function number] for default values of each function in the reg_defaults.v files. |
23-16 | TLV0 | R/W | 10h | Specifies the transition latency for the substate. Each of the 32 substates may specify one of the two transition latency values. This field contains the first of the two latency values. The unit of latency is specified by the Transition Latency Unit field of this register. Please see the define den_db_Fx_DPA_CAPABILITY_REG_TRANSITION_VALUE0 values [where x is the function number] for default values of each function in the reg_defaults.v files. |
15-14 | R2 | R | 0h | Reserved |
13-12 | PAS | R/W | 0h | This is the scale used to compute the actual power from the values specified in the Dynamic Power Allocation Array Registers 0 - 7. The actual power in Watts is obtained by multiplying the value in the Dynamic Power Allocation Array Register by this scale factor [00 = 10x, 01 = 1x, 10 = 0.1x, 11 = 0.01x]. Please see the define den_db_Fx_DPA_CAPABILITY_REG_POWER_ALLOCATION_SCALE values [where x is the function number] for default values of each function in the reg_defaults.v files. |
11-10 | R1 | R | 0h | Reserved |
9-8 | TLU | R/W | 0h | This is the unit of the transition latencies specified in the Transition Latency Value 0 and Transition Latency Value 1 fields of this register [ 00 = 1 ms, 01 = 10 ms, 10 = 100 ms, 11 = reserved]. Please see the define den_db_Fx_DPA_CAPABILITY_REG_TRANSITION_LATENCY_UNIT values [where x is the function number] for default values of each function in the reg_defaults.v files. |
7-5 | R0 | R | 0h | Reserved |
4-0 | MNS | R/W | 7h | Maximum number of DPA substates supported by the Function [the value in this field is the number of substates minus 1]. Please see the define den_db_Fx_DPA_CAPABILITY_REG_SUBSTATE_MAX values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_DPA_LAT_INDICATOR_REG is shown in Figure 12-1353 and described in Table 12-2644.
Return to the Summary Table.
This location contains Transition Latency Indicator bits for the DPA substates.
Offset = 1C8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01C8h + formula |
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 |
TLIN | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | TLIN | R/W | 0h | Bit i of this register indicates the choice of the transition latency value for substate i. A setting of 0 indicates that Transition Latency Value 0 from the DPA Capability Register applies to this substate a setting of 1 indicates that Transition Latency Value 1 applies. Please see the define den_db_Fx_DPA_TRANSITION_LATENCY values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_DPA_CTRL_STATUS_REG is shown in Figure 12-1354 and described in Table 12-2646.
Return to the Summary Table.
This location contains the DPA Control Register and the DPA Status Register.
Offset = 1CCh + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01CCh + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R5 | SC | ||||||||||||||
R-0h | R/W-0h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R4 | SCE | R3 | SS | ||||||||||||
R-0h | R/W-1h | R-0h | R/W-0h | ||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-21 | R5 | R | 0h | Reserved |
20-16 | SC | R/W | 0h | This field is used to initiate a transition of the Function's DPA to a new substate. To initiate the transition, software must write the desired substate value into this field and wait for the transition latency of the substate for the Function to complete the transition. This field can also be written from the local management bus. All substate transitions are disabled when the Substate Control Enabled bit is 0. The Controller generates a one-cycle pulse on the output DPA_INTERRUPT when the value if this field is changed [bit 0 is for PF 0 and so on] This interrupt informs the client of the request from software to change the DPA substate. In response, the client must read the Substate Control field from this register to determine the new substate, and perform the actions necessary to effect the substate change. On completion of the substate change, the client must update the Substate Status field to reflect the new substate the function is in. |
15-9 | R4 | R | 0h | Reserved |
8 | SCE | R/W | 1h | This bit enables the Substate Control field. This bit is initialized to 1 by the hardware on a power-on reset or a Function-Level Reset. Software may clear this bit by writing a 1 to this bit position, but cannot set this bit directly through a configuration write. Clearing this bit disables the Substate Control field, thus preventing further substate transitions for this Function. This bit can be set to 0 or 1 through the local management bus, by writing a 0 or 1, respectively. |
7-5 | R3 | R | 0h | Reserved |
4-0 | SS | R/W | 0h | This field provides the current DPA substate of this Function. This field is writable from the local management bus, and must be updated by the local software running on the EndPoint upon completion of a DPA transition to a new substate. |
PCIE_CORE_PFn_I_DPA_POWER_ALLOC_REG0 is shown in Figure 12-1355 and described in Table 12-2648.
Return to the Summary Table.
This is a register in an array of 2registers that contain the power allocations
for the DPA substates. Each location contains power allocation values for four substates, 8 bits
per substate. The value in each 8-bit field, when multiplied by the Power Allocation Scale
programmed in the DPA Capability Register, provides the power associated with the corresponding
substate in Watts.
Offset = 1D0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01D0h + formula |
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 |
SPA3_0 | SPA2_0 | SPA1_0 | SPA0_0 | ||||||||||||||||||||||||||||
R/W-3h | R/W-2h | R/W-1h | R/W-0h | ||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | SPA3_0 | R/W | 3h | This field contains the power allocation for the DPA substate #3 covered by this register. This value, when multiplied by the Power Allocation Scale programmed in the DPA Capability Register, provides the power associated with the corresponding substate in Watts. |
23-16 | SPA2_0 | R/W | 2h | This field contains the power allocation for the DPA substate #2 covered by this register. This value, when multiplied by the Power Allocation Scale programmed in the DPA Capability Register, provides the power associated with the corresponding substate in Watts. |
15-8 | SPA1_0 | R/W | 1h | This field contains the power allocation for the DPA substate #1 covered by this register. This value, when multiplied by the Power Allocation Scale programmed in the DPA Capability Register, provides the power associated with the corresponding substate in Watts. |
7-0 | SPA0_0 | R/W | 0h | This field contains the power allocation for the DPA substate #0 covered by this register. This value, when multiplied by the Power Allocation Scale programmed in the DPA Capability Register, provides the power associated with the corresponding substate in Watts. |
PCIE_CORE_PFn_I_DPA_POWER_ALLOC_REG1 is shown in Figure 12-1356 and described in Table 12-2650.
Return to the Summary Table.
This is a register in an array of 2registers that contain the power allocations
for the DPA substates. Each location contains power allocation values for four substates, 8 bits
per substate. The value in each 8-bit field, when multiplied by the Power Allocation Scale
programmed in the DPA Capability Register, provides the power associated with the corresponding
substate in Watts.
Offset = 1D4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01D4h + formula |
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 |
SPA3_1 | SPA2_1 | SPA1_1 | SPA0_1 | ||||||||||||||||||||||||||||
R/W-7h | R/W-6h | R/W-5h | R/W-4h | ||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | SPA3_1 | R/W | 7h | This field contains the power allocation for the DPA substate #7 covered by this register. This value, when multiplied by the Power Allocation Scale programmed in the DPA Capability Register, provides the power associated with the corresponding substate in Watts. |
23-16 | SPA2_1 | R/W | 6h | This field contains the power allocation for the DPA substate #6 covered by this register. This value, when multiplied by the Power Allocation Scale programmed in the DPA Capability Register, provides the power associated with the corresponding substate in Watts. |
15-8 | SPA1_1 | R/W | 5h | This field contains the power allocation for the DPA substate #5 covered by this register. This value, when multiplied by the Power Allocation Scale programmed in the DPA Capability Register, provides the power associated with the corresponding substate in Watts. |
7-0 | SPA0_1 | R/W | 4h | This field contains the power allocation for the DPA substate #4 covered by this register. This value, when multiplied by the Power Allocation Scale programmed in the DPA Capability Register, provides the power associated with the corresponding substate in Watts. |
PCIE_CORE_PFn_RSVD_07C_07F is shown in Figure 12-1357 and described in Table 12-2652.
Return to the Summary Table.
Reserved
Offset = 1D8h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 01D8h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PFn_I_SRIOV_EXT_CAP_HEADER_REG is shown in Figure 12-1358 and described in Table 12-2654.
Return to the Summary Table.
This location contains the PCI Express Extended Capability ID for SR-IOV and the offset
to the next capability block.
Offset = 200h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0200h + formula |
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 |
NCO | CV | PECID | |||||||||||||||||||||||||||||
R/W-300h | R/W-1h | R-10h | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 300h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 1h | Specifies the SIG-assigned value for the version of the capability structure. This field is set by default to 1, but can be modified independently for each Function from the local management bus. |
15-0 | PECID | R | 10h | This field is hardwired to the Capability ID assigned by PCI-SIG to the SR-IOV Extended Capability Structure [0010 hex]. |
PCIE_CORE_PFn_I_SRIOV_CAP_REG is shown in Figure 12-1359 and described in Table 12-2656.
Return to the Summary Table.
This register defines various capabilities of the SR-IOV implementation.
Offset = 204h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0204h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | VFT10RS | ACHP | VFMC | ||||
R-0h | R-0h | R/W-1h | R-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-3 | RESERVED | R | 0h | Reserved |
2 | VFT10RS | R | 0h | If set all VFs associated with this PF supports 1-bit requester capability otherwise, the VF does not. This bit can be disabled using local management register. |
1 | ACHP | R/W | 1h | A 1 in this bit position indicates that the ARI Capable Hierarchy bit in the SR-IOV Control Register is preserved across certain power state transitions [see the PCI-SIG Single Root IO Virtualization and Sharing Specifications, Version 1.1, Section 3.3.3.5 for details]. This bit is set to 1 by default, but can be modified from the local management bus. |
0 | VFMC | R | 0h | Set when the Controller supports VF migration. Hardwired to 0. |
PCIE_CORE_PFn_I_SRIOV_CTRL_STATUS_REG is shown in Figure 12-1360 and described in Table 12-2658.
Return to the Summary Table.
This location contains the SR-IOV Control Register and the SR-IOV Status Register.
Offset = 208h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0208h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
SSR | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
SSR | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R15 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R15 | T10RE | ARIE | VFMSE | VFMIE | VFME | VFE | |
R-0h | R-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | |
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | SSR | R | 0h | Not implemented. |
15-6 | R15 | R | 0h | Reserved |
5 | T10RE | R | 0h | 10bit TAGs generation are not supported in this configuration. |
4 | ARIE | R/W | 0h | This bit enables the ARI mode for Virtual Functions. ARI Capable Hierarchy is only present in the lowest numbered PF which is enabled [for example PF0] and affects all PFs of the Device. ARI Capable Hierarchy is Read Only Zero in other PFs of a Device. |
3 | VFMSE | R/W | 0h | This bit must be set to allow access to the memory space of the VFs associated with this PF. |
2 | VFMIE | R/W | 0h | Not supported. Hardwired to 0 |
1 | VFME | R/W | 0h | Not supported. Hardwired to 0 |
0 | VFE | R/W | 0h | This bit must be set to enable the VFs associated with this PF. |
PCIE_CORE_PFn_I_INITIAL_TOTAL_VFS_REG is shown in Figure 12-1361 and described in Table 12-2660.
Return to the Summary Table.
This location contains registers that specify the initial and the total number Virtual
Functions (VFs) in the device.
Offset = 20Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 020Ch + formula |
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 |
RESERVED | TVF | RESERVED | IVF | ||||||||||||||||||||||||||||
R/W-X | R/W-4h | R/W-X | R/W-4h | ||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-21 | RESERVED | R/W | X | |
20-16 | TVF | R/W | 4h | This field contains the total number of VFs per PF. Its default setting is identical to that of InitialVFs. This field can be modified using local management registers. |
15-5 | RESERVED | R/W | X | |
4-0 | IVF | R/W | 4h | This field contains the initial number of VFs configured for each PF. This field can be modified using local management registers. Please see the define den_db_PFx_TOTAL_VF_COUNT values [where x is the function number] for default values of each function in the reg_defaults.v files. |
PCIE_CORE_PFn_I_FUNC_DEP_LINK_NUMVFS_REG is shown in Figure 12-1362 and described in Table 12-2662.
Return to the Summary Table.
This location contains the Function Dependency Link that defines VF dependencies, and
the NumVFs register that stores the number of VFs configured.
Offset = 210h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0210h + formula |
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 |
RESERVED | FDL | NVF | |||||||||||||||||||||||||||||
R/W-X | R/W-0h | R/W-0h | |||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | RESERVED | R/W | X | |
23-16 | FDL | R/W | 0h | This field is used to specify dependencies between PFs. It can be modified independently for each Function from the local management bus. Please see the define den_db_Fx_SR_IOV_FUNCTION_DEPENDENCY_LINK values [where x is the function number] for default values of each function in the reg_defaults.v files. |
15-0 | NVF | R/W | 0h | This field must be set by the software to the number of VFs that it wants to enable for each PF. This field can be changed only when the VF Enable bit in the SR-IOV Control Register is 0. Its value should not exceed the setting of TotalVFs for the corresponding Physical Function. This field can also be written from the local management bus. |
PCIE_CORE_PFn_I_VF_OFFSET_STRIDE_REG is shown in Figure 12-1363 and described in Table 12-2664.
Return to the Summary Table.
Specifies the offset and stride values for VF address assignment.
Offset = 214h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0214h + formula |
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 |
VFS | FVFO | ||||||||||||||||||||||||||||||
R-1h | R/W-6h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | VFS | R | 1h | Stride value used to assign RIDs for VFs. The stride value is hardwired to 1 for all Physical Functions. |
15-0 | FVFO | R/W | 6h | Offset of First VF relative to its PF. Modifying this field is not supported. |
PCIE_CORE_PFn_I_VF_DEVICE_ID_REG is shown in Figure 12-1364 and described in Table 12-2666.
Return to the Summary Table.
This register specifies the VF device id for the device.
Offset = 218h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0218h + formula |
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 |
VFDI | R2 | ||||||||||||||||||||||||||||||
R/W-100h | R-0h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | VFDI | R/W | 100h | VF device id assigned to the device. Its default value is specified in reg_defaults.h, but can be re-written independently for each PF from the local management bus. |
15-0 | R2 | R | 0h | Reserved |
PCIE_CORE_PFn_I_SUPPORTED_PAGE_SIZE_REG is shown in Figure 12-1365 and described in Table 12-2668.
Return to the Summary Table.
This register specifies all the page sizes supported by the device.
Offset = 21Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 021Ch + formula |
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 |
R0 | PS | ||||||||||||||||||||||||||||||
R-0h | R/W-553h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | R0 | R | 0h | Reserved |
15-0 | PS | R/W | 553h | Page sizes supported by the device [one bit for each page size]. The Controller implements only bits 15:0 of this register. The default value of this field is specified in reg_defaults.h, but can be re-written independently for each PF from the local management bus. |
PCIE_CORE_PFn_I_SYSTEM_PAGE_SIZE_REG is shown in Figure 12-1366 and described in Table 12-2670.
Return to the Summary Table.
This register identifies the page size currently used by the system.
Offset = 220h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0220h + formula |
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 |
R0 | SPS | ||||||||||||||||||||||||||||||
R-0h | R/W-1h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | R0 | R | 0h | Reserved |
15-0 | SPS | R/W | 1h | This field must be programmed by software to the current page size in use. The Controller implements only bits 15:0 of this register. This field can also be written from the local management bus. |
PCIE_CORE_PFn_I_VF_BAR_0_REG is shown in Figure 12-1367 and described in Table 12-2672.
Return to the Summary Table.
This is part of the set of six Virtual Function Base Address Registers defined
by the SR-IOV Specifications. These registers are used to define address ranges for memory
accesses to the Endpoint device. This register may be used to define a range of 32-bit addresses,
or paired with the next adjacent register to define a 64-bit address range.
During the initial configuration of the device, the configuration program determines the size of
the address range defined by the BAR by writing a pattern of all 1's into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned value.
A value of 0 is returned by the Controller if this BAR is not configured. Otherwise, the number of 1's returned
is based on the length of the BAR.
Offset = 224h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0224h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
BAMRW | BAMR0 | ||||||||||||||
R/W-0h | R-0h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
BAMR0 | R8 | P0 | S0 | R7 | MSI | ||||||||||
R-0h | R-0h | R-0h | R-1h | R-0h | R-0h | ||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-22 | BAMRW | R/W | 0h | This field defines the base address of the memory address range. The number of implemented bits in this field determines the BAR aperture configured in BAR Configuration Registers of the associated Physical Function. |
21-8 | BAMR0 | R | 0h | This field defines the base address of the memory address range. The number of implemented bits in this field determines the BAR aperture configured in BAR Configuration Registers of the associated Physical Function. All other bits are not writeable, and are read as 0's. |
7-4 | R8 | R | 0h | These bits are hardwired to 0 |
3 | P0 | R | 0h | When the BAR is used to define a memory address range, this field declares whether data from the address range is prefetchable [0 = non-prefetchable, 1 = prefetchable]. The value read in this field is determined by the setting of BAR Configuration Registers of the associated Physical Function |
2 | S0 | R | 1h | When the BAR is used to define a memory address range, this field indicates whether the address range is 32-bit or 64-bit [0 = 32-bit, 1 = 64 bit]. For 64-bit address ranges, the value in BAR 1 is treated as a continuation of the base address in BAR 0. The value read in this field is determined by the setting of BAR Configuration Registers of the associated Physical Function. |
1 | R7 | R | 0h | This bit is hardwired to 0 for both memory and I/O BARs. |
0 | MSI | R | 0h | Specifies whether this BAR defines a memory address range or an I/O address range [0 = memory, 1 = I/O]. The value read in this field is determined by the setting of BAR Configuration Registers of the associated Physical Function |
PCIE_CORE_PFn_I_VF_BAR_1_REG is shown in Figure 12-1368 and described in Table 12-2674.
Return to the Summary Table.
This is part of the set of six Virtual Function Base Address Registers defined
by the SR-IOV Specifications. These registers are used to define address ranges for memory
accesses to the Endpoint device. This register may be used to define a range of 32-bit addresses.
During the initial configuration of the device, the configuration program determines the size of
the address range defined by the BAR by writing a pattern of all 1's into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned value.
A value of 0 is returned by the Controller if this BAR is not configured. Otherwise, the number of 1's returned
is based on the length of the BAR.
Offset = 228h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0228h + formula |
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 |
BAMRW | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | BAMRW | R/W | 0h | This field defines the base address of the memory address range. The number of implemented bits in this field determines the BAR aperture setting of BAR Configuration Registers of the associated Physical Function. All other bits are not writeable, and are read as 0's. |
PCIE_CORE_PFn_I_VF_BAR_2_REG is shown in Figure 12-1369 and described in Table 12-2676.
Return to the Summary Table.
This is part of the set of six Virtual Function Base Address Registers defined
by the SR-IOV Specifications. These registers are used to define address ranges for memory
accesses to the Endpoint device. This register may be used to define a range of 32-bit addresses,
or paired with the next adjacent register to define a 64-bit address range.
During the initial configuration of the device, the configuration program determines the size of
the address range defined by the BAR by writing a pattern of all 1's into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned value.
A value of 0 is returned by the Controller if this BAR is not configured. Otherwise, the number of 1's returned
is based on the length of the BAR.
Offset = 22Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 022Ch + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_I_VF_BAR_3_REG is shown in Figure 12-1370 and described in Table 12-2678.
Return to the Summary Table.
This is part of the set of six Virtual Function Base Address Registers defined
by the SR-IOV Specifications. These registers are used to define address ranges for memory
accesses to the Endpoint device. This register may be used to define a range of 32-bit addresses.
During the initial configuration of the device, the configuration program determines the size of
the address range defined by the BAR by writing a pattern of all 1's into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned value.
A value of 0 is returned by the Controller if this BAR is not configured. Otherwise, the number of 1's returned
is based on the length of the BAR.
Offset = 230h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0230h + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_I_VF_BAR_4_REG is shown in Figure 12-1371 and described in Table 12-2680.
Return to the Summary Table.
This is part of the set of six Virtual Function Base Address Registers defined
by the SR-IOV Specifications. These registers are used to define address ranges for memory
accesses to the Endpoint device. This register may be used to define a range of 32-bit addresses,
or paired with the next adjacent register to define a 64-bit address range.
During the initial configuration of the device, the configuration program determines the size of
the address range defined by the BAR by writing a pattern of all 1's into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned value.
A value of 0 is returned by the Controller if this BAR is not configured. Otherwise, the number of 1's returned
is based on the length of the BAR.
Offset = 234h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0234h + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_I_VF_BAR_5_REG is shown in Figure 12-1372 and described in Table 12-2682.
Return to the Summary Table.
This is part of the set of six Virtual Function Base Address Registers defined
by the SR-IOV Specifications. These registers are used to define address ranges for memory
accesses to the Endpoint device. This register may be used to define a range of 32-bit addresses.
During the initial configuration of the device, the configuration program determines the size of
the address range defined by the BAR by writing a pattern of all 1's into the BAR, reading back
from the BAR, and noting the position of the first 1 (the most significant) in the returned value.
A value of 0 is returned by the Controller if this BAR is not configured. Otherwise, the number of 1's returned
is based on the length of the BAR.
Offset = 238h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0238h + formula |
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 |
R7 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R7 | R | 0h | This field is reserved at power-on. This can be changed using BAR configuration regsiter in LM space. |
PCIE_CORE_PFn_I_VF_MIGRATION_STATE_ARR_OFFSET_REG is shown in Figure 12-1373 and described in Table 12-2684.
Return to the Summary Table.
Not implemented
Offset = 23Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 023Ch |
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 |
MSAOR | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | MSAOR | R | 0h | N/A |
PCIE_CORE_PFn_RSVD_090_09C is shown in Figure 12-1374 and described in Table 12-2686.
Return to the Summary Table.
Reserved
Offset = 240h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0240h + formula |
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 |
RSVD | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | RSVD | R | 0h | Reserved |
PCIE_CORE_PF0_I_SEC_PCIE_CAP_HDR_REG is shown in Figure 12-1375 and described in Table 12-2688.
Return to the Summary Table.
This register contains the PCI Express Extended Capability ID for the Secondary PCI
Express Extended Capability, its capability version, and the pointer to the next capability
structure. This register is implemented only in the configuration space of PF 0.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0300h |
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 |
NCO | CV | PECI | |||||||||||||||||||||||||||||
R/W-400h | R/W-1h | R-19h | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 400h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified independently for each PF from the local management bus. |
15-0 | PECI | R | 19h | This field is hardwired to the Capability ID assigned by PCI SIG to the Secondary PCI Express Capability |
PCIE_CORE_PF0_I_LINK_CONTROL3_REG is shown in Figure 12-1376 and described in Table 12-2690.
Return to the Summary Table.
Link Control3 Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0304h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R2 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R2 | ELSOSGV | R1 | |||||||||||||
R-0h | R/W-0h | R-0h | |||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-13 | R2 | R | 0h | Reserved |
12-9 | ELSOSGV | R/W | 0h | When the Link is in L0 and the bit in this field corresponding to the current Link speed is Set, SKP Ordered Sets are scheduled at the rate defined for SRNS, overriding the rate required based on the clock tolerance architecture. |
8-0 | R1 | R | 0h | Reserved |
PCIE_CORE_PF0_I_LANE_ERROR_STATUS_REG is shown in Figure 12-1377 and described in Table 12-2692.
Return to the Summary Table.
This register contains one bit per lane indicating the physical-layer error status of
the corresponding lane. A 1 indicates that a physical-layer error was detected by the Controller in
the corresponding lane. The error can be cleared by writing a 1 into the bit position, either
through a Configuration Write transaction from the link or from the local management bus.
The following errors are reported in this status bit:
(i) Parity error detected in Gen3 SKP OS,
(ii)Loss of Block Alignment in the lane.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0308h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | LES | ||||||||||||||
R-0h | R/W1C-0h | ||||||||||||||
LEGEND: R = Read Only; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-4 | R0 | R | 0h | N/A |
3-0 | LES | R/W1C | 0h | Each of these bits indicates the error status for the corresponding lane. STICKY. |
PCIE_CORE_PF0_I_LANE_EQUALIZATION_CONTROL_REG0 is shown in Figure 12-1378 and described in Table 12-2694.
Return to the Summary Table.
This register contains the 8.0GT/s Transmitter Preset and the Receiver Preset Hint values for
lanes 0 and 1, received from the Upstream Device during the Link Equalization procedure.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 030Ch |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R3 | UPRPH1 | UPTP1 | |||||
R-0h | R-7h | R-Fh | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R2_1 | R2 | ||||||
R-0h | R-0h | ||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R1 | UPRPH0 | UPTP0 | |||||
R-0h | R-7h | R-Fh | |||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0_1 | R0 | ||||||
R-0h | R-0h | ||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | R3 | R | 0h | Reserved |
30-28 | UPRPH1 | R | 7h | 8.0GT/s Lane 1 Receiver Preset Hint value received from the upstream device. |
27-24 | UPTP1 | R | Fh | 8.0GT/s Lane 1 Transmitter Preset value received from the upstream device. |
23 | R2_1 | R | 0h | Reserved |
22-16 | R2 | R | 0h | Reserved |
15 | R1 | R | 0h | Reserved |
14-12 | UPRPH0 | R | 7h | 8.0GT/s Lane 0 Receiver Preset Hint value received from the upstream device. |
11-8 | UPTP0 | R | Fh | 8.0GT/s Lane 0 Transmitter Preset value received from the upstream device. |
7 | R0_1 | R | 0h | Reserved |
6-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PF0_I_LANE_EQUALIZATION_CONTROL_REG1 is shown in Figure 12-1551 and described in Table 12-3044.
Return to the Summary Table.
This register contains the 8.0GT/s Transmitter Preset and the Receiver Preset Hint values for lanes 2 and 3, for use during the Link Equalization procedure.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0310h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R3 | UPRPH1 | UPTP1 | |||||
R-0h | R-7h | R-Fh | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R2_1 | DNRPH1 | DNTP1 | |||||
R-0h | R-7h | R-Fh | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R1 | UPRPH0 | UPTP0 | |||||
R-0h | R-7h | R-Fh | |||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0_1 | DNRPH0 | DNTP0 | |||||
R-0h | R-7h | R-Fh | |||||
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | R3 | R | 0h | Reserved |
30-28 | UPRPH1 | R | 7h | 8.0GT/s Value sent by the Controller as the Receiver Preset Hint for the remote receiver associated with Lane 3. The remote node may use this value to adapt its receiver at the start of the link equalization procedure. |
27-24 | UPTP1 | R | Fh | 8.0GT/s Value sent by the Controller as the Transmitter Preset for the remote transmitter associated with Lane 3. The remote node uses this value to set up its transmitter at the start of the link equalization procedure. |
23 | R2_1 | R | 0h | Reserved |
22-20 | DNRPH1 | R | 7h | 8.0GT/s Receiver Preset Hint value to be used for the local receiver associated with Lane 3. The Controller uses this value to set up the receiver attached to Lane 3 |
19-16 | DNTP1 | R | Fh | 8.0GT/s Transmitter Preset value to be used for the local transmitter associated with Lane 3. The Controller uses this value to set up the Lane 3 transmitter during link equalization. |
15 | R1 | R | 0h | Reserved |
14-12 | UPRPH0 | R | 7h | 8.0GT/s Value sent by the Controller as the Receiver Preset Hint for the remote receiver associated with Lane 2. The remote node may use this value to adapt its receiver at the start of the link equalization procedure. |
11-8 | UPTP0 | R | Fh | 8.0GT/s Value sent by the Controller as the Transmitter Preset for the remote transmitter associated with Lane 2. The remote node uses this value to set up its transmitter at the start of the link equalization procedure. |
7 | R0_1 | R | 0h | Reserved |
6-4 | DNRPH0 | R | 7h | 8.0GT/s Receiver Preset Hint value to be used for the local receiver associated with Lane 2. The Controller uses this value to set up the receiver attached to Lane 2 |
3-0 | DNTP0 | R | Fh | 8.0GT/s Transmitter Preset value to be used for the local transmitter associated with Lane 2. The Controller uses this value to set up the Lane 2 transmitter during link equalization. |
PCIE_CORE_PFn_I_VSEC_HEADER_REG is shown in Figure 12-1380 and described in Table 12-2698.
Return to the Summary Table.
The Vendor-Specific Capability allows device vendors to use the Capability mechanism for vendor specific information.
Offset = 400h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0400h + formula |
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 |
NCO | CV | PECI | |||||||||||||||||||||||||||||
R/W-440h | R/W-1h | R/W-Bh | |||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 440h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified independently for each PF from the local management bus. |
15-0 | PECI | R/W | Bh | This field is hardwired to the Capability ID assigned by PCI SIG to the Vendor-Specific Extended Capability. |
PCIE_CORE_PFn_I_VENDOR_SPECIFIC_HEADER_REG is shown in Figure 12-1381 and described in Table 12-2700.
Return to the Summary Table.
Vendor-Specific Header Register.
Offset = 404h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0404h + formula |
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 |
VL | VR | VI | |||||||||||||||||||||||||||||
R/W-10h | R/W-1h | R/W-1h | |||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | VL | R/W | 10h | Total byte count [in hex format] of the VSEC structure, including the Vendor-Specific Capability Header, the Vendor-Specific Header and the Vendor-Specific registers. This field can be written from the local management bus independently or each PF. |
19-16 | VR | R/W | 1h | Vendor-defined version number for the VSEC structure. This field can be written from the local management bus independently or each PF. |
15-0 | VI | R/W | 1h | This field contains a vendor defined ID number that indicates the nature and format of the information in the Vendor-Specific Capability Structure. This field can be written from the local management bus independently or each PF. |
PCIE_CORE_PFn_I_VENDOR_SPECIFIC_CONTROL_REG is shown in Figure 12-1382 and described in Table 12-2702.
Return to the Summary Table.
This contains the first 4 Bytes of Vendor-Specific Register space. In the current
implementation, the first 4 Bytes of Vendor Specific Registers is called as Vendor Specific Control Register and is described in the fields below.
Offset = 408h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0408h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
VSEC_COUT | |||||||||||||||
R/W-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
VSEC_COUT | HTI | VSEC_CIN | |||||||||||||
R/W-0h | R/W-0h | R-0h | |||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-9 | VSEC_COUT | R/W | 0h | The state of these bits drive the output pins Fx_VSEC_CONTROL_OUT [ where x is the function number]. These are implemented as register bits that can be read and written by the host through a Config transaction, or via the local management interface. |
8 | HTI | R/W | 0h | The state of this bit drives the output pins Fx_VSEC_INTERRUPT_OUT [ where x is the function number]. It can be used by the host to signal a software-driven interrupt to the application logic outside the Controller. This bit may be read and written by the host through a Config transaction, or via the local management interface. |
7-0 | VSEC_CIN | R | 0h | The 8-bit value read from this field of PFx reflects the setting of Fx_VSEC_CONTROL_IN [7:0] input to the Controller. This field can also be read from the local management bus |
PCIE_CORE_PFn_I_VENDOR_SPECIFIC_DATA_REG0 is shown in Figure 12-1383 and described in Table 12-2704.
Return to the Summary Table.
This contains the Bytes 4, 5, 6, 7 of Vendor-Specific Register space. In the current
implementation, the these 4 Bytes of Vendor Specific Registers are called as Vendor Specific Data Register 0 and is described below.
Offset = 40Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 040Ch + formula |
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 |
GPD | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | GPD | R/W | 0h | These bits are implemented as register bits that can be read and written by the host through a Config transaction, or via the local management interface. Their use is application-dependent. |
PCIE_CORE_PFn_I_PASID_HEADER_REG is shown in Figure 12-1384 and described in Table 12-2706.
Return to the Summary Table.
The presence of a PASID Extended Capability indicates that the Endpoint supports sending and
receiving TLPs containing a PASID TLP Prefix.
Offset = 440h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0440h + formula |
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 |
NCO | CV | PECI | |||||||||||||||||||||||||||||
R/W-4C0h | R/W-1h | R-1Bh | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 4C0h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified independently for each PF from the local management bus. |
15-0 | PECI | R | 1Bh | This field is hardwired to the Capability ID assigned by PCI SIG to the PASID Capability. |
PCIE_CORE_PFn_I_PASID_CAP_REG is shown in Figure 12-1385 and described in Table 12-2708.
Return to the Summary Table.
PASID Capability Header fields are described below:
Offset = 444h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0444h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R31 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R31 | PRME | EXPE | PASE | ||||
R-0h | R/W-0h | R/W-0h | R/W-0h | ||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R15 | MPSW | ||||||
R-0h | R/W-14h | ||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RSVD2 | PRMS | EXPS | RSVD1 | ||||
R-0h | R/W-1h | R/W-1h | R-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-19 | R31 | R | 0h | Reserved |
18 | PRME | R/W | 0h | If set, the Endpoint is permitted to send requests that have the Privileged Mode Requested bit set. If clear, the Endpoint is not permitted to do so. |
17 | EXPE | R/W | 0h | If set, the Endpoint is permitted to send requests that have the Execute Requested bit set. If clear, the Endpoint is not permitted to do so. |
16 | PASE | R/W | 0h | If set, the Endpoint is permitted to send and receive TLPs that contain a PASID TLP Prefix. If clear, the Endpoint is not permitted to do so. |
15-13 | R15 | R | 0h | Reserved |
12-8 | MPSW | R/W | 14h | Indicates the width of the PASID field supported by the Endpoint. The value indicates support for PASID values 0 through 2n-1 [inclusive]. The value 0 indicates support for a single PASID [0]. The value 20 indicates support for all PASID values [20 bits]. This field must be between 0 and 20 [inclusive]. |
7-3 | RSVD2 | R | 0h | These bits are currently reserved. These are implemented as register bits that can be read and written by the host through a Config transaction, or via the local management interface. |
2 | PRMS | R/W | 1h | If set, the Endpoint supports operating in Privileged and Non-Privileged modes, and supports sending requests that have the Privileged Mode Requested bit set. If clear, the Endpoint should never set the Privileged Mode Requested bit. |
1 | EXPS | R/W | 1h | If set, the Endpoint supports sending memory requests that have the Execute Requested bit set. If clear, the Endpoint should never set the Execute Requested bit. |
0 | RSVD1 | R | 0h | These bits are currently reserved. These are implemented as register bits that can be read and written by the host through a Config transaction, or via the local management interface. |
PCIE_CORE_PF0_I_VC_ENH_CAP_HEADER_REG is shown in Figure 12-1386 and described in Table 12-2710.
Return to the Summary Table.
This is the first register in the Virtual Channel Capability Structure. The VC Capability is present only in
the configuration space of Physical Function 0. This register contains the PCI Express Extended
Capability ID, the capability version, and the pointer to the next capability structure.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04C0h |
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 |
NCO | CV | PECID | |||||||||||||||||||||||||||||
R/W-5C0h | R/W-1h | R-2h | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 5C0h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified independently for each PF from the local management bus. |
15-0 | PECID | R | 2h | This field is hardwired to the Capability ID assigned by PCI SIG to the VC Capability. |
PCIE_CORE_PF0_I_PORT_VC_CAP_REG_1 is shown in Figure 12-1387 and described in Table 12-2712.
Return to the Summary Table.
This register has fields that describe the capabilities of the device with respect to the virtual channels.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04C4h |
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 |
R0 | EVC | ||||||||||||||||||||||||||||||
R-0h | R-3h | ||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-3 | R0 | R | 0h | N/A |
2-0 | EVC | R | 3h | Indicates the number of Virtual Channels in addition to the default VC supported by the device. This field is valid for all functions. |
PCIE_CORE_PF0_I_PORT_VC_CAP_REG_2 is shown in Figure 12-1388 and described in Table 12-2714.
Return to the Summary Table.
This register has fields that describe the capabilities of the device with respect to the virtual channels.
This register is not implemented. A read from this location returns all zeroes.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04C8h |
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 |
R1 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R1 | R | 0h | N/A |
PCIE_CORE_PF0_I_PORT_VC_CTRL_STS_REG is shown in Figure 12-1389 and described in Table 12-2716.
Return to the Summary Table.
This location contains the 16-bit VC Control Register and the 16-bit VC Status Register. These registers
are not implemented. A read from this location returns all zeroes.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04CCh |
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 |
R2 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R2 | R | 0h | N/A |
PCIE_CORE_PF0_I_VC_RES_CAP_REG_0 is shown in Figure 12-1390 and described in Table 12-2718.
Return to the Summary Table.
This register describes the capabilities associated with VC 0. This register is not implemented. A read
from this location returns all zeroes.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04D0h |
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 |
R3 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R3 | R | 0h | N/A |
PCIE_CORE_PF0_I_VC_RES_CTRL_REG_0 is shown in Figure 12-1391 and described in Table 12-2720.
Return to the Summary Table.
This register contains bits to configure VC 0.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04D4h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
VCEN | R6 | VCI | |||||
R-1h | R-0h | R-0h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R5 | PARS | LPAT | |||||
R-0h | R-0h | R-0h | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R4 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
TVM | TVM0 | ||||||
R/W-7Fh | R-1h | ||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | VCEN | R | 1h | Software uses this bit to enable the VC. For VC0 this bit is hardwired to 1. |
30-27 | R6 | R | 0h | N/A |
26-24 | VCI | R | 0h | VC ID assigned to VC0. For the VC0, this field is read-only and it is hardwired to 00b. For non VC0 case, it is allowed to use any VC-ID. This VC-ID has to be unique across all VCs. This must not be same as VC0's ID[VC0 ID=0]. |
23-20 | R5 | R | 0h | N/A |
19-17 | PARS | R | 0h | Configures the VC to use a specific port arbitration scheme. This field is not implemented, and hardwired to 0. |
16 | LPAT | R | 0h | Updates the port arbitration logic from the Port Arbitration Table for VC 0. This bit is not implemented, and hardwired to 0. |
15-8 | R4 | R | 0h | N/A |
7-1 | TVM | R/W | 7Fh | Indicates the TCs that are mapped to this VC. When bit 0 of this field is set, it indicates that TC 0 is mapped to VC 0.By default, all TCs are mapped to VC 0. |
0 | TVM0 | R | 1h | Indicates the TC0 always mapped to VC0. |
PCIE_CORE_PF0_I_VC_RES_STS_REG_0 is shown in Figure 12-1392 and described in Table 12-2722.
Return to the Summary Table.
This register contains status bits associated with VC 0.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04D8h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R7 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R7 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R7 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R7 | VCNP | PATS | |||||
R-0h | R-0h | R-0h | |||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-2 | R7 | R | 0h | N/A |
1 | VCNP | R | 0h | This indicates whether the Virtual Channel negotiation is in pending state. The value of this bit is defined only when the link is in the DL_Active state and Virtual Channel is enabled. When this bit is set by hardware, it indicates that the VC resource has not completed the process of negotiation. This bit is cleared by hardware after the VC negotiation is complete. |
0 | PATS | R | 0h | This is not implemented and hardwired to 0. |
PCIE_CORE_PF0_I_VC_RES_CAP_REG_1 is shown in Figure 12-1393 and described in Table 12-2724.
Return to the Summary Table.
This register describes the capabilities associated with VC 1. This register is not implemented. A read
from this location returns all zeroes.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04DCh |
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 |
R3 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R3 | R | 0h | N/A |
PCIE_CORE_PF0_I_VC_RES_CTRL_REG_1 is shown in Figure 12-1394 and described in Table 12-2726.
Return to the Summary Table.
This register contains bits to configure VC 1.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04E0h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
VCEN | R6 | VCI | |||||
R/W-0h | R-0h | R/W-1h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R5 | PARS | LPAT | |||||
R-0h | R-0h | R-0h | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R4 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
TVM | TVM0 | ||||||
R/W-0h | R-0h | ||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | VCEN | R/W | 0h | Software uses this bit to enable the VC. For VC0 this bit is hardwired to 1. |
30-27 | R6 | R | 0h | N/A |
26-24 | VCI | R/W | 1h | VC ID assigned to VC1. For the VC0, this field is read-only and it is hardwired to 00b. For non VC0 case, it is allowed to use any VC-ID. This VC-ID has to be unique across all VCs. This must not be same as VC0's ID[VC0 ID=0]. |
23-20 | R5 | R | 0h | N/A |
19-17 | PARS | R | 0h | Configures the VC to use a specific port arbitration scheme. This field is not implemented, and hardwired to 0. |
16 | LPAT | R | 0h | Updates the port arbitration logic from the Port Arbitration Table for VC 1. This bit is not implemented, and hardwired to 0. |
15-8 | R4 | R | 0h | N/A |
7-1 | TVM | R/W | 0h | Indicates the TCs that are mapped to this VC. When bit 1 of this field is set, it indicates that TC 1 is mapped to VC 1.By default, all TCs are mapped to VC 0. |
0 | TVM0 | R | 0h | Indicates the TC0 always mapped to VC0. |
PCIE_CORE_PF0_I_VC_RES_STS_REG_1 is shown in Figure 12-1395 and described in Table 12-2728.
Return to the Summary Table.
This register contains status bits associated with VC 1.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04E4h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R7 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R7 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R7 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R7 | VCNP | PATS | |||||
R-0h | R-0h | R-0h | |||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-2 | R7 | R | 0h | N/A |
1 | VCNP | R | 0h | This indicates whether the Virtual Channel negotiation is in pending state. The value of this bit is defined only when the link is in the DL_Active state and Virtual Channel is enabled. When this bit is set by hardware, it indicates that the VC resource has not completed the process of negotiation. This bit is cleared by hardware after the VC negotiation is complete. |
0 | PATS | R | 0h | This is not implemented and hardwired to 0. |
PCIE_CORE_PF0_I_VC_RES_CAP_REG_2 is shown in Figure 12-1396 and described in Table 12-2730.
Return to the Summary Table.
This register describes the capabilities associated with VC 2. This register is not implemented. A read
from this location returns all zeroes.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04E8h |
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 |
R3 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R3 | R | 0h | N/A |
PCIE_CORE_PF0_I_VC_RES_CTRL_REG_2 is shown in Figure 12-1397 and described in Table 12-2732.
Return to the Summary Table.
This register contains bits to configure VC 2.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04ECh |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
VCEN | R6 | VCI | |||||
R/W-0h | R-0h | R/W-2h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R5 | PARS | LPAT | |||||
R-0h | R-0h | R-0h | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R4 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
TVM | TVM0 | ||||||
R/W-0h | R-0h | ||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | VCEN | R/W | 0h | Software uses this bit to enable the VC. For VC0 this bit is hardwired to 1. |
30-27 | R6 | R | 0h | N/A |
26-24 | VCI | R/W | 2h | VC ID assigned to VC2. For the VC0, this field is read-only and it is hardwired to 00b. For non VC0 case, it is allowed to use any VC-ID. This VC-ID has to be unique across all VCs. This must not be same as VC0's ID[VC0 ID=0]. |
23-20 | R5 | R | 0h | N/A |
19-17 | PARS | R | 0h | Configures the VC to use a specific port arbitration scheme. This field is not implemented, and hardwired to 0. |
16 | LPAT | R | 0h | Updates the port arbitration logic from the Port Arbitration Table for VC 2. This bit is not implemented, and hardwired to 0. |
15-8 | R4 | R | 0h | N/A |
7-1 | TVM | R/W | 0h | Indicates the TCs that are mapped to this VC. When bit 2 of this field is set, it indicates that TC 2 is mapped to VC 2.By default, all TCs are mapped to VC 0. |
0 | TVM0 | R | 0h | Indicates the TC0 always mapped to VC0. |
PCIE_CORE_PF0_I_VC_RES_STS_REG_2 is shown in Figure 12-1398 and described in Table 12-2734.
Return to the Summary Table.
This register contains status bits associated with VC 2.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04F0h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R7 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R7 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R7 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R7 | VCNP | PATS | |||||
R-0h | R-0h | R-0h | |||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-2 | R7 | R | 0h | N/A |
1 | VCNP | R | 0h | This indicates whether the Virtual Channel negotiation is in pending state. The value of this bit is defined only when the link is in the DL_Active state and Virtual Channel is enabled. When this bit is set by hardware, it indicates that the VC resource has not completed the process of negotiation. This bit is cleared by hardware after the VC negotiation is complete. |
0 | PATS | R | 0h | This is not implemented and hardwired to 0. |
PCIE_CORE_PF0_I_VC_RES_CAP_REG_3 is shown in Figure 12-1399 and described in Table 12-2736.
Return to the Summary Table.
This register describes the capabilities associated with VC 3. This register is not implemented. A read
from this location returns all zeroes.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04F4h |
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 |
R3 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R3 | R | 0h | N/A |
PCIE_CORE_PF0_I_VC_RES_CTRL_REG_3 is shown in Figure 12-1400 and described in Table 12-2738.
Return to the Summary Table.
This register contains bits to configure VC 3.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04F8h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
VCEN | R6 | VCI | |||||
R/W-0h | R-0h | R/W-3h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R5 | PARS | LPAT | |||||
R-0h | R-0h | R-0h | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R4 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
TVM | TVM0 | ||||||
R/W-0h | R-0h | ||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | VCEN | R/W | 0h | Software uses this bit to enable the VC. For VC0 this bit is hardwired to 1. |
30-27 | R6 | R | 0h | N/A |
26-24 | VCI | R/W | 3h | VC ID assigned to VC3. For the VC0, this field is read-only and it is hardwired to 00b. For non VC0 case, it is allowed to use any VC-ID. This VC-ID has to be unique across all VCs. This must not be same as VC0's ID[VC0 ID=0]. |
23-20 | R5 | R | 0h | N/A |
19-17 | PARS | R | 0h | Configures the VC to use a specific port arbitration scheme. This field is not implemented, and hardwired to 0. |
16 | LPAT | R | 0h | Updates the port arbitration logic from the Port Arbitration Table for VC 3. This bit is not implemented, and hardwired to 0. |
15-8 | R4 | R | 0h | N/A |
7-1 | TVM | R/W | 0h | Indicates the TCs that are mapped to this VC. When bit 3 of this field is set, it indicates that TC 3 is mapped to VC 3.By default, all TCs are mapped to VC 0. |
0 | TVM0 | R | 0h | Indicates the TC0 always mapped to VC0. |
PCIE_CORE_PF0_I_VC_RES_STS_REG_3 is shown in Figure 12-1401 and described in Table 12-2740.
Return to the Summary Table.
This register contains status bits associated with VC 3.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 04FCh |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R7 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R7 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R7 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R7 | VCNP | PATS | |||||
R-0h | R-0h | R-0h | |||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-2 | R7 | R | 0h | N/A |
1 | VCNP | R | 0h | This indicates whether the Virtual Channel negotiation is in pending state. The value of this bit is defined only when the link is in the DL_Active state and Virtual Channel is enabled. When this bit is set by hardware, it indicates that the VC resource has not completed the process of negotiation. This bit is cleared by hardware after the VC negotiation is complete. |
0 | PATS | R | 0h | This is not implemented and hardwired to 0. |
PCIE_CORE_PFn_ATS_CAP_HEADER is shown in Figure 12-1402 and described in Table 12-2742.
Return to the Summary Table.
This location contains the ATS Extended Capabilities Register, its Capability ID, Version,
and a pointer to the next capability.
Offset = 5C0h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 05C0h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
ATSNXTCAP | ATSCAPVER | ||||||||||||||
R/W-640h | R/W-1h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ATSCAPID | |||||||||||||||
R-Fh | |||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | ATSNXTCAP | R/W | 640h | Indicates offset to the next PCI Express capability structure. |
19-16 | ATSCAPVER | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. |
15-0 | ATSCAPID | R | Fh | Indicates the ATS Extended Capability structure. This field must return a Capability ID of 000Fh indicating that this is an ATS Extended Capability structure. |
PCIE_CORE_PFn_ATS_CAP_CONTROL is shown in Figure 12-1403 and described in Table 12-2744.
Return to the Summary Table.
ATS Capability and Control Register
Offset = 5C4h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 05C4h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
ATSEN | R30 | ||||||
R/W-0h | R-0h | ||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R30 | ATSSTU | ||||||
R-0h | R/W-0h | ||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R15 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R15 | ATSGIS | ATSPGALNREQ | ATSINVQD | ||||
R-0h | R/W-1h | R/W-1h | R/W-1h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | ATSEN | R/W | 0h | When Set, the Function is enabled to cache translations. Default value is 0b. |
30-21 | R30 | R | 0h | Reserved |
20-16 | ATSSTU | R/W | 0h | This value indicates to the Function the minimum number of 4096-byte blocks that is indicated in a Translation Completions or Invalidate Requests. This is a power of 2 multiplier and the number of blocks is 2STU. A value of 0 0000b indicates one block and a value of 1 1111b indicates 231 blocks. |
15-7 | R15 | R | 0h | Reserved |
6 | ATSGIS | R/W | 1h | If Set, the Function supports InvalidationRequests that have the Global Invalidate bit Set. If Clear, the Function ignores the Global Invalidate bit in all Invalidate Requests. |
5 | ATSPGALNREQ | R/W | 1h | If Set, indicates the Untranslated Address is always aligned to a 4096 byte boundary. Controller supports only page aligned request. It always masks the bits and makes it aligned to 4096 for ATS requests. |
4-0 | ATSINVQD | R/W | 1h | The number of Invalidate Requests that the Function can accept before putting backpressure on the upstream connection. If 0 0000b, the Function can accept 32 Invalidate Requests. |
PCIE_CORE_PFn_ATS_PR_CAP_HEADER is shown in Figure 12-1404 and described in Table 12-2746.
Return to the Summary Table.
Page Request Extended Capability Structure is used to configure the Page Request Interface mechanism.
Offset = 640h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0640h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
ATSPRNXCAP | ATSPRCAPVER | ||||||||||||||
R/W-900h | R/W-1h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ATSPRCAPID | |||||||||||||||
R-13h | |||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | ATSPRNXCAP | R/W | 900h | The offset to the next PCI Extended Capability structure. |
19-16 | ATSPRCAPVER | R/W | 1h | This field is a PCI-SIG defined version number that indicates the version of the Capability structure present. |
15-0 | ATSPRCAPID | R | 13h | Indicates that the associated extended capability structure is a Page Request Extended Capability. This field must return a Capability ID of 0013h. |
PCIE_CORE_PFn_ATS_PR_CONTROL_STATUS is shown in Figure 12-1405 and described in Table 12-2748.
Return to the Summary Table.
ATS Page Request Control Status Register.
Offset = 644h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0644h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
ATSPRGRPR | RESERVED | ATSPRSTOP | |||||
R/W-1h | R/W-X | R/W-1h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | ATSPPRUPRGI | ATS_PR_RF | |||||
R/W-X | R/W-0h | R/W-0h | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R/W-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | ATSPRRST | ATSPREN | |||||
R/W-X | R/W-0h | R/W-0h | |||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | ATSPRGRPR | R/W | 1h | If Set, the Function expects a PASID TLP Prefix on PRG Response Messages when the corresponding Page Requests had a PASID TLP Prefix. If Clear, the Function does not expect PASID TLP Prefixes on any PRG Response Message. Function behavior is undefined if this bit is Clear and the Function receives a PRG Response Message with a PASID TLP Prefix. Function behavior is undefined if this bit is Set and the Function receives a PRG Response Message with no PASID TLP Prefix when the corresponding Page Requests had a PASID TLP Prefix |
30-25 | RESERVED | R/W | X | |
24 | ATSPRSTOP | R/W | 1h | When this field is Set, the associated page request interface has stopped issuing additional page requests and that all previously issued Page Requests have completed. When this field is Clear the associated page request interface either has not stopped or has stopped issuing new Page Requests but has outstanding Page Requests. This field is only meaningful if Enable is Clear. If Enable is Set, this field is undefined. When the Enable field is Cleared, after having been previously Set, the interface transitions to the stopping state and Clears this field. After all page requests currently outstanding at the Function[s] have completed, this field is Set and the interface enters the disabled state. If there were no outstanding page requests, this field may be Set immediately when Enable is Cleared. Resetting the interface will cause an immediate transition to the disabled state. While in the stopping state, receipt of a Response Failure message will result in the immediate transition to the disabled state [Setting this field]. For SR-IOV, this field is Set only when all associated Functions [PF and VFs] have stopped issuing page requests. Default value is 1b. |
23-18 | RESERVED | R/W | X | |
17 | ATSPPRUPRGI | R/W | 0h | This field, when Set, indicates that the Function has received a PRG Response Message containing a PRG index that has no matching request. This field is Set by the Function and cleared when a one is written to the field. For SR-IOV, this field is Set in the PF if any associated Function [PF or VF] receives a PRG Response Message that does has no matching request. Default value is 0b. |
16 | ATS_PR_RF | R/W | 0h | This field, when Set, indicates that the Function has received a PRG Response Message indicating a Response Failure. The Function expects no further responses from the host [any received are ignored]. This field is Set by the Function and Cleared when a one is written to the field. For SR-IOV, this field is Set in the PF if any associated Function [PF or VF] receives a PRG Response Message indicating Response Failure. Default value is 0b. |
15-2 | RESERVED | R/W | X | |
1 | ATSPRRST | R/W | 0h | When the Enable field is clear, or is being cleared in the same register update that sets this field, writing a 1b to this field, clears the associated implementation dependent page request credit counter and pending request state for the associated Page Request Interface. No action is initiated if this field is written to 0b or if this field is written with any value while the Enable field is Set. Reads of this field through PCIe link return 0b. Once this field is written by '1' through pcie link, a vector output[ATS_PR_CONTROL_REG_RESET] of controller gets set. client logic after clearing the credit counter and pending request state, has to clear this register through local management interface. |
0 | ATSPREN | R/W | 0h | This field, when set, indicates that the Page Request Interface is allowed to make page requests. If this field is Clear, the Page Request Interface is not allowed to issue page requests. If both this field and the Stopped field are Clear, then the Page Request Interface will not issue new page requests, but has outstanding page requests that have been transmitted or are queued for transmission. When the Page Request Interface is transitioned from not-Enabled to Enabled, its status flags [Stopped, Response Failure, and Unexpected Response flags] are cleared. Enabling a Page Request Interface that has not successfully Stopped has indeterminate results. Default value is 0b. |
PCIE_CORE_PFn_ATS_OUTSTANDING_PR_CAPACITY is shown in Figure 12-1406 and described in Table 12-2750.
Return to the Summary Table.
This register contains the number of outstanding page request messages the associated Page Request
Interface physically supports. This is the upper limit on the number of pages that can be usefully
allocated to the Page Request Interface.
Offset = 648h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0648h + formula |
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 |
ATSOUTPRCAP | |||||||||||||||||||||||||||||||
R/W-1h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | ATSOUTPRCAP | R/W | 1h | This register contains the number of outstanding page request messages the associated Page Request Interface physically supports. This is the upper limit on the number of pages that can be usefully allocated to the Page Request Interface. |
PCIE_CORE_PFn_ATS_OUTSTANDING_PR_ALLOC is shown in Figure 12-1407 and described in Table 12-2752.
Return to the Summary Table.
This register contains the number of outstanding page request messages the associated Page Request
Interface is allowed to issue.
Offset = 64Ch + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 064Ch + formula |
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 |
ATSOUTPRALLOC | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | ATSOUTPRALLOC | R/W | 0h | This register contains the number of outstanding page request messages the associated Page Request Interface is allowed to issue |
PCIE_CORE_PF0_I_L1_PM_EXT_CAP_HDR is shown in Figure 12-1408 and described in Table 12-2754.
Return to the Summary Table.
L1 PM Substates Extended Capability Header Register.
For a multi-Function device associated with an Endpoint implementing L1 PM Substates, this Extended Capability Structure is implemented only in Function 0, and controls the Endpoint's Link behavior on behalf of all the Functions of the device.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0900h |
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 |
NCO | CV | PECID | |||||||||||||||||||||||||||||
R/W-910h | R/W-1h | R-1Eh | |||||||||||||||||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | NCO | R/W | 910h | Indicates offset to the next PCI Express capability structure. The default next pointer value is dynamic and is dependent on whether the strap or LMI bits are set. |
19-16 | CV | R/W | 1h | Specifies the SIG assigned value for the version of the capability structure. This field is set by default to 1, but can be modified from the local management bus. |
15-0 | PECID | R | 1Eh | This field is hardwired to the Capability ID assigned by PCI SIG to the L1 PM Substates Extended Capability Structure [001E hex]. |
PCIE_CORE_PF0_I_L1_PM_CAP is shown in Figure 12-1409 and described in Table 12-2756.
Return to the Summary Table.
This register advertises the L1 PM Substates Capabilities.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0904h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R/W-X | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | RESERVED | L1PRTPVRONSCALE | |||||
R/W-Dh | R/W-X | R/W-0h | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
L1PRTCMMDRESTRTIME | |||||||
R/W-FFh | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | L1PMSUPP | L1ASPML11SUPP | L1ASPML12SUPP | L1PML11SUPP | L1PML12SUPP | ||
R/W-X | R/W-1h | R/W-1h | R/W-1h | R/W-1h | R/W-1h | ||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | RESERVED | R/W | X | |
23-19 | R0 | R/W | Dh | Along with the Port T_POWER_ON Scale field in the L1 PM Substates Capabilities register sets the time [in us] that this Port requires the port on the opposite side of Link to wait in L1.2.Exit after sampling CLKREQ# asserted before actively driving the interface. The value of Port T_POWER_ON is calculated by multiplying the value in this field by the scale value in the Port T_POWER_ON Scale field in the L1 PM Substates Capabilities register. T Power On is the minimum amount of time that each component must wait in L1.2.Exit after sampling CLKREQ# asserted before actively driving the interface. This is to ensure no device is ever actively driving into an unpowered component.This bit can be modified using local management interface. |
18 | RESERVED | R/W | X | |
17-16 | L1PRTPVRONSCALE | R/W | 0h | Specifies the scale used for the Port T_POWER_ON Value field in the L1 PM Substates Capabilities register. Range of Values 00b = 2us 01b = 10us 10b = 100us 11b = Reserved Default value is 00.This bit can be modified using local management interface. |
15-8 | L1PRTCMMDRESTRTIME | R/W | FFh | Time [in us] required for this Port to re-establish common mode during exit from PM or ASPM L1.2 substate. This bit can be modified using local management interface. |
7-5 | RESERVED | R/W | X | |
4 | L1PMSUPP | R/W | 1h | When Set this bit indicates that this Port supports L1 PM Substates.This bit can be modified using local management interface. |
3 | L1ASPML11SUPP | R/W | 1h | When Set this bit indicates that ASPM L1.1 is supported.This bit can be modified using local management interface. |
2 | L1ASPML12SUPP | R/W | 1h | When Set this bit indicates that ASPM L1.2 is supported.This bit can be modified using local management interface. |
1 | L1PML11SUPP | R/W | 1h | When Set this bit indicates that PCI-PM L1.1 is supported.This bit can be modified using local management interface. |
0 | L1PML12SUPP | R/W | 1h | When Set this bit indicates that PCI-PM L1.2 is supported. This bit can be modified using local management interface. |
PCIE_CORE_PF0_I_L1_PM_CTRL_1 is shown in Figure 12-1410 and described in Table 12-2758.
Return to the Summary Table.
This register is used to Control ASPM, PCI PM L1 substates.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0908h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
L1THRSHLDSC | RESERVED | L1THRSHLDVAL | |||||
R/W-0h | R/W-X | R/W-0h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
L1THRSHLDVAL | |||||||
R/W-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
L1CMMDRESTRTIME | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | L1ASPML11EN | L1ASPML12EN | L1PML11EN | L1PML12EN | |||
R/W-X | R/W-0h | R/W-0h | R/W-0h | R/W-0h | |||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-29 | L1THRSHLDSC | R/W | 0h | This field provides a scale for the value contained within the LTR_L1.2_THRESHOLD_Value. 000 - Value times 1 ns 001 - Value times 32 ns 010 - Value times 1024 ns 011 - Value times 32,768 ns 100 - Value times 1,048,576 ns 101 - Value times 33,554,422ns 110- 111 - Not permitted |
28-26 | RESERVED | R/W | X | |
25-16 | L1THRSHLDVAL | R/W | 0h | Along with the LTR_L1.2_THRESHOLD_Scale, this field indicates the LTR threshold used to determine if entry into L1 results in L1.1 [if enabled] or L1.2 [if enabled]. |
15-8 | L1CMMDRESTRTIME | R | 0h | This field is reserved for EP. |
7-4 | RESERVED | R/W | X | |
3 | L1ASPML11EN | R/W | 0h | When Set this bit enables ASPM L1.1. |
2 | L1ASPML12EN | R/W | 0h | When Set this bit enables ASPM L1.2. |
1 | L1PML11EN | R/W | 0h | When Set this bit enables PCI-PM L1.1. |
0 | L1PML12EN | R/W | 0h | When Set this bit enables PCI-PM L1.2. |
PCIE_CORE_PF0_I_L1_PM_CTRL_2 is shown in Figure 12-1411 and described in Table 12-2760.
Return to the Summary Table.
L1 PM Substates Control 2 Register
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 090Ch |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R/W-X | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R/W-X | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R/W-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
L1PWRONVAL | RESERVED | L1PWRONSC | |||||
R/W-5h | R/W-X | R/W-0h | |||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-8 | RESERVED | R/W | X | |
7-3 | L1PWRONVAL | R/W | 5h | Along with the T_POWER_ON Scale sets the minimum amount of time [in us] that the Port must wait in L1.2.Exit after sampling CLKREQ# asserted before actively driving the interface. T_POWER_ON is calculated by multiplying the value in this field by the value in the T_POWER_ON Scale field. |
2 | RESERVED | R/W | X | |
1-0 | L1PWRONSC | R/W | 0h | Specifies the scale used for T_POWER_ON Value. Range of Values 00b = 2us 01b = 10us 10b = 100us 11b = Reserved |
PCIE_CORE_PFn_I_DL_FEATURE_EXTENDED_CAPABILITY_HEADER_REG is shown in Figure 12-1412 and described in Table 12-2762.
Return to the Summary Table.
Data Link Feature Extended Capability Structure is used to configure the DL Feature mechanism.
Offset = 910h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0910h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
DLFNXCAP | DLFCAPVER | ||||||||||||||
R/W-920h | R/W-1h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
DLFCAPID | |||||||||||||||
R-25h | |||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | DLFNXCAP | R/W | 920h | The offset to the next PCI Extended Capability structure. |
19-16 | DLFCAPVER | R/W | 1h | This field is a PCI-SIG defined version number that indicates the version of the Capability structure present. |
15-0 | DLFCAPID | R | 25h | Indicates that the associated extended capability structure is the DL Feature Extended Capability. This field returns a Capability ID of 0025h. |
PCIE_CORE_PFn_I_DL_FEATURE_CAPABILITIES_REG is shown in Figure 12-1413 and described in Table 12-2764.
Return to the Summary Table.
Data Link Feature Capabilities Register..
Offset = 914h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0914h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
DLFEXEN | R0 | ||||||
R/W-1h | R-0h | ||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R0 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | DLFCAPVER | ||||||
R-0h | R/W-1h | ||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | DLFEXEN | R/W | 1h | If Set, this bit indicates that this Port will enter the DL_Feature negotiation state prior to Link Initialization. |
30-1 | R0 | R | 0h | Reserved |
0 | DLFCAPVER | R/W | 1h | This bit indicates that this Port supports the Scaled Flow Control Feature. |
PCIE_CORE_PFn_I_DL_FEATURE_STATUS_REG is shown in Figure 12-1414 and described in Table 12-2766.
Return to the Summary Table.
Data Link Feature Status Register..
Offset = 918h + (n * 1000h); where n = 0h to 5h
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0918h + formula |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RDLFSVAL | R1 | ||||||
R-0h | R-0h | ||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R23 | R0 | ||||||
R-0h | R-0h | ||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R0 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | RSFSUP | ||||||
R-0h | R-0h | ||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | RDLFSVAL | R | 0h | This bit indicates that the Port has received a Data Link Feature DLLP in state DL_Feature [see Section 3.2.1] and that the Remote Data Link Feature Supported and Remote Data Link Feature Ack fields are meaningful. This bit is Cleared on entry to state DL_Inactive. Default is 0b. |
30-24 | R1 | R | 0h | Reserved |
23 | R23 | R | 0h | Reserved |
22-1 | R0 | R | 0h | Reserved |
0 | RSFSUP | R | 0h | This bit indicates that the Remote end Device supports the Scaled Flow Control Feature. |
PCIE_CORE_PF0_I_MARGINING_EXTENDED_CAPABILITY_HEADER_REG is shown in Figure 12-1415 and described in Table 12-2768.
Return to the Summary Table.
Margining Extended Capability Structure is used to configure the device for Receiver Margining.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0920h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
MARNXCAP | MARCAPVER | ||||||||||||||
R/W-9C0h | R/W-1h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
MARCAPID | |||||||||||||||
R-27h | |||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | MARNXCAP | R/W | 9C0h | The offset to the next PCI Extended Capability structure. |
19-16 | MARCAPVER | R/W | 1h | This field is a PCI-SIG defined version number that indicates the version of the Capability structure present. |
15-0 | MARCAPID | R | 27h | Indicates that the associated extended capability structure is the Margining Extended Capability. This field returns a Capability ID of 0027h. |
PCIE_CORE_PF0_I_MARGINING_PORT_CAPABILITIES_STATUS_REG is shown in Figure 12-1416 and described in Table 12-2770.
Return to the Summary Table.
Margining Port Capabilities and Status Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0924h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R1 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R1 | MSRDY | MRDY | |||||
R-0h | R/W-0h | R-0h | |||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R0 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | MARUDS | ||||||
R-0h | R/W-1h | ||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-18 | R1 | R | 0h | Reserved |
17 | MSRDY | R/W | 0h | When Margining uses Driver Software is Set, then this bit, when Set, indicates that the required software has performed the required initialization. The value of this bit is Undefined if Margining users Driver Software is Clear. The Controller implementation sets the default value of this bit to 0. The driver software must initialize the Rx Margining parameters in the Local Management Lane Margining Registers and then program this bit to 1. |
16 | MRDY | R | 0h | Indicates when the Margining feature is ready to accept margining commands. If the Margining uses Driver Software bit is 1, then the Controller sets this status bit when the Margining Software Ready bit is set and the Link is in Gen4 L0 state. If the Margining uses Driver Software bit is 0, then the Controller sets this status bit when the Link is in Gen4 L0 state. |
15-1 | R0 | R | 0h | Reserved |
0 | MARUDS | R/W | 1h | If Set, indicates that Margining is partially implemented using Device Driver software. Margining Software Ready indicates when this software is initialized. If Clear, Margining does not require device driver software. The Controller implementation requires driver software to initialize the Rx Margining parameter values in Local Management Registers for Lane Margining. Hence, the default value of this bit is set to 1. |
PCIE_CORE_PF0_I_MARGINING_LANE_CONTROL_STATUS_REG0 is shown in Figure 12-1417 and described in Table 12-2772.
Return to the Summary Table.
Margining Lane Control and Status Register for Lane 0.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0928h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
MPSTS | |||||||
R/W-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R1 | UMSTS | MTSTS | RNSTS | ||||
R-0h | R/W-0h | R/W-0h | R/W-0h | ||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
MRGPAY | |||||||
R/W-9Ch | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | USGMOD | MRGTYP | RCVNUM | ||||
R-0h | R/W-0h | R/W-7h | R/W-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | MPSTS | R/W | 0h | Margin Payload Status for Margining Commands. This field is reset upon DL Down. |
23 | R1 | R | 0h | Reserved |
22 | UMSTS | R/W | 0h | Usage Model Status for Margining Commands. This field is reset upon DL Down. |
21-19 | MTSTS | R/W | 0h | Margin Type Status for Margining Commands. This field is reset upon DL Down. |
18-16 | RNSTS | R/W | 0h | Receiver Number Status for Margining Commands. This field is reset upon DL Down. |
15-8 | MRGPAY | R/W | 9Ch | Margin Payload for Margining Commands. This field is reset upon DL Down. |
7 | R0 | R | 0h | Reserved |
6 | USGMOD | R/W | 0h | Usage Model for Margining Commands. This field is reset upon DL Down. |
5-3 | MRGTYP | R/W | 7h | Margin Type for Margining Commands. This field is reset upon DL Down. |
2-0 | RCVNUM | R/W | 0h | Receiver Number for Margining Commands. This field is reset upon DL Down. |
PCIE_CORE_PF0_I_MARGINING_LANE_CONTROL_STATUS_REG1 is shown in Figure 12-1418 and described in Table 12-2774.
Return to the Summary Table.
Margining Lane Control and Status Register for Lane 1.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 092Ch |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
MPSTS | |||||||
R/W-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R1 | UMSTS | MTSTS | RNSTS | ||||
R-0h | R/W-0h | R/W-0h | R/W-0h | ||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
MRGPAY | |||||||
R/W-9Ch | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | USGMOD | MRGTYP | RCVNUM | ||||
R-0h | R/W-0h | R/W-7h | R/W-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | MPSTS | R/W | 0h | Margin Payload Status for Margining Commands. This field is reset upon DL Down. |
23 | R1 | R | 0h | Reserved |
22 | UMSTS | R/W | 0h | Usage Model Status for Margining Commands. This field is reset upon DL Down. |
21-19 | MTSTS | R/W | 0h | Margin Type Status for Margining Commands. This field is reset upon DL Down. |
18-16 | RNSTS | R/W | 0h | Receiver Number Status for Margining Commands. This field is reset upon DL Down. |
15-8 | MRGPAY | R/W | 9Ch | Margin Payload for Margining Commands. This field is reset upon DL Down. |
7 | R0 | R | 0h | Reserved |
6 | USGMOD | R/W | 0h | Usage Model for Margining Commands. This field is reset upon DL Down. |
5-3 | MRGTYP | R/W | 7h | Margin Type for Margining Commands. This field is reset upon DL Down. |
2-0 | RCVNUM | R/W | 0h | Receiver Number for Margining Commands. This field is reset upon DL Down. |
PCIE_CORE_PF0_I_MARGINING_LANE_CONTROL_STATUS_REG2 is shown in Figure 12-1419 and described in Table 12-2776.
Return to the Summary Table.
Margining Lane Control and Status Register for Lane 2.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0930h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
MPSTS | |||||||
R/W-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R1 | UMSTS | MTSTS | RNSTS | ||||
R-0h | R/W-0h | R/W-0h | R/W-0h | ||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
MRGPAY | |||||||
R/W-9Ch | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | USGMOD | MRGTYP | RCVNUM | ||||
R-0h | R/W-0h | R/W-7h | R/W-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | MPSTS | R/W | 0h | Margin Payload Status for Margining Commands. This field is reset upon DL Down. |
23 | R1 | R | 0h | Reserved |
22 | UMSTS | R/W | 0h | Usage Model Status for Margining Commands. This field is reset upon DL Down. |
21-19 | MTSTS | R/W | 0h | Margin Type Status for Margining Commands. This field is reset upon DL Down. |
18-16 | RNSTS | R/W | 0h | Receiver Number Status for Margining Commands. This field is reset upon DL Down. |
15-8 | MRGPAY | R/W | 9Ch | Margin Payload for Margining Commands. This field is reset upon DL Down. |
7 | R0 | R | 0h | Reserved |
6 | USGMOD | R/W | 0h | Usage Model for Margining Commands. This field is reset upon DL Down. |
5-3 | MRGTYP | R/W | 7h | Margin Type for Margining Commands. This field is reset upon DL Down. |
2-0 | RCVNUM | R/W | 0h | Receiver Number for Margining Commands. This field is reset upon DL Down. |
PCIE_CORE_PF0_I_MARGINING_LANE_CONTROL_STATUS_REG3 is shown in Figure 12-1420 and described in Table 12-2778.
Return to the Summary Table.
Margining Lane Control and Status Register for Lane 3.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0934h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
MPSTS | |||||||
R/W-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R1 | UMSTS | MTSTS | RNSTS | ||||
R-0h | R/W-0h | R/W-0h | R/W-0h | ||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
MRGPAY | |||||||
R/W-9Ch | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | USGMOD | MRGTYP | RCVNUM | ||||
R-0h | R/W-0h | R/W-7h | R/W-0h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | MPSTS | R/W | 0h | Margin Payload Status for Margining Commands. This field is reset upon DL Down. |
23 | R1 | R | 0h | Reserved |
22 | UMSTS | R/W | 0h | Usage Model Status for Margining Commands. This field is reset upon DL Down. |
21-19 | MTSTS | R/W | 0h | Margin Type Status for Margining Commands. This field is reset upon DL Down. |
18-16 | RNSTS | R/W | 0h | Receiver Number Status for Margining Commands. This field is reset upon DL Down. |
15-8 | MRGPAY | R/W | 9Ch | Margin Payload for Margining Commands. This field is reset upon DL Down. |
7 | R0 | R | 0h | Reserved |
6 | USGMOD | R/W | 0h | Usage Model for Margining Commands. This field is reset upon DL Down. |
5-3 | MRGTYP | R/W | 7h | Margin Type for Margining Commands. This field is reset upon DL Down. |
2-0 | RCVNUM | R/W | 0h | Receiver Number for Margining Commands. This field is reset upon DL Down. |
PCIE_CORE_PF0_I_PL_16GTS_EXTENDED_CAPABILITY_HEADER_REG is shown in Figure 12-1421 and described in Table 12-2780.
Return to the Summary Table.
Physical Layer 16 GT/s Extended Capability Structure is used to configure the device for Gen4 Equalization and Gen4 Lane Error Reporting.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09C0h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
PL16NXCAP | PL16CAPVER | ||||||||||||||
R/W-A20h | R/W-1h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
PL16CAPID | |||||||||||||||
R-26h | |||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | PL16NXCAP | R/W | A20h | The offset to the next PCI Extended Capability structure. |
19-16 | PL16CAPVER | R/W | 1h | This field is a PCI-SIG defined version number that indicates the version of the Capability structure present. |
15-0 | PL16CAPID | R | 26h | Indicates that the associated extended capability structure is for Physical layer 16 GT/s. This field returns a Capability ID of 0026h. |
PCIE_CORE_PF0_I_PL_16GTS_CAPABILITIES_REG is shown in Figure 12-1422 and described in Table 12-2782.
Return to the Summary Table.
Physical Layer 16GTs Capabilities Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09C4h |
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 |
R0 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PF0_I_PL_16GTS_CONTROL_REG is shown in Figure 12-1423 and described in Table 12-2784.
Return to the Summary Table.
Physical Layer 16GTs Control Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09C8h |
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 |
R0 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PF0_I_PL_16GTS_STATUS_REG is shown in Figure 12-1424 and described in Table 12-2786.
Return to the Summary Table.
Physical Layer 16GTs Status Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09CCh |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R0 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R0 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | LE16 | EP3S16 | EP2S16 | EP1S16 | EQC16 | ||
R-0h | R/W-0h | R-0h | R-0h | R-0h | R-0h | ||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-5 | R0 | R | 0h | Reserved |
4 | LE16 | R/W | 0h | This bit is set by Controller hardware to request the 16.0 GT/s Link equalization process to be performed on the Link. Controller hardware sets this bit if a link equalization problem is detected at the end of equalization at 16GT/s. Additionally, the Client Firmware may set this bit while requesting equalization through Local Management EP 16GTs Request Equalization Retrain Link bit. This bit is cleared by writing a 1 to this bit position by the host, or writing a 0 from the LMI. STICKY. |
3 | EP3S16 | R | 0h | This bit, when set to 1, indicates that the Phase 3 of the Transmitter Equalization procedure has completed successfully for 16.0 GT/s. STICKY. |
2 | EP2S16 | R | 0h | This bit, when set to 1, indicates that the Phase 2 of the Transmitter Equalization procedure has completed successfully for 16.0 GT/s. STICKY. |
1 | EP1S16 | R | 0h | This bit, when set to 1, indicates that the Phase 1 of the Transmitter Equalization procedure has completed successfully for 16.0 GT/s. STICKY. |
0 | EQC16 | R | 0h | This bit, when set to 1, indicates that the Transmitter Equalization procedure has completed for 16.0 GT/s. STICKY. |
PCIE_CORE_PF0_I_PL_16GTS_LOCAL_DATA_PARITY_MISMATCH_STATUS_REG is shown in Figure 12-1425 and described in Table 12-2788.
Return to the Summary Table.
Physical Layer 16GTs Local Data Parity Mismatch Status Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09D0h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R0 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R0 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | LDPMS16 | ||||||
R-0h | R/W1C-0h | ||||||
LEGEND: R = Read Only; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-4 | R0 | R | 0h | N/A |
3-0 | LDPMS16 | R/W1C | 0h | Each bit indicates if the corresponding Lane detected a Data Paritymismatch. A value of 1b indicates that a mismatch was detected on the corresponding Lane Number. |
PCIE_CORE_PF0_I_PL_16GTS_FIRST_RETIMER_DATA_PARITY_MISMATCH_STATUS_REG is shown in Figure 12-1426 and described in Table 12-2790.
Return to the Summary Table.
Physical Layer 16GTs First Retimer Data Parity Mismatch Status Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09D4h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R0 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R0 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | FRDPMS16 | ||||||
R-0h | R/W1C-0h | ||||||
LEGEND: R = Read Only; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-4 | R0 | R | 0h | N/A |
3-0 | FRDPMS16 | R/W1C | 0h | Each bit indicates if the first retimer in the corresponding Lane detected a Data Parity mismatch. A value of 1b indicates that a mismatch was detected on the corresponding Lane Number. The value of this field is undefined when no Retimers are present. |
PCIE_CORE_PF0_I_PL_16GTS_SECOND_RETIMER_DATA_PARITY_MISMATCH_STATUS_REG is shown in Figure 12-1427 and described in Table 12-2792.
Return to the Summary Table.
Physical Layer 16GTs Second Retimer Data Parity Mismatch Status Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09D8h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R0 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R0 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
R0 | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R0 | SRDPMS16 | ||||||
R-0h | R/W1C-0h | ||||||
LEGEND: R = Read Only; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-4 | R0 | R | 0h | N/A |
3-0 | SRDPMS16 | R/W1C | 0h | Each bit indicates if the second retimer in the corresponding Lane detected a Data Parity mismatch. A value of 1b indicates that a mismatch was detected on the corresponding Lane Number. The value of this field is undefined when no Retimers are present. |
PCIE_CORE_PF0_I_PL_16GTS_RESERVED_REG is shown in Figure 12-1428 and described in Table 12-2794.
Return to the Summary Table.
Register at offset 1Ch in this capability is Reserved.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09DCh |
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 |
R0 | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | R0 | R | 0h | Reserved |
PCIE_CORE_PF0_I_PL_16GTS_LANE_EQUALIZATION_CONTROL_REG0 is shown in Figure 12-1429 and described in Table 12-2796.
Return to the Summary Table.
This register contains the Upstream Port 16.0GT/s Transmitter Preset for
lanes 0, 1, 2 and 3, received from the Downstream Port during the 16GT/s Link Equalization procedure.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 09E0h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
UPTP316 | DPTP316 | UPTP216 | DPTP216 | ||||||||||||
R-Fh | R-Fh | R-Fh | R-Fh | ||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
UPTP116 | DPTP116 | UPTP016 | DPTP016 | ||||||||||||
R-Fh | R-Fh | R-Fh | R-Fh | ||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-28 | UPTP316 | R | Fh | 16.0GT/s Lane 3 Transmitter Preset value that the Downstream Port sends on the associated Lane to the Endpoint device during 16GT/s Link Equalization. |
27-24 | DPTP316 | R | Fh | Transmitter Preset used for 16.0 GT/s equalization by this Port when the Port is operating as a Downstream Port. |
23-20 | UPTP216 | R | Fh | 16.0GT/s Lane 2 Transmitter Preset value that the Downstream Port sends on the associated Lane to the Endpoint device during 16GT/s Link Equalization. |
19-16 | DPTP216 | R | Fh | Transmitter Preset used for 16.0 GT/s equalization by this Port when the Port is operating as a Downstream Port. |
15-12 | UPTP116 | R | Fh | 16.0GT/s Lane 1 Transmitter Preset value that the Downstream Port sends on the associated Lane to the Endpoint device during 16GT/s Link Equalization. |
11-8 | DPTP116 | R | Fh | Transmitter Preset used for 16.0 GT/s equalization by this Port when the Port is operating as a Downstream Port. |
7-4 | UPTP016 | R | Fh | 16.0GT/s Lane 0 Transmitter Preset value that the Downstream Port sends on the associated Lane to the Endpoint device during 16GT/s Link Equalization. |
3-0 | DPTP016 | R | Fh | Transmitter Preset used for 16.0 GT/s equalization by this Port when the Port is operating as a Downstream Port. |
PCIE_CORE_PF0_I_PTM_EXTENDED_CAPABILITY_HEADER_REG is shown in Figure 12-1430 and described in Table 12-2798.
Return to the Summary Table.
Precision Time Measurement Extended Capability Structure is used discovering and controlling the distribution of a PTM hierarchy.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0A20h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
PTMNXCAP | PTMCAPVER | ||||||||||||||
R/W-0h | R/W-1h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
PTMCAPID | |||||||||||||||
R-1Fh | |||||||||||||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-20 | PTMNXCAP | R/W | 0h | The offset to the next PCIe Extended Capability structure. |
19-16 | PTMCAPVER | R/W | 1h | This field is a PCI-SIG defined version number that indicates the version of the Capability structure present. |
15-0 | PTMCAPID | R | 1Fh | Indicates that the associated extended capability structure is for Precision Time Measurement capability. This field returns a Capability ID of 001Fh. |
PCIE_CORE_PF0_I_PTM_CAPABILITIES_REG is shown in Figure 12-1431 and described in Table 12-2800.
Return to the Summary Table.
PTM Capabilities Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0A24h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R16 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R16 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
LOCCLKGR | |||||||
R/W-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R3 | PTMRTCAP | PTMRSCAP | PTMRQCAP | ||||
R-0h | R/W-0h | R/W-0h | R/W-1h | ||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | R16 | R | 0h | Reserved |
15-8 | LOCCLKGR | R/W | 0h | This field indicates the granularity of the PTM Local Clock in a PTM Time Source. In EP Mode: This field is not used and is set to 8'd00 by default. Note: This bit must not be programmed in EP Mode. |
7-3 | R3 | R | 0h | Reserved |
2 | PTMRTCAP | R/W | 0h | This bit is used to indicate that the Controller implements PTM Time Source Role and is capable of serving as PTM Root. By default, this bit is set to 0 when the Controller is in Endpoint Mode. Note: This bit must not be programmed in EP Mode. |
1 | PTMRSCAP | R/W | 0h | This bit is used to indicate support for PTM Responder Role. By default, this bit is set to 0 when the Controller is in Endpoint Mode. Note: This bit must not be programmed in EP Mode. |
0 | PTMRQCAP | R/W | 1h | This bit is used to indicate support for PTM Requester Role. By default, this bit is set to 1 when the Controller is in Endpoint Mode. This bit can be programmed through the local management APB interface if required. |
PCIE_CORE_PF0_I_PTM_CONTROL_REG is shown in Figure 12-1432 and described in Table 12-2802.
Return to the Summary Table.
PTM Control Register.
Instance | Physical Address |
---|---|
PCIE1_CORE_DBN_CFG_PCIE_CORE | 0D80 0A28h |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
R16 | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
R16 | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
EFFGRN | |||||||
R/W-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
R2 | RTSEL | PTMEN | |||||
R-0h | R/W-0h | R/W-0h | |||||
LEGEND: R = Read Only; R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | R16 | R | 0h | Reserved |
15-8 | EFFGRN | R/W | 0h | In EP Mode: This field provides information relating to the expected accuracy of the PTM Clock. However, this field does not impact the functionality of the PTM Requester. System SW is expected to program this field with to the value representing the maximum Local Clock Granularity reported by the PTM Root and all the intervening PTM Time Sources. |
7-2 | R2 | R | 0h | Reserved |
1 | RTSEL | R/W | 0h | Since Endpoint cannot be a PTM Root, this bit is set to 0 by default in Endpoint Mode. Note: This bit must not be programmed in EP Mode. |
0 | PTMEN | R/W | 0h | When Set, this function is permitted to participate in the PTM mechanism as PTM Requester. By default, this bit is set to 0. This field is configured by System SW. |