drivers/hid/intel-ish-hid/ishtp-hid.c

File Facts

System

Linux kernel

Corpus path

drivers/hid/intel-ish-hid/ishtp-hid.c

Extension

.c

Size

6542 bytes

Lines

276

Domain

Driver Families

Bucket

drivers/hid

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/hid.h
• linux/intel-ish-client-if.h
• uapi/linux/input.h
• ishtp-hid.h

Detected Declarations

• function Copyright
• function ishtp_hid_start
• function ishtp_hid_stop
• function ishtp_hid_close
• function ishtp_hid_request
• function ishtp_wait_for_response
• function ishtp_hid_wakeup
• function ishtp_hid_probe
• function ishtp_hid_remove

Annotated Snippet

if (client_data->hid_sensor_hubs[i]) {
			data = client_data->hid_sensor_hubs[i]->driver_data;
			hid_destroy_device(client_data->hid_sensor_hubs[i]);
			kfree(data);
			client_data->hid_sensor_hubs[i] = NULL;
		}
	}
}

Annotation

• Immediate include surface: `linux/hid.h`, `linux/intel-ish-client-if.h`, `uapi/linux/input.h`, `ishtp-hid.h`.
• Detected declarations: `function Copyright`, `function ishtp_hid_start`, `function ishtp_hid_stop`, `function ishtp_hid_close`, `function ishtp_hid_request`, `function ishtp_wait_for_response`, `function ishtp_hid_wakeup`, `function ishtp_hid_probe`, `function ishtp_hid_remove`.
• Atlas domain: Driver Families / drivers/hid.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.