drivers/mcb/Kconfig
Source file repositories/reference/linux-study-clean/drivers/mcb/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/mcb/Kconfig- Extension
[no extension]- Size
- 1000 bytes
- Lines
- 42
- Domain
- Driver Families
- Bucket
- drivers/mcb
- 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
#
# MEN Chameleon Bus (MCB) support
#
menuconfig MCB
tristate "MCB support"
default n
depends on HAS_IOMEM
help
The MCB (MEN Chameleon Bus) is a Bus specific to MEN Mikroelektronik
FPGA based devices. It is used to identify MCB based IP-Cores within
an FPGA and provide the necessary framework for instantiating drivers
for these devices.
If build as a module, the module is called mcb.ko
if MCB
config MCB_PCI
tristate "PCI based MCB carrier"
default n
depends on PCI
help
This is a MCB carrier on a PCI device. Both PCI attached on-board
FPGAs as well as CompactPCI attached MCB FPGAs are supported with
this driver.
If build as a module, the module is called mcb-pci.ko
config MCB_LPC
tristate "LPC (non PCI) based MCB carrier"
default n
help
This is a MCB carrier on a LPC or non PCI device.
If build as a module, the module is called mcb-lpc.ko
endif # MCB
Annotation
- Atlas domain: Driver Families / drivers/mcb.
- 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.