arch/sh/cchips/Kconfig
Source file repositories/reference/linux-study-clean/arch/sh/cchips/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/cchips/Kconfig- Extension
[no extension]- Size
- 1041 bytes
- Lines
- 47
- Domain
- Architecture Layer
- Bucket
- arch/sh
- Inferred role
- Architecture Layer: build/configuration rule
- Status
- atlas-only
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
# SPDX-License-Identifier: GPL-2.0
menu "Companion Chips"
config HD6446X_SERIES
bool
choice
prompt "HD6446x options"
depends on HD6446X_SERIES
default HD64461
config HD64461
bool "Hitachi HD64461 companion chip support"
help
The Hitachi HD64461 provides an interface for
the SH7709 CPU, supporting a LCD controller,
CRT color controller, IrDA up to 4 Mbps, and a
PCMCIA controller supporting 2 slots.
More information is available at
<http://semiconductor.hitachi.com/windowsce/superh/sld013.htm>.
Say Y if you want support for the HD64461.
Otherwise, say N.
endchoice
# These will also be split into the Kconfig's below
config HD64461_IRQ
int "HD64461 IRQ"
depends on HD64461
default "52"
help
The default setting of the HD64461 IRQ is 52.
Do not change this unless you know what you are doing.
config HD64461_ENABLER
bool "HD64461 PCMCIA enabler"
depends on HD64461
help
Say Y here if you want to enable PCMCIA support
via the HD64461 companion chip.
Otherwise, say N.
endmenu
Annotation
- Atlas domain: Architecture Layer / arch/sh.
- Implementation status: atlas-only.
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.