drivers/media/platform/qcom/venus/dbgfs.c

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/qcom/venus/dbgfs.c

Extension

.c

Size

604 bytes

Lines

29

Domain

Driver Families

Bucket

drivers/media

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/debugfs.h
• linux/fault-inject.h
• core.h

Detected Declarations

• function venus_dbgfs_init
• function venus_dbgfs_deinit

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-only
/*
 * Copyright (C) 2020 Linaro Ltd.
 */

#include <linux/debugfs.h>
#include <linux/fault-inject.h>

#include "core.h"

#ifdef CONFIG_FAULT_INJECTION
DECLARE_FAULT_ATTR(venus_ssr_attr);
#endif

void venus_dbgfs_init(struct venus_core *core)
{
	core->root = debugfs_create_dir("venus", NULL);
	debugfs_create_x32("fw_level", 0644, core->root, &venus_fw_debug);

#ifdef CONFIG_FAULT_INJECTION
	fault_create_debugfs_attr("fail_ssr", core->root, &venus_ssr_attr);
#endif
}

void venus_dbgfs_deinit(struct venus_core *core)
{
	debugfs_remove_recursive(core->root);
}

Annotation

• Immediate include surface: `linux/debugfs.h`, `linux/fault-inject.h`, `core.h`.
• Detected declarations: `function venus_dbgfs_init`, `function venus_dbgfs_deinit`.
• Atlas domain: Driver Families / drivers/media.
• 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.