drivers/misc/c2port/Kconfig
Source file repositories/reference/linux-study-clean/drivers/misc/c2port/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/misc/c2port/Kconfig- Extension
[no extension]- Size
- 888 bytes
- Lines
- 34
- Domain
- Driver Families
- Bucket
- drivers/misc
- 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
#
# C2 port devices
#
menuconfig C2PORT
tristate "Silicon Labs C2 port support"
help
This option enables support for Silicon Labs C2 port used to
program Silicon micro controller chips (and other 8051 compatible).
If your board have no such micro controllers you don't need this
interface at all.
To compile this driver as a module, choose M here: the module will
be called c2port_core. Note that you also need a client module
usually called c2port-*.
If you are not sure, say N here.
if C2PORT
config C2PORT_DURAMAR_2150
tristate "C2 port support for Eurotech's Duramar 2150"
depends on X86
help
This option enables C2 support for the Eurotech's Duramar 2150
on board micro controller.
To compile this driver as a module, choose M here: the module will
be called c2port-duramar2150.
endif # C2PORT
Annotation
- Atlas domain: Driver Families / drivers/misc.
- 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.