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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

684 bytes

Lines

28

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/bitops.h
• linux/atomic.h

Detected Declarations

• struct adf_accel_dev

Annotated Snippet

#ifndef ADF_RAS_H
#define ADF_RAS_H

#include <linux/bitops.h>
#include <linux/atomic.h>

struct adf_accel_dev;

void adf_sysfs_start_ras(struct adf_accel_dev *accel_dev);
void adf_sysfs_stop_ras(struct adf_accel_dev *accel_dev);

#define ADF_RAS_ERR_CTR_READ(ras_errors, ERR) \
	atomic_read(&(ras_errors).counter[ERR])

#define ADF_RAS_ERR_CTR_CLEAR(ras_errors) \
	do { \
		for (int err = 0; err < ADF_RAS_ERRORS; ++err) \
			atomic_set(&(ras_errors).counter[err], 0); \
	} while (0)

#define ADF_RAS_ERR_CTR_INC(ras_errors, ERR) \
	atomic_inc(&(ras_errors).counter[ERR])

#endif /* ADF_RAS_H */

Annotation

• Immediate include surface: `linux/bitops.h`, `linux/atomic.h`.
• Detected declarations: `struct adf_accel_dev`.
• Atlas domain: Driver Families / drivers/crypto.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.