drivers/pinctrl/mediatek/pinctrl-mtmips.h

File Facts

System

Linux kernel

Corpus path

drivers/pinctrl/mediatek/pinctrl-mtmips.h

Extension

.h

Size

1049 bytes

Lines

54

Domain

Driver Families

Bucket

drivers/pinctrl

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct mtmips_pmx_group
• struct mtmips_pmx_func
• struct mtmips_pmx_group

Annotated Snippet

struct mtmips_pmx_func {
	const char *name;
	const char value;

	int pin_first;
	int pin_count;
	int *pins;

	int *groups;
	int group_count;

	int enabled;
};

struct mtmips_pmx_group {
	const char *name;
	int enabled;

	const u32 shift;
	const char mask;
	const char gpio;

	struct mtmips_pmx_func *func;
	int func_count;
};

int mtmips_pinctrl_init(struct platform_device *pdev,
			struct mtmips_pmx_group *data);

#endif

Annotation

• Detected declarations: `struct mtmips_pmx_group`, `struct mtmips_pmx_func`, `struct mtmips_pmx_group`.
• Atlas domain: Driver Families / drivers/pinctrl.
• 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.