drivers/crypto/intel/qat/qat_common/adf_kpt.h

File Facts

System

Linux kernel

Corpus path

drivers/crypto/intel/qat/qat_common/adf_kpt.h

Extension

.h

Size

706 bytes

Lines

30

Domain

Driver Families

Bucket

drivers/crypto

Inferred role

Driver Families: implementation source

Status

source implementation candidate

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct adf_accel_dev
• struct adf_kpt_interface_data
• struct adf_kpt_hw_data

Annotated Snippet

struct adf_kpt_interface_data {
	bool enable;
	bool swk_shared;
	unsigned int swk_cnt_per_fn;
	unsigned int swk_cnt_per_pasid;
	unsigned int swk_max_ttl;
};

struct adf_kpt_hw_data {
	unsigned int max_swk_cnt_per_fn_pasid;
	unsigned int max_swk_ttl;
	struct adf_kpt_interface_data user_input;
};

int adf_enable_kpt(struct adf_accel_dev *accel_dev);

#endif /* ADF_KPT_H_ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct adf_accel_dev`, `struct adf_kpt_interface_data`, `struct adf_kpt_hw_data`.
• Atlas domain: Driver Families / drivers/crypto.
• Implementation status: source implementation candidate.

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.