drivers/misc/ibmasm/r_heartbeat.c

File Facts

System

Linux kernel

Corpus path

drivers/misc/ibmasm/r_heartbeat.c

Extension

.c

Size

1945 bytes

Lines

87

Domain

Driver Families

Bucket

drivers/misc

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/sched/signal.h
• ibmasm.h
• dot_command.h

Detected Declarations

• function ibmasm_init_reverse_heartbeat
• function ibmasm_start_reverse_heartbeat
• function ibmasm_stop_reverse_heartbeat

Annotated Snippet

if (signal_pending(current) || rhb->stopped) {
			result = -EINTR;
			break;
		}
	}
	command_put(cmd);
	rhb->stopped = 0;

	return result;
}

void ibmasm_stop_reverse_heartbeat(struct reverse_heartbeat *rhb)
{
	rhb->stopped = 1;
	wake_up_interruptible(&rhb->wait);
}

Annotation

• Immediate include surface: `linux/sched/signal.h`, `ibmasm.h`, `dot_command.h`.
• Detected declarations: `function ibmasm_init_reverse_heartbeat`, `function ibmasm_start_reverse_heartbeat`, `function ibmasm_stop_reverse_heartbeat`.
• Atlas domain: Driver Families / drivers/misc.
• 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.