drivers/accel/ivpu/ivpu_fw_log.h

File Facts

System

Linux kernel

Corpus path

drivers/accel/ivpu/ivpu_fw_log.h

Extension

.h

Size

793 bytes

Lines

32

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

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __IVPU_FW_LOG_H__
#define __IVPU_FW_LOG_H__

#include <linux/types.h>

#include "ivpu_drv.h"

#define IVPU_FW_LOG_DEFAULT 0
#define IVPU_FW_LOG_DEBUG   1
#define IVPU_FW_LOG_INFO    2
#define IVPU_FW_LOG_WARN    3
#define IVPU_FW_LOG_ERROR   4
#define IVPU_FW_LOG_FATAL   5

#define IVPU_FW_VERBOSE_BUFFER_SMALL_SIZE	SZ_1M
#define IVPU_FW_VERBOSE_BUFFER_LARGE_SIZE	SZ_8M
#define IVPU_FW_CRITICAL_BUFFER_SIZE		SZ_512K

extern unsigned int ivpu_fw_log_level;

void ivpu_fw_log_print(struct ivpu_device *vdev, bool only_new_msgs, struct drm_printer *p);
void ivpu_fw_log_mark_read(struct ivpu_device *vdev);
void ivpu_fw_log_reset(struct ivpu_device *vdev);


#endif /* __IVPU_FW_LOG_H__ */

Annotation

• Immediate include surface: `linux/types.h`, `ivpu_drv.h`.
• 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.