- Feature Name:
- PI Phase(s) Supported:
- SMM Required?
Simple overview that describes the purpose of the feature. In general, this should be no longer than one paragraph.
High-Level Theory of Operation¶
A description of how the device works at a high-level.
The description should not be constrained to implementation details but provide a simple mental model of how the feature is supposed to work.
A bulleted list of the firmware volumes that feature module(s) are placed in.
A bulleted list of the modules that make up the feature.
Each module in the feature should have a section that describes the module in a level of detail that is useful to better understand the module source code.
Each library in the feature should have a section that describes the library in a level of detail that is useful to better understand the library source code.
A bulleted list of key functions for interacting with the feature.
Not all features need to be listed. Only functions exposed through external interfaces that are important for feature users to be aware of.
Information that is useful for configuring the feature.
Not all configuration options need to be listed. This section is used to provide more background on configuration options than possible elsewhere.
Architecturally defined data structures and flows for the feature.
Key control flows for the feature.
Any special build flows should be described in this section.
This is particularly useful for features that use custom build tools or require non-standard tool configuration. If the standard flow in the feature package template is used, this section may be empty.
Test Point Results¶
The test(s) that can verify porting is complete for the feature.
Each feature must describe at least one test point to verify the feature is successful. If the test point is not implemented, this should be stated.
Functional Exit Criteria¶
The testable functionality for the feature.
This section should provide an ordered list of criteria that a board integrator can reference to ensure the feature is functional on their board.
Feature Enabling Checklist¶
An ordered list of required activities to achieve desired functionality for the feature.
A general expectation for the impact on overall boot performance due to using this feature.
This section is expected to provide guidance on: * How to estimate performance impact due to the feature * How to measure performance impact of the feature * How to manage performance impact of the feature
Common size or performance tuning options for this feature.
This section is recommended but not required. If not used, the contents should be left empty.