drivers/sh/intc/Kconfig
Source file repositories/reference/linux-study-clean/drivers/sh/intc/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/sh/intc/Kconfig- Extension
[no extension]- Size
- 1195 bytes
- Lines
- 45
- Domain
- Driver Families
- Bucket
- drivers/sh
- Inferred role
- Driver Families: build/configuration rule
- Status
- atlas-only
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
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-only
config SH_INTC
bool
select IRQ_DOMAIN
if SH_INTC
comment "Interrupt controller options"
config INTC_USERIMASK
bool "Userspace interrupt masking support"
depends on (SUPERH && CPU_SH4A) || COMPILE_TEST
help
This enables support for hardware-assisted userspace hardirq
masking.
SH-4A and newer interrupt blocks all support a special shadowed
page with all non-masking registers obscured when mapped in to
userspace. This is primarily for use by userspace device
drivers that are using special priority levels.
If in doubt, say N.
config INTC_BALANCING
bool "Hardware IRQ balancing support"
depends on SMP && SUPERH && CPU_SHX3
help
This enables support for IRQ auto-distribution mode on SH-X3
SMP parts. All of the balancing and CPU wakeup decisions are
taken care of automatically by hardware for distributed
vectors.
If in doubt, say N.
config INTC_MAPPING_DEBUG
bool "Expose IRQ to per-controller id mapping via debugfs"
depends on DEBUG_FS
help
This will create a debugfs entry for showing the relationship
between system IRQs and the per-controller id tables.
If in doubt, say N.
endif
Annotation
- Atlas domain: Driver Families / drivers/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.