drivers/gpu/drm/xe/xe_sysctrl_mailbox.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_sysctrl_mailbox.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_sysctrl_mailbox.h- Extension
.h- Size
- 742 bytes
- Lines
- 32
- 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
linux/bitfield.hlinux/types.habi/xe_sysctrl_abi.h
Detected Declarations
struct xe_sysctrlstruct xe_sysctrl_mailbox_command
Annotated Snippet
#ifndef _XE_SYSCTRL_MAILBOX_H_
#define _XE_SYSCTRL_MAILBOX_H_
#include <linux/bitfield.h>
#include <linux/types.h>
#include "abi/xe_sysctrl_abi.h"
struct xe_sysctrl;
struct xe_sysctrl_mailbox_command;
#define XE_SYSCTRL_APP_HDR_GROUP_ID(hdr) \
FIELD_GET(APP_HDR_GROUP_ID_MASK, (hdr)->data)
#define XE_SYSCTRL_APP_HDR_COMMAND(hdr) \
FIELD_GET(APP_HDR_COMMAND_MASK, (hdr)->data)
#define XE_SYSCTRL_APP_HDR_VERSION(hdr) \
FIELD_GET(APP_HDR_VERSION_MASK, (hdr)->data)
void xe_sysctrl_mailbox_init(struct xe_sysctrl *sc);
int xe_sysctrl_send_command(struct xe_sysctrl *sc,
struct xe_sysctrl_mailbox_command *cmd,
size_t *rdata_len);
#endif
Annotation
- Immediate include surface: `linux/bitfield.h`, `linux/types.h`, `abi/xe_sysctrl_abi.h`.
- Detected declarations: `struct xe_sysctrl`, `struct xe_sysctrl_mailbox_command`.
- 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.