drivers/accel/rocket/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/accel/rocket/Kconfig
Extension: [no extension]
Size: 781 bytes
Lines: 25
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.

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_ROCKET
	tristate "Rocket (support for Rockchip NPUs)"
	depends on DRM_ACCEL
	depends on (ARCH_ROCKCHIP && ARM64) || COMPILE_TEST
	depends on ROCKCHIP_IOMMU || COMPILE_TEST
	depends on MMU
	select DRM_SCHED
	select DRM_GEM_SHMEM_HELPER
	help
	  Choose this option if you have a Rockchip SoC that contains a
	  compatible Neural Processing Unit (NPU), such as the RK3588. Called by
	  Rockchip either RKNN or RKNPU, it accelerates inference of neural
	  networks.

	  The interface exposed to userspace is described in
	  include/uapi/drm/rocket_accel.h and is used by the Rocket userspace
	  driver in Mesa3D.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called rocket.

Annotation

Atlas domain: Driver Families / drivers/accel.
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.