drivers/input/touchscreen/goodix_berlin.h

File Facts

System

Linux kernel

Corpus path

drivers/input/touchscreen/goodix_berlin.h

Extension

.h

Size

941 bytes

Lines

40

Domain

Driver Families

Bucket

drivers/input

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/pm.h

Detected Declarations

• struct goodix_berlin_ic_data
• struct device
• struct input_id
• struct regmap

Annotated Snippet

struct goodix_berlin_ic_data {
	int fw_version_info_addr;
	int ic_info_addr;
	ssize_t read_dummy_len;
	ssize_t read_prefix_len;
};

struct device;
struct input_id;
struct regmap;

int goodix_berlin_probe(struct device *dev, int irq, const struct input_id *id,
			struct regmap *regmap,
			const struct goodix_berlin_ic_data *ic_data);

extern const struct dev_pm_ops goodix_berlin_pm_ops;
extern const struct attribute_group *goodix_berlin_groups[];

#endif

Annotation

• Immediate include surface: `linux/pm.h`.
• Detected declarations: `struct goodix_berlin_ic_data`, `struct device`, `struct input_id`, `struct regmap`.
• Atlas domain: Driver Families / drivers/input.
• 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.