// Request current calibration HIDP_REPORT_ID reportId = 0x01; BYTE buffer[256]; buffer[0] = CMD_READ_CALIBRATION; HidD_SetFeature(hDevice, buffer, sizeof(buffer));
If you are dealing with a specific Silead or Goodix sensor, or need help creating a custom calibration tool, please let me know. Share public link
NTSTATUS WriteCalibrationToRegistry( WDFDEVICE Device, PVOID Data, ULONG Size, ULONG Version) kmdf hid minidriver for touch i2c device calibration
KMDF allows developers to build stable, modern kernel-mode drivers that handle complex hardware interactions—including I2C bus negotiation, interrupt management, and power sequencing—while reducing the risk of system instability compared to older WDM models. However, HID minidrivers are not a standard fit in the KMDF architecture because the HID class driver has conflicting requirements for the driver dispatch table. Microsoft resolves this with a special pass-through driver ( MsHidKmdf.sys ), which resides between the HID class driver and your minidriver, acting as the functional driver while forwarding I/O requests to your filter driver.
: Calibration is often handled via custom Feature Reports within the HID report descriptor or through specialized vendor software that interacts with the minidriver. 2. Common Calibration Issues Microsoft resolves this with a special pass-through driver
The driver pulls raw data from the I2C bus and recalculates the coordinates in real time using a 2D transformation matrix before sending the packet to HIDClass.sys . This is ideal when the touch controller firmware cannot store persistent calibration profiles. Configuration and Registry Settings
Step 3: Apply Transformation inside Data Processing Callback Common Calibration Issues The driver pulls raw data
This technical guide explores how to design, implement, and calibrate a KMDF HID minidriver for I2C touch devices. Architecture of Windows Touch Drivers
WDF_DRIVER_CONFIG config; WDF_DRIVER_CONFIG_INIT(&config, MyTouchCalibEvtDeviceAdd); return WdfDriverCreate(DriverObject, RegistryPath, WDF_NO_OBJECT_ATTRIBUTES, &config, WDF_NO_HANDLE);
[Version] Signature = "$WINDOWS NT$" Class = HIDClass ClassGuid = 745a17a0-74d3-11d0-b6fe-00a0c90f57da Provider = %ProviderName% CatalogFile = TouchMinidriver.cat DriverVer = 05/25/2026,1.0.0.0 [DestinationDirs] DefaultDestDir = 13 [Manufacturer] %ManufacturerName% = TouchDevice, NTamd64 [TouchDevice.NTamd64] %DeviceDesc% = TouchMinidriver_Install, ACPI\VEN_EXTC&DEV_0001 [TouchMinidriver_Install.NT] CopyFiles = TouchMinidriver_CopyFiles [TouchMinidriver_CopyFiles] TouchMinidriver.sys [TouchMinidriver_Install.NT.HW] AddReg = TouchMinidriver_HW_AddReg [TouchMinidriver_HW_AddReg] HKR,,"UpperFilters",0x00010000,"MSHWDVK" ; Enable Windows integrated touch calibration UI HKR,,"TouchCalibrationEnabled",0x00010001,1 Use code with caution. Registry Paths for Calibration Data