include/dt-bindings/power/nvidia,tegra264-bpmp.h
Source file repositories/reference/linux-study-clean/include/dt-bindings/power/nvidia,tegra264-bpmp.h
File Facts
- System
- Linux kernel
- Corpus path
include/dt-bindings/power/nvidia,tegra264-bpmp.h- Extension
.h- Size
- 889 bytes
- Lines
- 25
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: implementation source
- Status
- source implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef DT_BINDINGS_POWER_NVIDIA_TEGRA264_BPMP_H
#define DT_BINDINGS_POWER_NVIDIA_TEGRA264_BPMP_H
#define TEGRA264_POWER_DOMAIN_DISP 1
#define TEGRA264_POWER_DOMAIN_AUD 2
/* reserved 3:9 */
#define TEGRA264_POWER_DOMAIN_XUSB_SS 10
#define TEGRA264_POWER_DOMAIN_XUSB_DEV 11
#define TEGRA264_POWER_DOMAIN_XUSB_HOST 12
#define TEGRA264_POWER_DOMAIN_MGBE0 13
#define TEGRA264_POWER_DOMAIN_MGBE1 14
#define TEGRA264_POWER_DOMAIN_MGBE2 15
#define TEGRA264_POWER_DOMAIN_MGBE3 16
#define TEGRA264_POWER_DOMAIN_VI 17
#define TEGRA264_POWER_DOMAIN_VIC 18
#define TEGRA264_POWER_DOMAIN_ISP0 19
#define TEGRA264_POWER_DOMAIN_ISP1 20
#define TEGRA264_POWER_DOMAIN_PVA0 21
#define TEGRA264_POWER_DOMAIN_GPU 22
#endif /* DT_BINDINGS_POWER_NVIDIA_TEGRA264_BPMP_H */Annotation
- Atlas domain: Repository Root And Misc / include.
- 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.