drivers/net/ethernet/qlogic/qed/qed_selftest.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/qlogic/qed/qed_selftest.h

Extension

.h

Size

978 bytes

Lines

54

Domain

Driver Families

Bucket

drivers/net

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

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _QED_SELFTEST_API_H
#define _QED_SELFTEST_API_H
#include <linux/types.h>

/**
 * qed_selftest_memory(): Perform memory test.
 *
 * @cdev: Qed dev pointer.
 *
 * Return: Int.
 */
int qed_selftest_memory(struct qed_dev *cdev);

/**
 * qed_selftest_interrupt(): Perform interrupt test.
 *
 * @cdev: Qed dev pointer.
 *
 * Return: Int.
 */
int qed_selftest_interrupt(struct qed_dev *cdev);

/**
 * qed_selftest_register(): Perform register test.
 *
 * @cdev: Qed dev pointer.
 *
 * Return: Int.
 */
int qed_selftest_register(struct qed_dev *cdev);

/**
 * qed_selftest_clock(): Perform clock test.
 *
 * @cdev: Qed dev pointer.
 *
 * Return: Int.
 */
int qed_selftest_clock(struct qed_dev *cdev);

/**
 * qed_selftest_nvram(): Perform nvram test.
 *
 * @cdev: Qed dev pointer.
 *
 * Return: Int.
 */
int qed_selftest_nvram(struct qed_dev *cdev);

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Atlas domain: Driver Families / drivers/net.
• 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.