drivers/mfd/ucb1x00-ts.c

File Facts

System

Linux kernel

Corpus path

drivers/mfd/ucb1x00-ts.c

Extension

.c

Size

10927 bytes

Lines

446

Domain

Driver Families

Bucket

drivers/mfd

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• 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/module.h
• linux/moduleparam.h
• linux/init.h
• linux/interrupt.h
• linux/sched.h
• linux/spinlock.h
• linux/completion.h
• linux/delay.h
• linux/string.h
• linux/input.h
• linux/device.h
• linux/freezer.h
• linux/slab.h
• linux/kthread.h
• linux/mfd/ucb1x00.h
• mach/collie.h
• asm/mach-types.h

Detected Declarations

• struct ucb1x00_ts
• function ucb1x00_ts_evt_add
• function ucb1x00_ts_event_release
• function ucb1x00_ts_mode_int
• function ucb1x00_ts_read_pressure
• function ucb1x00_ts_read_xpos
• function ucb1x00_ts_read_ypos
• function ucb1x00_ts_read_xres
• function ucb1x00_ts_read_yres
• function ucb1x00_ts_pen_down
• function ucb1x00_thread
• function ucb1x00_ts_irq
• function ucb1x00_ts_open
• function ucb1x00_ts_close
• function ucb1x00_ts_add
• function ucb1x00_ts_remove
• function ucb1x00_ts_init
• function ucb1x00_ts_exit
• module init ucb1x00_ts_init

Annotated Snippet

module_init(ucb1x00_ts_init);
module_exit(ucb1x00_ts_exit);

MODULE_AUTHOR("Russell King <rmk@arm.linux.org.uk>");
MODULE_DESCRIPTION("UCB1x00 touchscreen driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/init.h`, `linux/interrupt.h`, `linux/sched.h`, `linux/spinlock.h`, `linux/completion.h`, `linux/delay.h`.
• Detected declarations: `struct ucb1x00_ts`, `function ucb1x00_ts_evt_add`, `function ucb1x00_ts_event_release`, `function ucb1x00_ts_mode_int`, `function ucb1x00_ts_read_pressure`, `function ucb1x00_ts_read_xpos`, `function ucb1x00_ts_read_ypos`, `function ucb1x00_ts_read_xres`, `function ucb1x00_ts_read_yres`, `function ucb1x00_ts_pen_down`.
• Atlas domain: Driver Families / drivers/mfd.
• Implementation status: integration 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.