drivers/gpu/drm/amd/display/dc/irq/dce110/irq_service_dce110.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/display/dc/irq/dce110/irq_service_dce110.h

Extension

.h

Size

1821 bytes

Lines

54

Domain

Driver Families

Bucket

drivers/gpu

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

• ../irq_service.h

Detected Declarations

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

Annotated Snippet

#ifndef __DAL_IRQ_SERVICE_DCE110_H__
#define __DAL_IRQ_SERVICE_DCE110_H__

#include "../irq_service.h"

struct irq_service *dal_irq_service_dce110_create(
	struct irq_service_init_data *init_data);

enum dc_irq_source to_dal_irq_source_dce110(
		struct irq_service *irq_service,
		uint32_t src_id,
		uint32_t ext_id);

bool dal_irq_service_dummy_set(
	struct irq_service *irq_service,
	const struct irq_source_info *info,
	bool enable);

bool dal_irq_service_dummy_ack(
	struct irq_service *irq_service,
	const struct irq_source_info *info);

bool dce110_vblank_set(
	struct irq_service *irq_service,
	const struct irq_source_info *info,
	bool enable);

#endif

Annotation

• Immediate include surface: `../irq_service.h`.
• Atlas domain: Driver Families / drivers/gpu.
• 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.