IOCTL_STORAGE_DEVICE_POWER_CAP IOCTL (ntddstor.h)
A driver can use IOCTL_STORAGE_DEVICE_POWER_CAP to specify a maximum operational power consumption level for a storage device. The OS will do its best to transition the device to a power state that will not exceed the given maximum; however, this depends on what the device supports. The actual maximum may be less than or greater than the desired maximum.
Major code
Input buffer
Irp->AssociatedIrp.SystemBuffer contains a STORAGE_DEVICE_POWER_CAP structure that specifies the maximum power.
Input buffer length
- Parameters.DeviceIoControl.InputBufferLength indicates the size, in bytes, of the input parameter buffer at Irp->AssociatedIrp.SystemBuffer, which must be greater than or equal to
sizeof(STORAGE_DEVICE_POWER_CAP).
Output buffer
If the operation is successful, the output buffer at Irp->AssociatedIrp.SystemBuffer will contain a STORAGE_DEVICE_POWER_CAP structure.
Output buffer length
Parameters.DeviceIoControl.OutputBufferLength indicates the size, in bytes, of the output parameter buffer at Irp->AssociatedIrp.SystemBuffer. OutputBufferLength must be greater than or equal to sizeof(STORAGE_DEVICE_POWER_CAP).
Status block
The Information field is set to the number of bytes returned. The Status field is set to STATUS_SUCCESS, or possibly to STATUS_INVALID_DEVICE_REQUEST, STATUS_INVALID_PARAMETER, or STATUS_NOT_SUPPORTED.
Remarks
For a reboot, the IOCTL_STORAGE_DEVICE_POWER_CAP effect is not persistent. For an NVMe device reset/power cycle, the IOCTL’s effect is persistent.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client | Windows 10 |
| Minimum supported server | Windows Server 2016 |
| Header | ntddstor.h (include Ntddstor.h) |
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for