drivers/power/reset/brcmstb-reboot.c
Source file repositories/reference/linux-study-clean/drivers/power/reset/brcmstb-reboot.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/power/reset/brcmstb-reboot.c- Extension
.c- Size
- 2861 bytes
- Lines
- 122
- Domain
- Driver Families
- Bucket
- drivers/power
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bitops.hlinux/device.hlinux/errno.hlinux/init.hlinux/io.hlinux/jiffies.hlinux/notifier.hlinux/of_address.hlinux/of_irq.hlinux/of_platform.hlinux/platform_device.hlinux/printk.hlinux/reboot.hlinux/regmap.hlinux/smp.hlinux/mfd/syscon.h
Detected Declarations
struct reset_reg_maskfunction brcmstb_restart_handlerfunction brcmstb_reboot_probefunction brcmstb_reboot_initmodule init brcmstb_reboot_init
Annotated Snippet
subsys_initcall(brcmstb_reboot_init);Annotation
- Immediate include surface: `linux/bitops.h`, `linux/device.h`, `linux/errno.h`, `linux/init.h`, `linux/io.h`, `linux/jiffies.h`, `linux/notifier.h`, `linux/of_address.h`.
- Detected declarations: `struct reset_reg_mask`, `function brcmstb_restart_handler`, `function brcmstb_reboot_probe`, `function brcmstb_reboot_init`, `module init brcmstb_reboot_init`.
- Atlas domain: Driver Families / drivers/power.
- Implementation status: integration 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.