drivers/crypto/cavium/nitrox/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/crypto/cavium/nitrox/Kconfig

Extension

[no extension]

Size

520 bytes

Lines

22

Domain

Driver Families

Bucket

drivers/crypto

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
#
# Cavium NITROX Crypto Device configuration
#
config CRYPTO_DEV_NITROX
	tristate
	select CRYPTO_SKCIPHER
	select CRYPTO_AES
	select CRYPTO_LIB_DES
	select FW_LOADER

config CRYPTO_DEV_NITROX_CNN55XX
	tristate "Support for Cavium CNN55XX driver"
	depends on PCI_MSI && 64BIT
	select CRYPTO_DEV_NITROX
	help
	  Support for Cavium NITROX family CNN55XX driver
	  for accelerating crypto workloads.

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

Annotation

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