Dennis HilkLinux diagnosticsDE

Input & other peripherals

HID over I2C touchpad and touchscreen transport

An internal I2C HID path can expose touch input without any USB device entry.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

This is a documented transport family with no invented PCI or USB pair. I2C/ACPI descriptions, the HID device and input capabilities are separate evidence; a missing lsusb entry is expected for an I2C-only device.

This is an explicit class, transport or driver-context profile. It is not an exact numeric product match.

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

i2c_hid provides transport initialization and registers a HID device, which can then bind hid_multitouch or another HID interpreter. Firmware-described interrupts and power sequencing are part of the transport path, not a USB driver selection.

  • i2c_hid — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

No external firmware filename was established in the checked driver path. This does not describe firmware stored inside the device.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Inspect registered I2C devices

ls -l /sys/bus/i2c/devices/

List registered devices without sudo. This is not an active I2C bus scan and sends no probing transactions. Use ancestry to associate the HID/input function with an existing firmware-described device.

Inspect HID-layer bindings

ls -l /sys/bus/hid/devices/*/driver

Read HID driver symlinks without sudo. Correlate the HID path with its parent USB/I2C device before assigning a driver; a generic HID driver and a transport driver describe different layers.

Inspect input handlers and capabilities

cat /proc/bus/input/devices

This reads the input registry without sudo and does not capture keystrokes. Names, handlers and bus information help associate event nodes with hardware; a device entry alone does not prove desktop routing or correct calibration.

Limitations & related issues

Transport-family context does not identify a touchpad vendor or promise all gestures. An ACPI-described device can fail before any input node exists; adding a USB VID/PID would not resolve that layer.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.