Parameter Storage Management in Multi-Power Domain Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data processing systems with multiple power domains face challenges in efficiently managing parameter values across different power states, particularly in non-retaining states where data is lost, and require mechanisms to reload data with minimal overhead and delay.
Innovation Solution
A data processing apparatus with a master store in one power domain and slave stores in others, where parameter value fetching circuitry retrieves the parameter value from another slave store when switching from a non-retaining to a retaining power state, reducing the need for direct access to the master store and minimizing overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If parameter values are stored in slave stores within each power domain, then access speed to parameter values is improved, but data loss occurs when the domain enters non-retaining power state
Solution Approach 1:
The system performs preliminary actions by maintaining slave stores with parameter copies in power domains that will remain in retaining state, so that when a domain needs to switch to non-retaining state, the data is already preserved in the slave store of another domain ready for rapid retrieval
Solution Approach 2:
Slave stores act as intermediary storage elements between the master store and the power domain registers. They provide local cached copies that can be rapidly retrieved without requiring the domain to be fully powered up or accessing the central master store, thus mediating between data persistence and fast access needs
2Reliability
If direct access to master store is used for parameter values, then data consistency is maintained, but congestion and delay increase during power state switching
Solution Approach 1:
The system segments the parameter storage function by distributing copies of parameter values across multiple slave stores in different power domains. This segmentation allows multiple domains to access parameter data simultaneously from their local slave stores without congesting the single master store, reducing switch time and improving responsiveness
Solution Approach 2:
Parameter values are preliminarily copied to slave stores before power state changes occur. This preliminary action ensures that when a domain switches to non-retaining state, the data is already available in the slave store of another domain that can quickly supply the needed parameter values, avoiding delays in reconfiguration
3Reliability
If parameter values are reloaded from master store during power state change, then data freshness is ensured, but overhead and switching time increase
Solution Approach 1:
Slave stores serve as intermediary data sources that hold cached copies of parameter values. When a domain switches from non-retaining to retaining state, it can retrieve fresh data from the slave store of another domain that maintained the data, rather than requiring a direct reload from the master store, thus reducing overhead and switching time while ensuring data freshness
Solution Approach 2:
The system uses copying by maintaining duplicate copies of parameter values in slave stores across multiple power domains. This copying mechanism allows rapid data retrieval without requiring complete reconfiguration or direct access to the master store, reducing the complexity and time of power state transitions while preserving data accuracy
Data Source
AI summary
An apparatus for processing data 2 contains multiple power domains which may be in a non-retaining power state or a retaining power state. If a power domain is in a non-retaining power state in which it is not able to retain a copy of a stored parameter value and it is switched into a retaining power state in which it requires a copy of that parameter value, then it fetches the parameter value from a store within another power domain. One of the power domains contains a master copy of the parameter value to which writes changing in the parameter value are made. At least one of the other power domains fetches a copy of the parameter value if required from a power domain other than the power domain containing the master copy.