arch/arm64/boot/dts/renesas/rzg3s-smarc-switches.h
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/renesas/rzg3s-smarc-switches.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/renesas/rzg3s-smarc-switches.h- Extension
.h- Size
- 962 bytes
- Lines
- 41
- 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 __RZG3S_SMARC_SWITCHES_H__
#define __RZG3S_SMARC_SWITCHES_H__
/*
* On-board switches' states:
* @SW_OFF: switch's state is OFF
* @SW_ON: switch's state is ON
*/
#define SW_OFF 0
#define SW_ON 1
/*
* SW_CONFIG[x] switches' states:
* @SW_CONFIG2:
* SW_OFF - SD0 is connected to eMMC
* SW_ON - SD0 is connected to uSD0 card
* @SW_CONFIG3:
* SW_OFF - SD2 is connected to SoC
* SW_ON - SCIF1, SSI0, IRQ0, IRQ1 connected to SoC
*/
#define SW_CONFIG2 SW_OFF
#define SW_CONFIG3 SW_ON
/*
* SW_OPT_MUX[x] switches' states:
* @SW_OPT_MUX4:
* SW_OFF - The SMARC SER0 signals are routed to M.2 Key E UART
* SW_ON - The SMARC SER0 signals are routed to PMOD1
*/
#define SW_OPT_MUX4 SW_ON
#endif /* __RZG3S_SMARC_SWITCHES_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.