drivers/misc/bcm-vk/Kconfig

Source file repositories/reference/linux-study-clean/drivers/misc/bcm-vk/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/misc/bcm-vk/Kconfig
Extension: [no extension]
Size: 919 bytes
Lines: 30
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.
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
#
# Broadcom VK device
#
config BCM_VK
	tristate "Support for Broadcom VK Accelerators"
	depends on PCI_MSI
	help
	  Select this option to enable support for Broadcom
	  VK Accelerators.  VK is used for performing
	  multiple specific offload processing tasks in parallel.
	  Such offload tasks assist in such operations as video
	  transcoding, compression, and crypto tasks.
	  This driver enables userspace programs to access these
	  accelerators via /dev/bcm-vk.N devices.

	  If unsure, say N.

config BCM_VK_TTY
	bool "Enable tty ports on a Broadcom VK Accelerator device"
	depends on TTY
	depends on BCM_VK
	help
	  Select this option to enable tty support to allow console
	  access to Broadcom VK Accelerator cards from host.

	  Device node will in the form /dev/bcm-vk.x_ttyVKy where:
	  x is the instance of the VK card
	  y is the tty device number on the VK card.

Annotation

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