drivers/clk/visconti/reset.h
Source file repositories/reference/linux-study-clean/drivers/clk/visconti/reset.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/clk/visconti/reset.h- Extension
.h- Size
- 880 bytes
- Lines
- 37
- Domain
- Driver Families
- Bucket
- drivers/clk
- 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/reset-controller.h
Detected Declarations
struct visconti_reset_datastruct visconti_reset
Annotated Snippet
struct visconti_reset_data {
u32 rson_offset;
u32 rsoff_offset;
u8 rs_idx;
};
struct visconti_reset {
struct reset_controller_dev rcdev;
struct regmap *regmap;
const struct visconti_reset_data *resets;
spinlock_t *lock;
};
extern const struct reset_control_ops visconti_reset_ops;
int visconti_register_reset_controller(struct device *dev,
struct regmap *regmap,
const struct visconti_reset_data *resets,
unsigned int num_resets,
const struct reset_control_ops *reset_ops,
spinlock_t *lock);
#endif /* _VISCONTI_RESET_H_ */
Annotation
- Immediate include surface: `linux/reset-controller.h`.
- Detected declarations: `struct visconti_reset_data`, `struct visconti_reset`.
- Atlas domain: Driver Families / drivers/clk.
- 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.