Protocol Implementation (touchpad-protocol-implementation)
This section provides guidelines for implementing the communication protocol that is used by Windows Precision Touchpad devices.
Touchpad devices are expected to use the Human Interface Device (HID) protocol to communicate with their Windows host.
A good understanding of the HID protocol is needed to be able to understand the information presented here. See the following resources for information about the HID protocol:
- Device Class Definition for Human Interface Devices (HID) Version 1.11
- HID Usage Tables Version 1.12
- HID Over I2C Protocol Specification Version 1.0
Windows includes a HID class driver and corresponding HID I²C, HID USB, HID SPI, and HID BTH miniport drivers. So there is no need to develop 3rd-party drivers for Windows Precision Touchpad devices that use one of these buses. However, if you want to use a 3rd-party bus controller, or develop your own to use with your device, you can do that.
If you want your device to connect via an alternate bus, then a 3rd-party HID mini-port driver might be required. You only need to report the usages described in this topic, in the firmware for your device. Windows will use your firmware and its own HID drivers to enable mouse and gesture capabilities for your device, and also provide Windows applications with access to your device.
A sample descriptor is provided in the Sample Report Descriptors topic.
In this section
| Topic | Description |
|---|---|
This topic presents the required HID descriptors (and device attributes) for a Windows Precision Touchpad device in Windows 10 and later operating systems. |
|
This section discusses the required HID top-level collections that are used for precision touchpad reporting in Windows 10 and later operating systems. |
|
This topic presents a sample report descriptor and sample descriptor excerpts for a Windows Precision Touchpad device. |