drivers/accel/ivpu/ivpu_coredump.h

File Facts

System

Linux kernel

Corpus path

drivers/accel/ivpu/ivpu_coredump.h

Extension

.h

Size

516 bytes

Lines

26

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

• drm/drm_print.h
• ivpu_drv.h
• ivpu_fw_log.h

Detected Declarations

• function ivpu_dev_coredump

Annotated Snippet

#ifndef __IVPU_COREDUMP_H__
#define __IVPU_COREDUMP_H__

#include <drm/drm_print.h>

#include "ivpu_drv.h"
#include "ivpu_fw_log.h"

#ifdef CONFIG_DEV_COREDUMP
void ivpu_dev_coredump(struct ivpu_device *vdev);
#else
static inline void ivpu_dev_coredump(struct ivpu_device *vdev)
{
	struct drm_printer p = drm_info_printer(vdev->drm.dev);

	ivpu_fw_log_print(vdev, false, &p);
}
#endif

#endif /* __IVPU_COREDUMP_H__ */

Annotation

• Immediate include surface: `drm/drm_print.h`, `ivpu_drv.h`, `ivpu_fw_log.h`.
• Detected declarations: `function ivpu_dev_coredump`.
• 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.