drivers/accel/ivpu/ivpu_ms.h

File Facts

System

Linux kernel

Corpus path

drivers/accel/ivpu/ivpu_ms.h

Extension

.h

Size

1009 bytes

Lines

37

Domain

Driver Families

Bucket

drivers/accel

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

Detected Declarations

• struct drm_device
• struct drm_file
• struct ivpu_bo
• struct ivpu_device
• struct ivpu_file_priv
• struct ivpu_ms_instance

Annotated Snippet

struct ivpu_ms_instance {
	struct ivpu_bo *bo;
	struct list_head ms_instance_node;
	u64 mask;
	u64 buff_size;
	u64 active_buff_vpu_addr;
	u64 inactive_buff_vpu_addr;
	void *active_buff_ptr;
	void *inactive_buff_ptr;
	u64 leftover_bytes;
	void *leftover_addr;
};

int ivpu_ms_start_ioctl(struct drm_device *dev, void *data, struct drm_file *file);
int ivpu_ms_stop_ioctl(struct drm_device *dev, void *data, struct drm_file *file);
int ivpu_ms_get_data_ioctl(struct drm_device *dev, void *data, struct drm_file *file);
int ivpu_ms_get_info_ioctl(struct drm_device *dev, void *data, struct drm_file *file);
void ivpu_ms_cleanup(struct ivpu_file_priv *file_priv);
void ivpu_ms_cleanup_all(struct ivpu_device *vdev);

#endif /* __IVPU_MS_H__ */

Annotation

• Immediate include surface: `linux/list.h`.
• Detected declarations: `struct drm_device`, `struct drm_file`, `struct ivpu_bo`, `struct ivpu_device`, `struct ivpu_file_priv`, `struct ivpu_ms_instance`.
• Atlas domain: Driver Families / drivers/accel.
• 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.