include/dt-bindings/reset/mediatek,mt8196-resets.h
Source file repositories/reference/linux-study-clean/include/dt-bindings/reset/mediatek,mt8196-resets.h
File Facts
- System
- Linux kernel
- Corpus path
include/dt-bindings/reset/mediatek,mt8196-resets.h- Extension
.h- Size
- 783 bytes
- Lines
- 27
- 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_RESET_CONTROLLER_MT8196
#define _DT_BINDINGS_RESET_CONTROLLER_MT8196
/* PEXTP0 resets */
#define MT8196_PEXTP0_RST0_PCIE0_MAC 0
#define MT8196_PEXTP0_RST0_PCIE0_PHY 1
/* PEXTP1 resets */
#define MT8196_PEXTP1_RST0_PCIE1_MAC 0
#define MT8196_PEXTP1_RST0_PCIE1_PHY 1
#define MT8196_PEXTP1_RST0_PCIE2_MAC 2
#define MT8196_PEXTP1_RST0_PCIE2_PHY 3
/* UFS resets */
#define MT8196_UFSAO_RST0_UFS_MPHY 0
#define MT8196_UFSAO_RST1_UFS_UNIPRO 1
#define MT8196_UFSAO_RST1_UFS_CRYPTO 2
#define MT8196_UFSAO_RST1_UFSHCI 3
#endif /* _DT_BINDINGS_RESET_CONTROLLER_MT8196 */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.