diff options
| author | Ruiyu Ni <ruiyu.ni@intel.com> | 2017-08-04 17:07:31 +0800 |
|---|---|---|
| committer | Ruiyu Ni <ruiyu.ni@intel.com> | 2017-08-09 15:59:13 +0800 |
| commit | 7111e46fdebca0e03f6ddfcb029522c2fe68c74b (patch) | |
| tree | 4db6f365ba6e43a6d6fb1bfb020e00cb6c447856 /BaseTools/Source/Python/Common/ToolDefClassObject.py | |
| parent | a607eb97ef92605d88ac72e551bae34da7c81394 (diff) | |
| download | edk2-7111e46fdebca0e03f6ddfcb029522c2fe68c74b.tar.gz edk2-7111e46fdebca0e03f6ddfcb029522c2fe68c74b.tar.bz2 edk2-7111e46fdebca0e03f6ddfcb029522c2fe68c74b.zip | |
MdeModulePkg/NvmExpressDxe: Notify NVME HW when system reset happens
Per NVM Express Spec, software should notify NVME HW when shutdown
occurs.
The NVME controller requires notification for shutdown as part of
its management of internal structures. Even with FUA, failing to
notify the NVME controller to shutdown power off causes the NVME
controller to take quite some time to organize its tables on the
next power on. This time exceeds the normal timeout, so we would
fail to boot the NVME disk.
The host should set the Shutdown Notification (CC.SHN) field to 01b
to indicate a normal shutdown operation. The controller indicates
when shutdown processing is completed by updating the Shutdown Status
(CSTS.SHST) field to 10b.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Reviewed-by: Hao A Wu <hao.a.wu@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Common/ToolDefClassObject.py')
0 files changed, 0 insertions, 0 deletions