drivers/gpu/drm/ci/xfails/rockchip-rk3288-fails.txt
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/ci/xfails/rockchip-rk3288-fails.txt
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/ci/xfails/rockchip-rk3288-fails.txt- Extension
.txt- Size
- 726 bytes
- Lines
- 19
- Domain
- Driver Families
- Bucket
- drivers/gpu
- Inferred role
- Driver Families: documentation
- Status
- atlas-only
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.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
core_setmaster@master-drop-set-root,Crash
core_setmaster@master-drop-set-shared-fd,Crash
core_setmaster@master-drop-set-user,Crash
core_setmaster_vs_auth,Crash
fbdev@pan,Crash
kms_cursor_crc@cursor-dpms,Crash
kms_cursor_crc@cursor-sliding-32x32,Crash
kms_cursor_legacy@basic-flip-before-cursor-atomic,Crash
kms_cursor_legacy@cursor-vs-flip-atomic,Crash
kms_flip@basic-flip-vs-wf_vblank,Crash
kms_flip@flip-vs-panning-vs-hang,Crash
kms_flip@plain-flip-fb-recreate-interruptible,Crash
kms_pipe_crc_basic@read-crc-frame-sequence,Crash
kms_plane_cursor@overlay,Crash
kms_plane_cursor@viewport,Crash
kms_prop_blob@invalid-set-prop-any,Crash
kms_prop_blob@invalid-set-prop,Crash
kms_properties@get_properties-sanity-non-atomic,Fail
Annotation
- Atlas domain: Driver Families / drivers/gpu.
- Implementation status: atlas-only.
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.