arch/arm64/boot/dts/exynos/google/gs101-pinctrl.h
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/exynos/google/gs101-pinctrl.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/exynos/google/gs101-pinctrl.h- Extension
.h- Size
- 870 bytes
- Lines
- 34
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
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 __DTS_ARM64_SAMSUNG_EXYNOS_GOOGLE_PINCTRL_GS101_H__
#define __DTS_ARM64_SAMSUNG_EXYNOS_GOOGLE_PINCTRL_GS101_H__
#define GS101_PIN_PULL_NONE 0
#define GS101_PIN_PULL_DOWN 1
#define GS101_PIN_PULL_UP 3
/* Pin function in power down mode */
#define GS101_PIN_PDN_OUT0 0
#define GS101_PIN_PDN_OUT1 1
#define GS101_PIN_PDN_INPUT 2
#define GS101_PIN_PDN_PREV 3
/* GS101 drive strengths */
#define GS101_PIN_DRV_2_5_MA 0
#define GS101_PIN_DRV_5_MA 1
#define GS101_PIN_DRV_7_5_MA 2
#define GS101_PIN_DRV_10_MA 3
#define GS101_PIN_FUNC_INPUT 0
#define GS101_PIN_FUNC_OUTPUT 1
#define GS101_PIN_FUNC_2 2
#define GS101_PIN_FUNC_3 3
#define GS101_PIN_FUNC_EINT 0xf
#endif /* __DTS_ARM64_SAMSUNG_EXYNOS_GOOGLE_PINCTRL_GS101_H__ */Annotation
- Atlas domain: Architecture Layer / arch/arm64.
- 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.