arch/sh/include/mach-common/mach/secureedge5410.h
Source file repositories/reference/linux-study-clean/arch/sh/include/mach-common/mach/secureedge5410.h
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/include/mach-common/mach/secureedge5410.h- Extension
.h- Size
- 1566 bytes
- Lines
- 48
- Domain
- Architecture Layer
- Bucket
- arch/sh
- 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
asm/io_generic.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _ASM_SH_IO_SNAPGEAR_H
#define _ASM_SH_IO_SNAPGEAR_H
#define __IO_PREFIX snapgear
#include <asm/io_generic.h>
/*
* We need to remember what was written to the ioport as some bits
* are shared with other functions and you cannot read back what was
* written :-|
*
* Bit Read Write
* -----------------------------------------------
* D0 DCD on ttySC1 power
* D1 Reset Switch heatbeat
* D2 ttySC0 CTS (7100) LAN
* D3 - WAN
* D4 ttySC0 DCD (7100) CONSOLE
* D5 - ONLINE
* D6 - VPN
* D7 - DTR on ttySC1
* D8 - ttySC0 RTS (7100)
* D9 - ttySC0 DTR (7100)
* D10 - RTC SCLK
* D11 RTC DATA RTC DATA
* D12 - RTS RESET
*/
#define SECUREEDGE_IOPORT_ADDR ((volatile short *) 0xb0000000)
extern unsigned short secureedge5410_ioport;
#define SECUREEDGE_WRITE_IOPORT(val, mask) (*SECUREEDGE_IOPORT_ADDR = \
(secureedge5410_ioport = \
((secureedge5410_ioport & ~(mask)) | ((val) & (mask)))))
#define SECUREEDGE_READ_IOPORT() \
((*SECUREEDGE_IOPORT_ADDR&0x0817) | (secureedge5410_ioport&~0x0817))
#endif /* _ASM_SH_IO_SNAPGEAR_H */
Annotation
- Immediate include surface: `asm/io_generic.h`.
- Atlas domain: Architecture Layer / arch/sh.
- 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.