Skip to content

Latest commit

 

History

History
73 lines (59 loc) · 2.82 KB

ns-ufxbase-_ufx_hardware_failure_context.md

File metadata and controls

73 lines (59 loc) · 2.82 KB
UID title description old-location tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames f1_keywords topic_type api_type api_location api_name
NS:ufxbase._UFX_HARDWARE_FAILURE_CONTEXT
_UFX_HARDWARE_FAILURE_CONTEXT (ufxbase.h)
The UFX_HARDWARE_FAILURE_CONTEXT structure is used to define controller-specific hardware failure properties.
buses\ufx_hardware_failure_context.htm
usbref
05/07/2018
UFX_HARDWARE_FAILURE_CONTEXT structure
*PUFX_HARDWARE_FAILURE_CONTEXT, PUFX_HARDWARE_FAILURE_CONTEXT, PUFX_HARDWARE_FAILURE_CONTEXT structure pointer [Buses], UFX_HARDWARE_FAILURE_CONTEXT, UFX_HARDWARE_FAILURE_CONTEXT structure [Buses], _UFX_HARDWARE_FAILURE_CONTEXT, buses.ufx_hardware_failure_context, ufxbase/PUFX_HARDWARE_FAILURE_CONTEXT, ufxbase/UFX_HARDWARE_FAILURE_CONTEXT
ufxbase.h
Windows
Windows
UFX_HARDWARE_FAILURE_CONTEXT, *PUFX_HARDWARE_FAILURE_CONTEXT
_UFX_HARDWARE_FAILURE_CONTEXT
ufxbase/_UFX_HARDWARE_FAILURE_CONTEXT
PUFX_HARDWARE_FAILURE_CONTEXT
ufxbase/PUFX_HARDWARE_FAILURE_CONTEXT
UFX_HARDWARE_FAILURE_CONTEXT
ufxbase/UFX_HARDWARE_FAILURE_CONTEXT
APIRef
kbSyntax
HeaderDef
ufxbase.h
_UFX_HARDWARE_FAILURE_CONTEXT
PUFX_HARDWARE_FAILURE_CONTEXT
UFX_HARDWARE_FAILURE_CONTEXT

_UFX_HARDWARE_FAILURE_CONTEXT structure

-description

The UFX_HARDWARE_FAILURE_CONTEXT structure is used to define controller-specific hardware failure properties.

-struct-fields

-field Size

The size of the UFX_HARDWARE_FAILURE_CONTEXT structure.

-field ExceptionCode

The controller-specific hardware failure code.

-field Data

A variable-length array of data associated with the hardware failure.

-remarks

In cases where the function controller has experienced a fatal error, the client driver may allocate a variable-length UFX_HARDWARE_FAILURE_CONTEXT structure, set the Size field to the allocated size, set the ExceptionCode field to a value indicating the type of hardware error (as defined by the client driver) and fill in any associated information in the Data array. It may then pass this structure to the UfxDeviceNotifyHardwareFailure UFX function. UFX will in turn pass this structure to the client driver’s EVT_UFX_DEVICE_CONTROLLER_RESET event callback function (if it exists).