IDT PCI Express 89HPES32NT24xG2, User Manual, Page: 167 / 744

IDT Power Management
PES32NT24xG2 User Manual 9 - 3 January 30, 2013
Notes
– Any error message resulting from the reception of a TLP is reported in the same manner as when
the bridge is not in D3
hot
(e.g, generation of an ERR_NONFATAL message to the root).
• This requires transitioning the link to the L0 state when error reporting is enabled and the link is
not in L0.
– Error messages resulting from any event other than the reception of a TLP are discarded (i.e., no
error message is generated).
– All received completions that target the bridge are treated as unexpected completions (UC).
– Completions flowing in either direction through the bridge are routed as normal. This behavior of
the bridge does not differ from that of the bridge when it is in the D0 power management state.
• This requires transitioning the link to the L0 state when the completion needs to be transmitted
on the link by the bridge function and the link is not in L0.
• There is not need to transition the link to the L0 state when the completion is not transmitted on
the link by the bridge function (e.g., when the completion flows from the PCI-to-PCI bridge func-
tion to the NT function in a port configured in ‘Upstream Switch Port with NT Endpoint’ mode).
– All request TLPs received on the secondary interface are treated as unsupported requests (UR).
NT functions have the following behavior when in the D3
hot
power management state.
– The function accepts, processes and completes all type 0 configuration read and write requests.
– Accepts and processes all message requests that target the function.
– All requests received by the function, except as noted above, are treated as unsupported requests
(UR).
– Any error message resulting from the receipt of a TLP is reported in the same manner as when
the function is not in D3
hot
(e.g, generation of an ERR_NONFATAL message to the root).
• This requires transitioning the link to the L0 state when error reporting is enabled and the link is
not in L0.
– Error messages resulting from any event other than the receipt of a TLP are discarded (i.e., no
error message is generated).
– All received completions whose destination ID match the NT function’s bus/dev/function are
treated as unexpected completions (UC).
– All received completions transferred on the NT interconnect are routed as normal.
– All request TLPs received by another NT function that target the partition associated with the NT
function in D3
hot
are treated as unsupported requests (UR) by the NT function that receives the
TLP.
– All completion TLPs received by another NT function that target the partition associated with the
NT function in D3
hot
are silently dropped.
– Note that it is the responsibility of software (e.g., the NT driver) to ensure that inter-partition
communication associated with the NT function is properly quiesced prior to placing this function
into D3
hot
.
DMA functions have the following behavior when in the D3
hot
power management state.
– The function accepts, processes and completes all type 0 configuration read and write requests.
– Accepts and processes all message requests that target the function.
– All requests received by the function, except as noted above, are treated as unsupported requests
(UR).
– Any error message resulting from the receipt of a TLP is reported in the same manner as when
the function is not in D3
hot
(e.g, generation of an ERR_NONFATAL message to the root).