Touch, Input, and HID: Architecture and Driver Support

Windows supports uniform access to input devices that are based on the Human Interface Devices (sometimes called the Human Input Devices) or HID specification. Vendors can extend the functionality of devices by adding filter drivers to the Windows layered driver architecture. Vendor-written drivers for most devices can use UMDF. Mouse and keyboard filter drivers should use KMDF.

While earlier versions of Windows supported USB as the primary HID transport; Microsoft provides native support for the following transports in Windows 8:

• USB
• Bluetooth
• Bluetooth LE
• I²C

Vendor specific transports are also allowed via 3rd party transport drivers. For more information, refer to the Human Input Devices section of the Windows Driver Kit documentation on MSDN.

Enhanced Keyboards and Windows. Keyboards with special buttons (to start a browser, to control volume, and so on) do not require special drivers. In fact, custom drivers can lengthen boot time. We encourage vendors to implement HID-compatible scan codes, and use the built-in HID support in Windows.

Tablet and Windows Touch Topics

• Design Recommendations for Windows 8 Touchpads
• Touch in Windows 8
• How to use the RA Tool to measure Touch Latency (Video) (08 minutes 08 seconds)
• How to Use the Precision Touch Testing Tool (Video) (8 minutes, 3 seconds)

Input Device Topics for Windows 8

• USB Biometric Input Device Class Proposal
• Windows Keyboard Layouts
• Best Practices for Developing Third-Party Drivers for Keyboards, Mice, and Touchpads
• The HID Class Driver for Sensors
• HID Sensors Usages
• HID over Bluetooth (Human Interface Device Profile)
• HID over I²C
• HID over I²C Protocol Specification
• HID over USB
• Human Input Devices