drivers/reset/amlogic/reset-meson.h

File Facts

System

Linux kernel

Corpus path

drivers/reset/amlogic/reset-meson.h

Extension

.h

Size

737 bytes

Lines

29

Domain

Driver Families

Bucket

drivers/reset

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/module.h
• linux/regmap.h
• linux/reset-controller.h

Detected Declarations

• struct meson_reset_param

Annotated Snippet

struct meson_reset_param {
	const struct reset_control_ops *reset_ops;
	unsigned int reset_num;
	unsigned int reset_offset;
	unsigned int level_offset;
	bool level_low_reset;
};

int meson_reset_controller_register(struct device *dev, struct regmap *map,
				    const struct meson_reset_param *param);

extern const struct reset_control_ops meson_reset_ops;
extern const struct reset_control_ops meson_reset_toggle_ops;

#endif /* __MESON_RESET_H */

Annotation

• Immediate include surface: `linux/module.h`, `linux/regmap.h`, `linux/reset-controller.h`.
• Detected declarations: `struct meson_reset_param`.
• Atlas domain: Driver Families / drivers/reset.
• 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.