HID_WIN_API_总结

1. HidD_GetHidGuid

The HidD_GetHidGuid routine returns the device interface GUID for HIDClass devices.

VOID

HidD_GetHidGuid(

OUT LPGUID HidGuid

);

Parameters

HidGuid

Pointer to a caller-allocated GUID buffer that the routine uses to return the

device interface GUID for HIDClass devices.

Return Value

None.

Headers

Declared in hidsdi.h. Include hidsdi.h.

Comments

Only user-mode applications can call HidD_GetHidGuid.

For more information, see HID Concepts, HID collections, and Operating HID Collections.

See Also

IoGetDeviceInterfaces

Built on Friday, April 11, 2003

调用hidD_GetHidGuid(hidGuid) hidGuid{4d1e55b2-f16f-11cf-88cb-001111000030}System.Guid

2.SetupDiGetClassDevs

The SetupDiGetClassDevs function returns a device information set that contains all devices of a specified class.

HDEVINFO

SetupDiGetClassDevs(

IN LPGUID ClassGuid, OPTIONAL

IN PCTSTR Enumerator, OPTIONAL

IN HWND hwndParent, OPTIONAL

IN DWORD Flags

);

Parameters

ClassGuid

Optionally points to a class GUID for a setup class or an interface class. If the

DIGCF_DEVICEINTERFACE flag is set, ClassGuid represents an interface

class; otherwise, ClassGuid represents a setup class.

If the DIGCF_ALLCLASSES flag is set, this parameter is ignored and

the resulting list contains devices of all installed classes.

Enumerator

Optionally points to a string that filters the devices that are returned.

If the DIGCF_DEVICEINTERFACE flag is set, this parameter optionally points to a string representing the PnP name of a particular device.

This function only examines this particular device to determine whether it exposes any interfaces of the requested interface class.

If the DIGCF_DEVICEINTERFACE flag is not set, this parameter

optionally specifies the name of the PnP enumerator that enumerates

the devices of interest. (The names of system-supplied enumerators

appear in register.h.) This function only examines device instances of

this enumerator. If this parameter is NULL, this function retrieves

device information for all device instances on the system. hwndParent

Supplies the handle of the top-level window to be used for any user interface

relating to the members of this set.

Flags

Supplies control options used in building the device information set. Can be a

combination of the following values:

DIGCF_ALLCLASSES

Return a list of installed devices for all classes. If this flag is set, the

ClassGuid parameter is ignored.

DIGCF_DEVICEINTERFACE

Return devices that expose interfaces of the interface class specified by

ClassGuid. If this flag is not set, ClassGuid specifies a setup class.

DIGCF_PRESENT

Return only devices that are currently present.

DIGCF_PROFILE

Return only devices that are a part of the current hardware profile.

Return Value

SetupDiGetClassDevs returns a handle to a device information set containing all installed devices matching the specified parameters. If the function fails, it returns INVALID_HANDLE_VALUE or another appropriate error. To get extended error information, call GetLastError.

Headers

Declared in setupapi.h. Include setupapi.h.

Comments

The caller of this function must delete the returned device information set when it is no longer needed by calling SetupDiDestroyDeviceInfoList.

If DIGCF_DEVICEINTERFACE is set, ClassGuid (if used) must point to a device interface class GUID and Enumerator (if used) must point to a PnP device name. The returned device information set contains devices that expose interfaces of the requested interface class. Enumerate the interfaces of the devices using SetupDiEnumDeviceInterfaces.

If DIGCF_DEVICEINTERFACE is not set, ClassGuid (if used) must point to a setup class GUID and Enumerator (if used) must specify the name of the PnP enumerator that enumerates the devices of interest.

Call SetupDiGetClassDevsEx to retrieve the devices for a class on a remote machine.

See Also

SetupDiCreateDeviceInfoList, SetupDiDestroyDeviceInfoList, SetupDiEnumDeviceInterfaces, SetupDiGetClassDevsEx

Built on Friday, April 11, 2003

3.SetupDiDestroyDeviceInfoList

The SetupDiDestroyDeviceInfoList function destroys a device information set and frees all associated memory.

WINSETUPAPI BOOL WINAPI

SetupDiDestroyDeviceInfoList(

IN HDEVINFO DeviceInfoSet

);

Parameters

DeviceInfoSet

Supplies a handle to the device information set to destroy.

Return Value

The function returns TRUE if it is successful. Otherwise, it returns FALSE and the logged error can be retrieved with a call to GetLastError.

Headers

Declared in setupapi.h. Include setupapi.h.

See Also

SetupDiCreateDeviceInfoList, SetupDiGetClassDevs

Built on Friday, April 11, 2003

4.SetupDiEnumDeviceInterfaces

The SetupDiEnumDeviceInterfaces function returns a context structure for a device interface element of a device information set. Each call returns

information about one device interface; the function can be called repeatedly to get information about several interfaces exposed by one or more devices. WINSETUPAPI BOOL WINAPI

SetupDiEnumDeviceInterfaces(

IN HDEVINFO DeviceInfoSet,

IN PSP_DEVINFO_DATA DeviceInfoData, OPTIONAL

IN LPGUID InterfaceClassGuid,

IN DWORD MemberIndex,

OUT PSP_DEVICE_INTERFACE_DATA DeviceInterfaceData

);

Parameters

DeviceInfoSet

Pointer to a device information set containing the device(s) for which to return interface information. This handle is typically returned by

SetupDiGetClassDevs.

DeviceInfoData

Optionally points to an SP_DEVINFO_DATA structure that constrains the

search for interfaces to those of just one device in the device information set.

This pointer is typically returned by SetupDiEnumDeviceInfo. InterfaceClassGuid

Pointer to a GUID that specifies the device interface class for the requested

interface.

MemberIndex

Specifies a zero-based index into the list of interfaces in the device

information set. The caller should call this function first with MemberIndex set to zero to obtain the first interface. Then, repeatedly increment MemberIndex

and retrieve an interface until this function fails and GetLastError returns

ERROR_NO_MORE_ITEMS.

If DeviceInfoData specifies a particular device, the MemberIndex is

relative to only the interfaces exposed by that device. DeviceInterfaceData

Pointer to a caller-allocated buffer that contains, on successful return, a

completed SP_DEVICE_INTERFACE_DATA structure that identifies an

interface that meets the search parameters. The caller must set

DeviceInterfaceData.cbSize to sizeof(SP_DEVICE_INTERFACE_DATA)

before calling this function.

Return Value

SetupDiEnumDeviceInterfaces returns TRUE if the function completed without error. If the function completed with an error, FALSE is returned and the error code for the failure can be retrieved by calling GetLastError.

Headers

Declared in setupapi.h. Include setupapi.h.

Comments

DeviceInterfaceData points to a structure that identifies a requested device interface. To get detailed information about an interface, call SetupDiGetDeviceInterfaceDetail. The detailed information includes the name of the device interface that can be passed to a Win32? function such as CreateFile (described in Platform SDK documentation) to get a handle to the interface.

See Also

SetupDiGetClassDevs, SetupDiEnumDeviceInfo, SetupDiGetDeviceInterfaceDetail

Built on Friday, April 11, 2003

SP_DEVICE_INTERFACE_DATA

An SP_DEVICE_INTERFACE_DATA structure defines a device interface in a device information set.

typedef struct _SP_DEVICE_INTERFACE_DATA {

DWORD cbSize;

GUID InterfaceClassGuid;

DWORD Flags;

ULONG_PTR Reserved;

} SP_DEVICE_INTERFACE_DATA, *PSP_DEVICE_INTERFACE_DATA;

Members

cbSize

The size, in bytes, of the SP_DEVICE_INTERFACE_DATA structure. InterfaceClassGuid

The GUID for the class to which the device interface belongs.

Flags

Can be one or more of the following:

SPINT_ACTIVE

The interface is active (enabled).

SPINT_DEFAULT

The interface is the default interface for the device class.

SPINT_REMOVED

The interface is removed.

Reserved

Reserved. Do not use.

See Also

SetupDiCreateDeviceInterface, SetupDiEnumDeviceInterfaces, SetupDiGetDeviceInterfaceAlias, SetupDiOpenDeviceInterface, SetupDiSetDeviceInterfaceDefault,

SP_DEVICE_INTERFACE_DETAIL_DATA

Built on Friday, April 11, 2003

5.SetupDiGetDeviceInterfaceDetail

The SetupDiGetDeviceInterfaceDetail function returns details about a particular device interface.

WINSETUPAPI BOOL WINAPI

SetupDiGetDeviceInterfaceDetail(

IN HDEVINFO DeviceInfoSet,

IN PSP_DEVICE_INTERFACE_DATA DeviceInterfaceData,

OUT PSP_DEVICE_INTERFACE_DETAIL_DATA DeviceInterfaceDetailData, OPTIONAL IN DWORD DeviceInterfaceDetailDataSize,

OUT PDWORD RequiredSize, OPTIONAL

OUT PSP_DEVINFO_DATA DeviceInfoData OPTIONAL

);

Parameters

DeviceInfoSet

Pointer to the device information set containing the interface and its

underlying device. This handle is typically returned by

SetupDiGetClassDevs.

DeviceInterfaceData

Pointer to a SP_DEVICE_INTERFACE_DATA structure that identifies the

interface, typically returned by SetupDiEnumDeviceInterfaces. DeviceInterfaceDetailData

Optionally points to a caller-allocated

SP_DEVICE_INTERFACE_DETAIL_DATA structure to receive information about the specified interface. The caller must set

DeviceInterfaceDetailData.cbSize to

sizeof(SP_DEVICE_INTERFACE_DETAIL_DATA) before calling this

function. The cbSize field always contains the size of the fixed part of the data structure, not a size reflecting the variable-length string at the end.

This parameter must be NULL if DeviceInterfaceDetailSize is zero. DeviceInterfaceDetailDataSize

Specifies the size of the DeviceInterfaceDetailData buffer. The buffer must be at least (offsetof(SP_DEVICE_INTERFACE_DETAIL_DATA, DevicePath) + sizeof(TCHAR)) bytes, to contain the fixed part of the structure and a single NULL to terminate an empty MULTI_SZ string.

This parameter must be zero if DeviceInterfaceDetailData is NULL. RequiredSize

Optionally points to a caller-allocated variable to receive the required size of

the DeviceInterfaceDetailData buffer. This size includes the size of the fixed

part of the structure plus the number of bytes required for the variable-length

device path string.

DeviceInfoData

Optionally points to a caller-allocated buffer to receive information about the

device that exposes the requested interface. The caller must set

DeviceInfoData.cbSize to sizeof(SP_DEVINFO_DATA).

Return Value

SetupDiGetDeviceInterfaceDetail returns TRUE if the function completed without error. If the function completed with an error, FALSE is returned and the error code for the failure can be retrieved by calling GetLastError.

Headers

Declared in setupapi.h. Include setupapi.h.

Comments

Using this function to get details about an interface is typically a two-step process:

1.Get the required buffer size. Call SetupDiGetDeviceInterfaceDetail with a

NULL DeviceInterfaceDetailData pointer, an DeviceInterfaceDetailDataSize

of zero, and a valid RequiredSize variable. In response to such a call, this

function returns the required buffer size at RequiredSize and fails with

GetLastError returning ERROR_INSUFFICIENT_BUFFER.

2.Allocate an appropriately sized buffer and call the function again to get the

interface details.

The interface detail returned by this function consists of a device path that can be passed to Win32 functions such as CreateFile. Do not attempt to parse the device path symbolic name. The device path can be reused across system boots.

SetupDiGetDeviceInterfaceDetail can be used to get just the DeviceInfoData. If the interface exists but DeviceInterfaceDetailData is NULL, this function fails, GetLastError returns ERROR_INSUFFICIENT_BUFFER, and the DeviceInfoData structure is filled with information about the device that exposes the interface.

See Also

SetupDiEnumDeviceInterfaces, SetupDiGetClassDevs

Built on Friday, April 11, 2003

SP_DEVICE_INTERFACE_DETAIL_D ATA

An SP_DEVICE_INTERFACE_DETAIL_DATA structure contains the path for a device interface.

typedef struct _SP_DEVICE_INTERFACE_DETAIL_DATA {

DWORD cbSize;

TCHAR DevicePath[ANYSIZE_ARRAY];

} SP_DEVICE_INTERFACE_DETAIL_DATA, *PSP_DEVICE_INTERFACE_DETAIL_DATA; Members

cbSize

The size, in bytes, of the fixed portion of the

SP_DEVICE_INTERFACE_DETAIL_DATA structure.

DevicePath

A NULL-terminated string that contains the device interface path. This path

can be passed to Win32? functions such as CreateFile.

See Also

SetupDiGetDeviceInterfaceDetail

Built on Friday, April 11, 2003

6.HidD_GetAttributes

The HidD_GetAttributes routine returns the attributes of a specified top-level collection.

BOOLEAN

HidD_GetAttributes(

IN HANDLE HidDeviceObject,

OUT PHIDD_ATTRIBUTES Attributes

);

Parameters

HidDeviceObject

Specifies an open handle to a top-level collection.

Attributes

Pointer to a caller-allocated HIDD_ATTRIBUTES structure that returns the

attributes of the collection specified by HidDeviceObject.

Return Value

HidD_GetAttributes returns TRUE if succeeds; otherwise, it returns FALSE. Headers

Declared in hidsdi.h. Include hidsdi.h.

Comments

Only user-mode applications can call HidD_GetAttributes. Kernel-mode drivers can use IOCTL_HID_GET_COLLECTION_INFORMATION.

For more information, see HID Concepts, HID collections, and Operating HID Collections.

See Also

HIDD_ATTRIBUTES, IOCTL_HID_GET_COLLECTION_INFORMATION

Built on Friday, April 11, 2003

HIDD_ATTRIBUTES

The HIDD_ATTRIBUTES structure contains vendor information about a HIDClass device.

typedef struct _HIDD_ATTRIBUTES {

ULONG Size;

USHORT VendorID;

USHORT ProductID;

USHORT VersionNumber;

} HIDD_ATTRIBUTES, *PHIDD_ATTRIBUTES;

Members

Size

Specifies the size, in bytes, of a HIDD_ATTRIBUTES structure.

VendorID

Specifies a HID device's vendor ID.

ProductID

Specifies a HID device's product ID.

VersionNumber

Specifies the manufacturer's revision number for a HIDClass device. Headers

Declared in hidsdi.h. Include hidsdi.h.

Comments

A caller of HidD_GetAttributes, uses this structure to obtain a device's vendor information.

Before using a HIDD_ATTRIBUTES structure with HIDClass Support Routines, the caller must set the Size member.

See Also

HidD_GetAttributes

Built on Friday, April 11, 2003

7. RegisterDeviceNotification

HDEVNOTIFY WINAPI RegisterDeviceNotification(

__in HANDLE hRecipient,

__in LPVOID NotificationFilter,

__in DWORD Flags

);

Parameters

hRecipient [in]

A handle to the window or service that will receive device events for the devices

specified in the NotificationFilter parameter. The same window handle can be used in

multiple calls to RegisterDeviceNotification.

Services can specify either a window handle or service status handle. NotificationFilter [in]

A pointer to a block of data that specifies the type of device for which notifications

should be sent. This block always begins with the DEV_BROADCAST_HDR structure.

The data following this header is dependent on the value of the dbch_devicetype

member, which can be DBT_DEVTYP_DEVICEINTERFACE or DBT_DEVTYP_HANDLE. For more information, see Remarks.

Flags [in]

This parameter can be one of the following values.

Value Meaning

DEVICE_NOTIFY_WINDOW_HANDLE

0x00000000The hRecipient parameter is a window handle.

DEVICE_NOTIFY_SERVICE_HANDLE 0x00000001The hRecipient parameter is a service status handle.

In addition, you can specify the following value.

Value Meaning

DEVICE_NOTIFY_ALL_INTERFACE_CLASSES 0x00000004Notifies the recipient of device interface events for all device interface classes. (The dbcc_classguid member is ignored.) This value can be used only if the

dbch_devicetype member is

DBT_DEVTYP_DEVICEINTERFACE.

Windows2000:This

value is not supported.

Return Value

If the function succeeds, the return value is a device notification handle.

If the function fails, the return value is NULL. To get extended error information, call GetLastError.

Remarks

Applications send event notifications using the BroadcastSystemMessage function. Any application with a top-level window can receive basic notifications by processing the

WM_DEVICECHANGE message. Applications can use the RegisterDeviceNotification function to register to receive device notifications.

Services can use the RegisterDeviceNotification function to register to receive device notifications. If a service specifies a window handle in the hRecipient parameter, the notifications are sent to the window procedure. If hRecipient is a service status handle, SERVICE_CONTROL_DEVICEEVENT notifications are sent to the service control handler. For more information about the service control handler, see HandlerEx.

Be sure to handle Plug and Play device events as quickly as possible. Otherwise, the system may become unresponsive. If your event handler is to perform an operation that may block execution (such as I/O), it is best to start another thread to perform the operation asynchronously.

Device notification handles returned by RegisterDeviceNotification must be closed by calling the UnregisterDeviceNotification function when they are no longer needed.

The DBT_DEVICEARRIVAL and DBT_DEVICEREMOVECOMPLETE events are automatically broadcast to all top-level windows for port devices. Therefore, it is not necessary to call RegisterDeviceNotification for ports, and the function fails if the dbch_devicetype member is DBT_DEVTYP_PORT. Volume notifications are also broadcast to top-level windows, so the function fails if dbch_devicetype is DBT_DEVTYP_VOLUME. OEM-defined devices are not used directly by the system, so the function fails if dbch_devicetype is DBT_DEVTYP_OEM.

Examples

For an example, see Registering for Device Notification.

Requirements

Minimum supported

client Windows2000 Professional

Minimum supported

server Windows2000 Server

Header Winuser.h (include Windows.h)

Library User32.lib

DLL User32.dll

Unicode and ANSI

names RegisterDeviceNotificationW (Unicode) and RegisterDeviceNotificationA (ANSI)

See Also

BroadcastSystemMessage

DEV_BROADCAST_HDR

Device Management Functions

Device Notifications

HandlerEx

UnregisterDeviceNotification

WM_DEVICECHANGE

Send comments about this topic to Microsoft

Build date: 3/18/2010

typedef struct _DEV_BROADCAST_HDR {

DWORD dbch_size;

DWORD dbch_devicetype;

DWORD dbch_reserved;

} DEV_BROADCAST_HDR, *PDEV_BROADCAST_HDR;

Members

dbch_size

The size of this structure, in bytes.

If this is a user-defined event, this member must be the size of this header, plus the

size of the variable-length data in the _DEV_BROADCAST_USERDEFINED structure. dbch_devicetype

The device type, which determines the event-specific information that follows the first three members. This member can be one of the following values.

Value Meaning

DBT_DEVTYP_DEVICEINTERFACE 0x00000005Class of devices. This structure is a

DEV_BROADCAST_DEVICEINTERFACE structure.

DBT_DEVTYP_HANDLE 0x00000006File system handle. This structure is a DEV_BROADCAST_HANDLE structure.

DBT_DEVTYP_OEM 0x00000000OEM- or IHV-defined device type. This structure is a DEV_BROADCAST_OEM structure.

DBT_DEVTYP_PORT 0x00000003Port device (serial or parallel). This structure is a DEV_BROADCAST_PORT structure.

DBT_DEVTYP_VOLUME 0x00000002Logical volume. This structure is a DEV_BROADCAST_VOLUME structure.

dbch_reserved

Reserved; do not use.

Requirements

Minimum supported client W

Minimum supported server W

Header Dbt.h

8.HidD_SetOutputReport

The HidD_SetOutputReport routine sends an output report to a top-level collection.

BOOLEAN __stdcall

HidD_SetOutputReport(

IN HANDLE HidDeviceObject,

IN PVOID ReportBuffer,

IN ULONG ReportBufferLength

);

HidDeviceObject

Specifies an open handle to a top-level collection.

ReportBuffer

Pointer to a caller-allocated output report buffer that the caller uses to specify

a report ID.

If the top-level collection includes report IDs, the caller must set the first byte of the buffer to a nonzero report ID; otherwise, the caller must set the first byte to zero.

The output report — excluding its report ID, if report IDs are used — is located at ((PUCHAR)ReportBuffer+ 1).

ReportBufferLength

Specifies the size, in bytes, of the report buffer. The report buffer must be

large enough to hold the output report — excluding its report ID, if report IDs are used — plus one additional byte that specifies a nonzero report ID or zero.

Return Value

If HidD_SetOutputReport succeeds, it returns TRUE; otherwise, it returns FALSE.

Headers

Declared in hidsdi.h. Include hidsdi.h.

Comments

Only user-mode applications can call HidD_SetOutputReport. Kernel-mode drivers can use an IOCTL_HID_SET_OUTPUT_REPORT request.

See also Sending HID Reports.

For more information, see HID Concepts, HID collections, and Operating HID Collections.

See Also

HidD_GetFeature, HidD_GetInputReport, HidD_SetFeature,

IOCTL_HID_GET_FEATURE, IOCTL_HID_GET_INPUT_REPORT,

IOCTL_HID_SET_FEATURE, IOCTL_HID_SET_OUTPUT_REPORT

Built on Friday, April 11, 2003

9.HidD_GetFeature

The HidD_GetFeature routine returns a feature report from a specified top-level collection.

BOOLEAN

HidD_GetFeature(

IN HANDLE HidDeviceObject,

OUT PVOID ReportBuffer,

IN ULONG ReportBufferLength

);

Parameters

HidDeviceObject

Specifies an open handle to a top-level collection.

ReportBuffer

Pointer to a caller-allocated HID report buffer that the caller uses to specify a

report ID. HidD_GetFeature uses ReportBuffer to return the specified feature report.

If the top-level collection includes report IDs, the caller must set the first byte of the buffer to a nonzero report ID; otherwise the caller must set

the first byte to zero.

ReportBufferLength

Specifies the size, in bytes, of the report buffer. The report buffer must be

large enough to hold the feature report — excluding its report ID, if report IDs are used — plus one additional byte that specifies a nonzero report ID or zero. Return Value

If HidD_GetFeature succeeds, it returns TRUE; otherwise, it returns FALSE.

Headers

Declared in hidsdi.h. Include hidsdi.h.

Comments

The feature report — excluding its report ID, if report IDs are used — is returned at ((PUCHAR)ReportBuffer + 1).

Only user-mode applications can call HidD_GetFeature. Kernel-mode drivers can use an IOCTL_HID_GET_FEATURE request.

For more information, see the following topics:

USB HID Standard

Hid Concepts

Obtaining HID Reports

See Also

HidD_SetFeature, HidD_GetInputReport, HidD_SetOutputReport,

IOCTL_HID_GET_FEATURE, IOCTL_HID_GET_INPUT_REPORT,

IOCTL_HID_SET_FEATURE, IOCTL_HID_SET_OUTPUT_REPORT

Built on Friday, April 11, 2003

HID Reports

A HID report is used to transmit HID control data to and from a HIDClass device. A report descriptor defines the format of a report. Input and output reports specify control data and feature reports specify configuration data. If a device supports more than one report of the same type, each report is assigned a unique report ID. The following figure shows an example of a HID collection that contains two input reports.

Example of a HID Collection with Two Input Reports

This figure shows two input reports, one containing value and button data and the other containing only button data. In general, the number of reports within a HID collection and the number of values and buttons in a report are device-specific.

Input and Output Reports

Input and output reports specify HID control data. Input controls are sources of data relevant to an application, for example, x and y data obtained from a pointing device. Output controls are a sink for application data, for example, an LED that indicates the state of a device.

For information about reading and writing reports, see Obtaining HID Reports and Sending HID Reports.

Feature Reports

A feature report specifies configuration information for a device. A user-mode application obtains and sets feature information by using the following HIDClass support routines:

HidD_GetFeature

HidD_SetFeature

A kernel-mode driver obtains and sets feature information by using the following HID class driver IOCTLs:

IOCTL_HID_GET_FEATURE

IOCTL_HID_SET_FEATURE

Built on Friday, April 11, 2003

HidD_SetFeature

The HidD_SetFeature routine sends a feature report to a top-level collection. BOOLEAN

HidD_SetFeature(

IN HANDLE HidDeviceObject,

IN PVOID ReportBuffer,

IN ULONG ReportBufferLength

);

Parameters

HidDeviceObject

Specifies an open handle to a top-level collection.

ReportBuffer

Pointer to a caller-allocated feature report buffer that the caller uses to specify

a HID report ID.

If the top-level collection includes report IDs, the caller must set the first byte of the buffer to a nonzero report ID; otherwise, the caller must set the first byte to zero.

The feature report — excluding its report ID, if report IDs are used — is located at ((PUCHAR)ReportBuffer + 1).

ReportBufferLength

Specifies the size, in bytes, of the report buffer. The report buffer must be

large enough to hold the feature report — excluding its report ID, if report IDs are used — plus one additional byte that specifies a nonzero report ID or zero.

Return Value

If HidD_SetFeature succeeds, it returns TRUE; otherwise, it returns FALSE. Headers

Declared in hidsdi.h. Include hidsdi.h.

Comments

Only user-mode applications can call HidD_SetFeature. Kernel-mode drivers can use the IOCTL_HID_SET_FEATURE request.

For more information, see the following topics:

USB HID Standard

HID Concepts

Sending HID Reports

See Also

HidD_GetFeature, HidD_GetInputReport, HidD_SetOutputReport,

IOCTL_HID_GET_FEATURE, IOCTL_HID_GET_INPUT_REPORT,

IOCTL_HID_SET_FEATURE, IOCTL_HID_SET_OUTPUT_REPORT

Built on Friday, April 11, 2003

10.HidP_GetCaps

The HidP_GetCaps routine returns a top-level collection's HIDP_CAPS structure.

NTSTATUS

HidP_GetCaps(

IN PHIDP_PREPARSED_DATA PreparsedData,

OUT PHIDP_CAPS Capabilities

);