drivers/media/platform/amd/isp4/Kconfig
Source file repositories/reference/linux-study-clean/drivers/media/platform/amd/isp4/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/platform/amd/isp4/Kconfig- Extension
[no extension]- Size
- 551 bytes
- Lines
- 18
- Domain
- Driver Families
- Bucket
- drivers/media
- 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 VIDEO_AMD_ISP4_CAPTURE
tristate "AMD ISP4 and camera driver"
depends on DRM_AMDGPU && DRM_AMD_ISP
depends on HAS_DMA
depends on VIDEO_DEV
select VIDEOBUF2_CORE
select VIDEOBUF2_MEMOPS
select VIDEOBUF2_V4L2
select VIDEOBUF2_VMALLOC
select VIDEO_V4L2_SUBDEV_API
help
This is support for AMD ISP4 and camera subsystem driver.
Say Y here to enable the ISP4 and camera device for video capture.
To compile this driver as a module, choose M here. The module will
be called amd_isp4_capture.
Annotation
- Atlas domain: Driver Families / drivers/media.
- 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.