The driver must handle the IOCTL_HID_SET_OUTPUT_REPORT or custom IOCTLS sent by a companion application (or the OS) to update the active calibration.
To implement effective calibration, you must first understand how Windows communicates with your I2C touch controller. The architecture is modular, separating low-level transport from high-level Windows Touch Input infrastructure. The Driver Stack kmdf hid minidriver for touch i2c device calibration best
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. The Driver Stack This public link is valid
For high-report-rate touch screens, configure a WDFIOTARGET with a continuous reader to pre-fetch touch data into a ring buffer. Can’t copy the link right now
: For out-of-band communication like sending new calibration data from a user-mode application, expose a secondary Top-Level Collection (TLC) in your HID descriptor. Typical Calibration Workflow
For standard I2C touch devices, Approach A (Firmware Handled) is preferred. However, the driver must implement Approach B (Driver Handled) as a fallback if the firmware lacks processing capability.