drivers/crypto/cavium/nitrox/Makefile

File Facts

System

Linux kernel

Corpus path

drivers/crypto/cavium/nitrox/Makefile

Extension

[no extension]

Size

337 bytes

Lines

16

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.

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
obj-$(CONFIG_CRYPTO_DEV_NITROX_CNN55XX) += n5pf.o

n5pf-objs := nitrox_main.o \
	nitrox_isr.o \
	nitrox_lib.o \
	nitrox_hal.o \
	nitrox_reqmgr.o \
	nitrox_algs.o	\
	nitrox_mbx.o	\
	nitrox_skcipher.o \
	nitrox_aead.o

n5pf-$(CONFIG_PCI_IOV) += nitrox_sriov.o
n5pf-$(CONFIG_DEBUG_FS) += nitrox_debugfs.o

Annotation

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