If the boundary between static (PS) and dynamic (PL) is specifically at the PS-PL interface, the following use cases apply:
- If the entire PL is included in the dynamic region, partial reconfiguration includes a power domain shutdown. This temporarily powers down the entire PL. The Segmented Configuration PL reload use case specifically covers this scenario.
- If a portion of the PL is included in the dynamic region and abuts the PS, you must manage decoupling from the PS domain. This means flushing transactions and pausing activity on the reconfigured PL-side interfaces to ensure no system lockup occurs.
- The static design should include the functional behavior required for the data and interface management. It can implement mechanisms such as handshaking or disabling interfaces, which might be required for bus structures to avoid invalid transactions. Also consider the down-time performance effect of a dynamic module. This is the unavailability of any shared resources in the dynamic module during or after reconfiguration. This is the most common scenario.