drivers/accel/ivpu/Kconfig

Source file repositories/reference/linux-study-clean/drivers/accel/ivpu/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/accel/ivpu/Kconfig
Extension: [no extension]
Size: 868 bytes
Lines: 28
Domain: Driver Families
Bucket: drivers/accel
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.
Touches IRQ or DMA behavior; this matters for the representative real-device path.

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

config DRM_ACCEL_IVPU
	tristate "Intel NPU (Neural Processing Unit)"
	depends on DRM_ACCEL
	depends on X86_64 && !UML
	depends on PCI && PCI_MSI
	select FW_LOADER
	select DRM_GEM_SHMEM_HELPER
	select GENERIC_ALLOCATOR
	select WANT_DEV_COREDUMP
	help
	  Choose this option if you have a system with an 14th generation
	  Intel CPU (Meteor Lake) or newer. Intel NPU (formerly called Intel VPU)
	  is a CPU-integrated inference accelerator for Computer Vision
	  and Deep Learning applications.

	  If "M" is selected, the module will be called intel_vpu.

config DRM_ACCEL_IVPU_DEBUG
	bool "Intel NPU debug mode"
	depends on DRM_ACCEL_IVPU
	help
	  Choose this option to enable additional
	  debug features for the Intel NPU driver:
	  - Always print debug messages regardless of dyndbg config,
	  - Enable unsafe module params.

Annotation

Atlas domain: Driver Families / drivers/accel.
Implementation status: atlas-only.
IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.