drivers/gpu/drm/lima/lima_drv.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/lima/lima_drv.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/lima/lima_drv.h- Extension
.h- Size
- 907 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
drm/drm_file.hlima_ctx.hlima_device.h
Detected Declarations
struct lima_vmstruct lima_bostruct lima_sched_taskstruct drm_lima_gem_submit_bostruct lima_drm_privstruct lima_submitstruct lima_compatiblefunction to_lima_drm_priv
Annotated Snippet
struct lima_drm_priv {
struct lima_vm *vm;
struct lima_ctx_mgr ctx_mgr;
};
struct lima_submit {
struct lima_ctx *ctx;
int pipe;
u32 flags;
struct drm_lima_gem_submit_bo *bos;
struct lima_bo **lbos;
u32 nr_bos;
u32 in_sync[2];
u32 out_sync;
struct lima_sched_task *task;
};
struct lima_compatible {
enum lima_gpu_id id;
};
static inline struct lima_drm_priv *
to_lima_drm_priv(struct drm_file *file)
{
return file->driver_priv;
}
#endif
Annotation
- Immediate include surface: `drm/drm_file.h`, `lima_ctx.h`, `lima_device.h`.
- Detected declarations: `struct lima_vm`, `struct lima_bo`, `struct lima_sched_task`, `struct drm_lima_gem_submit_bo`, `struct lima_drm_priv`, `struct lima_submit`, `struct lima_compatible`, `function to_lima_drm_priv`.
- 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.