drivers/input/rmi4/rmi_driver.c

File Facts

System

Linux kernel

Corpus path

drivers/input/rmi4/rmi_driver.c

Extension

.c

Size

31894 bytes

Lines

1285

Domain

Driver Families

Bucket

drivers/input

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/bitmap.h
• linux/delay.h
• linux/fs.h
• linux/irq.h
• linux/pm.h
• linux/slab.h
• linux/of.h
• linux/irqdomain.h
• uapi/linux/input.h
• linux/rmi.h
• linux/export.h
• rmi_bus.h
• rmi_driver.h

Detected Declarations

• function Copyright
• function reset_one_function
• function configure_one_function
• function rmi_driver_process_reset_requests
• function list_for_each_entry
• function rmi_driver_process_config_requests
• function list_for_each_entry
• function rmi_process_interrupt_requests
• function rmi_set_attn_data
• function rmi_irq_fn
• function rmi_irq_init
• function list_for_each_entry
• function suspend_one_function
• function rmi_suspend_functions
• function list_for_each_entry
• function resume_one_function
• function rmi_resume_functions
• function list_for_each_entry
• function rmi_enable_sensor
• function rmi_driver_set_input_params
• function rmi_driver_set_input_name
• function rmi_driver_set_irq_bits
• function rmi_driver_clear_irq_bits
• function rmi_driver_reset_handler
• function rmi_read_pdt_entry
• function rmi_driver_copy_pdt_to_fd
• function rmi_scan_pdt_page
• function rmi_scan_pdt
• function rmi_read_register_desc
• function rmi_register_desc_calc_size
• function rmi_register_desc_calc_reg_offset
• function rmi_register_desc_has_subpacket
• function rmi_check_bootloader_mode
• function rmi_count_irqs
• function rmi_initial_reset
• function rmi_create_function
• function rmi_enable_irq
• function rmi_disable_irq
• function rmi_driver_suspend
• function rmi_driver_resume
• function rmi_driver_remove
• function rmi_driver_of_probe
• function rmi_driver_of_probe
• function rmi_probe_interrupts
• function rmi_init_functions
• function rmi_driver_probe
• function rmi_is_physical_driver
• function rmi_register_physical_driver

Annotated Snippet

bool rmi_is_physical_driver(const struct device_driver *drv)
{
	return drv == &rmi_physical_driver.driver;
}

int __init rmi_register_physical_driver(void)
{
	int error;

	error = driver_register(&rmi_physical_driver.driver);
	if (error) {
		pr_err("%s: driver register failed, code=%d.\n", __func__,
		       error);
		return error;
	}

	return 0;
}

void __exit rmi_unregister_physical_driver(void)
{
	driver_unregister(&rmi_physical_driver.driver);
}

Annotation

• Immediate include surface: `linux/bitmap.h`, `linux/delay.h`, `linux/fs.h`, `linux/irq.h`, `linux/pm.h`, `linux/slab.h`, `linux/of.h`, `linux/irqdomain.h`.
• Detected declarations: `function Copyright`, `function reset_one_function`, `function configure_one_function`, `function rmi_driver_process_reset_requests`, `function list_for_each_entry`, `function rmi_driver_process_config_requests`, `function list_for_each_entry`, `function rmi_process_interrupt_requests`, `function rmi_set_attn_data`, `function rmi_irq_fn`.
• Atlas domain: Driver Families / drivers/input.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.