drivers/staging/greybus/Kconfig
Source file repositories/reference/linux-study-clean/drivers/staging/greybus/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/greybus/Kconfig- Extension
[no extension]- Size
- 6347 bytes
- Lines
- 217
- Domain
- Driver Families
- Bucket
- drivers/staging
- 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
if GREYBUS
config GREYBUS_AUDIO
tristate "Greybus Audio Class driver"
depends on SOUND && SND_SOC
help
Select this option if you have a device that follows the
Greybus Audio Class specification.
To compile this code as a module, chose M here: the module
will be called gb-audio.ko
config GREYBUS_AUDIO_APB_CODEC
tristate "Greybus APBridge Audio codec driver"
depends on SND_SOC && GREYBUS_AUDIO
help
Select this option if you have a Toshiba APB device that has I2S
ports and acts as a Greybus "Dummy codec". This device is a
bridge from an APB-I2S port to a Unipro network.
To compile this code as a module, chose M here: the module
will be called gb-audio-codec.ko
config GREYBUS_BOOTROM
tristate "Greybus Bootrom Class driver"
help
Select this option if you have a device that follows the
Greybus Bootrom Class specification.
To compile this code as a module, chose M here: the module
will be called gb-bootrom.ko
config GREYBUS_CAMERA
tristate "Greybus Camera Class driver"
depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN
help
Select this option if you have a device that follows the
Greybus Camera Class specification.
To compile this code as a module, chose M here: the module
will be called gb-camera.ko
config GREYBUS_FIRMWARE
tristate "Greybus Firmware Download Class driver"
depends on SPI
help
Select this option if you have a device that follows the
Greybus Firmware Download Class specification.
To compile this code as a module, chose M here: the module
will be called gb-firmware.ko
config GREYBUS_HID
tristate "Greybus HID Class driver"
depends on HID && INPUT
help
Select this option if you have a device that follows the
Greybus HID Class specification.
To compile this code as a module, chose M here: the module
will be called gb-hid.ko
config GREYBUS_LIGHT
tristate "Greybus LED Class driver"
depends on LEDS_CLASS_FLASH
help
Select this option if you have a device that follows the
Greybus LED Class specification.
Annotation
- Atlas domain: Driver Families / drivers/staging.
- 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.