drivers/net/wwan/iosm/iosm_ipc_irq.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wwan/iosm/iosm_ipc_irq.h

Extension

.h

Size

729 bytes

Lines

34

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct iosm_pcie

Annotated Snippet

#ifndef IOSM_IPC_IRQ_H
#define IOSM_IPC_IRQ_H

struct iosm_pcie;

/**
 * ipc_doorbell_fire - fire doorbell to CP
 * @ipc_pcie:	Pointer to iosm_pcie
 * @irq_n:	Doorbell type
 * @data:	ipc state
 */
void ipc_doorbell_fire(struct iosm_pcie *ipc_pcie, int irq_n, u32 data);

/**
 * ipc_release_irq - Release the IRQ handler.
 * @ipc_pcie:	Pointer to iosm_pcie struct
 */
void ipc_release_irq(struct iosm_pcie *ipc_pcie);

/**
 * ipc_acquire_irq - acquire IRQ & register IRQ handler.
 * @ipc_pcie:	Pointer to iosm_pcie struct
 *
 * Return: 0 on success and failure value on error
 */
int ipc_acquire_irq(struct iosm_pcie *ipc_pcie);

#endif

Annotation

• Detected declarations: `struct iosm_pcie`.
• 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.