drivers/staging/media/ipu7/ipu7-boot.h

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/ipu7/ipu7-boot.h

Extension

.h

Size

769 bytes

Lines

26

Domain

Driver Families

Bucket

drivers/staging

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/types.h

Detected Declarations

• struct ipu7_bus_device
• struct syscom_queue_config

Annotated Snippet

#ifndef IPU7_BOOT_H
#define IPU7_BOOT_H

#include <linux/types.h>

struct ipu7_bus_device;
struct syscom_queue_config;

#define FW_QUEUE_CONFIG_SIZE(num_queues)	\
	(sizeof(struct syscom_queue_config) * (num_queues))

int ipu7_boot_init_boot_config(struct ipu7_bus_device *adev,
			       struct syscom_queue_config *qconfigs,
			       int num_queues, u32 uc_freq,
			       dma_addr_t subsys_config, u8 major);
void ipu7_boot_release_boot_config(struct ipu7_bus_device *adev);
int ipu7_boot_start_fw(const struct ipu7_bus_device *adev);
int ipu7_boot_stop_fw(const struct ipu7_bus_device *adev);
u32 ipu7_boot_get_boot_state(const struct ipu7_bus_device *adev);
#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct ipu7_bus_device`, `struct syscom_queue_config`.
• Atlas domain: Driver Families / drivers/staging.
• 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.