include/uapi/drm/drm_ras.h
Source file repositories/reference/linux-study-clean/include/uapi/drm/drm_ras.h
File Facts
- System
- Linux kernel
- Corpus path
include/uapi/drm/drm_ras.h- Extension
.h- Size
- 1353 bytes
- Lines
- 51
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: implementation source
- Status
- source implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
enum drm_ras_node_type
Annotated Snippet
#ifndef _UAPI_LINUX_DRM_RAS_H
#define _UAPI_LINUX_DRM_RAS_H
#define DRM_RAS_FAMILY_NAME "drm-ras"
#define DRM_RAS_FAMILY_VERSION 1
/*
* Type of the node. Currently, only error-counter nodes are supported, which
* expose reliability counters for a hardware/software component.
*/
enum drm_ras_node_type {
DRM_RAS_NODE_TYPE_ERROR_COUNTER = 1,
};
enum {
DRM_RAS_A_NODE_ATTRS_NODE_ID = 1,
DRM_RAS_A_NODE_ATTRS_DEVICE_NAME,
DRM_RAS_A_NODE_ATTRS_NODE_NAME,
DRM_RAS_A_NODE_ATTRS_NODE_TYPE,
__DRM_RAS_A_NODE_ATTRS_MAX,
DRM_RAS_A_NODE_ATTRS_MAX = (__DRM_RAS_A_NODE_ATTRS_MAX - 1)
};
enum {
DRM_RAS_A_ERROR_COUNTER_ATTRS_NODE_ID = 1,
DRM_RAS_A_ERROR_COUNTER_ATTRS_ERROR_ID,
DRM_RAS_A_ERROR_COUNTER_ATTRS_ERROR_NAME,
DRM_RAS_A_ERROR_COUNTER_ATTRS_ERROR_VALUE,
__DRM_RAS_A_ERROR_COUNTER_ATTRS_MAX,
DRM_RAS_A_ERROR_COUNTER_ATTRS_MAX = (__DRM_RAS_A_ERROR_COUNTER_ATTRS_MAX - 1)
};
enum {
DRM_RAS_CMD_LIST_NODES = 1,
DRM_RAS_CMD_GET_ERROR_COUNTER,
DRM_RAS_CMD_CLEAR_ERROR_COUNTER,
__DRM_RAS_CMD_MAX,
DRM_RAS_CMD_MAX = (__DRM_RAS_CMD_MAX - 1)
};
#endif /* _UAPI_LINUX_DRM_RAS_H */
Annotation
- Detected declarations: `enum drm_ras_node_type`.
- Atlas domain: Repository Root And Misc / include.
- 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.