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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

577 bytes

Lines

17

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct adf_hw_csr_ops
• struct qat_migdev_ops
• struct adf_accel_dev
• struct adf_pfvf_ops

Annotated Snippet

#ifndef ADF_GEN6_SHARED_H_
#define ADF_GEN6_SHARED_H_

struct adf_hw_csr_ops;
struct qat_migdev_ops;
struct adf_accel_dev;
struct adf_pfvf_ops;

void adf_gen6_init_pf_pfvf_ops(struct adf_pfvf_ops *pfvf_ops);
void adf_gen6_init_hw_csr_ops(struct adf_hw_csr_ops *csr_ops);
int adf_gen6_comp_dev_config(struct adf_accel_dev *accel_dev);
int adf_gen6_no_dev_config(struct adf_accel_dev *accel_dev);
void adf_gen6_init_vf_mig_ops(struct qat_migdev_ops *vfmig_ops);
#endif/* ADF_GEN6_SHARED_H_ */

Annotation

• Detected declarations: `struct adf_hw_csr_ops`, `struct qat_migdev_ops`, `struct adf_accel_dev`, `struct adf_pfvf_ops`.
• 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.