drivers/scsi/isci/unsolicited_frame_control.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/isci/unsolicited_frame_control.c

Extension

.c

Size

7466 bytes

Lines

212

Domain

Driver Families

Bucket

drivers/scsi

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

• host.h
• unsolicited_frame_control.h
• registers.h

Detected Declarations

• function sci_unsolicited_frame_control_construct
• function sci_unsolicited_frame_control_get_header
• function sci_unsolicited_frame_control_get_buffer
• function sci_unsolicited_frame_control_release_frame

Annotated Snippet

if (frame_get+1 == SCU_MAX_UNSOLICITED_FRAMES-1) {
			frame_cycle ^= SCU_MAX_UNSOLICITED_FRAMES;
			frame_get = 0;
		} else
			frame_get++;
	}

	uf_control->get = SCU_UFQGP_GEN_BIT(ENABLE_BIT) | frame_cycle | frame_get;

	return true;
}

Annotation

• Immediate include surface: `host.h`, `unsolicited_frame_control.h`, `registers.h`.
• Detected declarations: `function sci_unsolicited_frame_control_construct`, `function sci_unsolicited_frame_control_get_header`, `function sci_unsolicited_frame_control_get_buffer`, `function sci_unsolicited_frame_control_release_frame`.
• Atlas domain: Driver Families / drivers/scsi.
• 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.