include/dt-bindings/iio/adc/mediatek,mt6358-auxadc.h
Source file repositories/reference/linux-study-clean/include/dt-bindings/iio/adc/mediatek,mt6358-auxadc.h
File Facts
- System
- Linux kernel
- Corpus path
include/dt-bindings/iio/adc/mediatek,mt6358-auxadc.h- Extension
.h- Size
- 653 bytes
- Lines
- 23
- 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_MEDIATEK_MT6358_AUXADC_H
#define _DT_BINDINGS_MEDIATEK_MT6358_AUXADC_H
/* ADC Channel Index */
#define MT6358_AUXADC_BATADC 0
#define MT6358_AUXADC_VCDT 1
#define MT6358_AUXADC_BAT_TEMP 2
#define MT6358_AUXADC_CHIP_TEMP 3
#define MT6358_AUXADC_ACCDET 4
#define MT6358_AUXADC_VDCXO 5
#define MT6358_AUXADC_TSX_TEMP 6
#define MT6358_AUXADC_HPOFS_CAL 7
#define MT6358_AUXADC_DCXO_TEMP 8
#define MT6358_AUXADC_VBIF 9
#define MT6358_AUXADC_VCORE_TEMP 10
#define MT6358_AUXADC_VPROC_TEMP 11
#define MT6358_AUXADC_VGPU_TEMP 12
#define MT6358_AUXADC_VBAT 13
#endifAnnotation
- 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.