drivers/net/wwan/iosm/iosm_ipc_irq.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wwan/iosm/iosm_ipc_irq.c

Extension

.c

Size

2137 bytes

Lines

91

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• iosm_ipc_pcie.h
• iosm_ipc_protocol.h

Detected Declarations

• function Copyright
• function ipc_doorbell_fire
• function ipc_msi_interrupt
• function ipc_release_irq
• function ipc_acquire_irq

Annotated Snippet

if (rc) {
			dev_err(ipc_pcie->dev, "unable to grab IRQ, rc=%d", rc);
			ipc_pcie->nvec = i;
			ipc_release_irq(ipc_pcie);
			goto error;
		}
	}

error:
	return rc;
}

Annotation

• Immediate include surface: `iosm_ipc_pcie.h`, `iosm_ipc_protocol.h`.
• Detected declarations: `function Copyright`, `function ipc_doorbell_fire`, `function ipc_msi_interrupt`, `function ipc_release_irq`, `function ipc_acquire_irq`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.