drivers/remoteproc/pru_rproc.h

File Facts

System

Linux kernel

Corpus path

drivers/remoteproc/pru_rproc.h

Extension

.h

Size

1382 bytes

Lines

47

Domain

Driver Families

Bucket

drivers/remoteproc

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 pruss_int_map
• struct pru_irq_rsc

Annotated Snippet

struct pruss_int_map {
	u8 event;
	u8 chnl;
	u8 host;
};

/**
 * struct pru_irq_rsc - PRU firmware section header for IRQ data
 * @type: resource type
 * @num_evts: number of described events
 * @pru_intc_map: PRU interrupt routing description
 *
 * The PRU firmware blob can contain optional .pru_irq_map ELF section, which
 * provides the PRUSS interrupt mapping description. The pru_irq_rsc struct
 * describes resource entry format.
 */
struct pru_irq_rsc {
	u8 type;
	u8 num_evts;
	struct pruss_int_map pru_intc_map[];
} __packed;

#endif	/* _PRU_RPROC_H_ */

Annotation

• Detected declarations: `struct pruss_int_map`, `struct pru_irq_rsc`.
• Atlas domain: Driver Families / drivers/remoteproc.
• 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.