drivers/misc/keba/Kconfig
Source file repositories/reference/linux-study-clean/drivers/misc/keba/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/misc/keba/Kconfig- Extension
[no extension]- Size
- 836 bytes
- Lines
- 27
- 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
config KEBA_CP500
tristate "KEBA CP500 system FPGA support"
depends on X86_64 || ARM64 || COMPILE_TEST
depends on PCI
depends on I2C
select AUXILIARY_BUS
help
This driver supports the KEBA CP500 system FPGA, which is used in
KEBA CP500 devices. It registers all sub devices present on the CP500
system FPGA as separate devices. A driver is needed for each sub
device.
This driver can also be built as a module. If so, the module will be
called cp500.
config KEBA_LAN9252
tristate "KEBA CP500 LAN9252 configuration"
depends on SPI
depends on KEBA_CP500 || COMPILE_TEST
help
This driver is used for updating the configuration of the LAN9252
controller on KEBA CP500 devices.
This driver can also be built as a module. If so, the module will be
called lan9252.
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.