drivers/gpu/drm/loongson/lsdc_gem.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/loongson/lsdc_gem.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/loongson/lsdc_gem.h- Extension
.h- Size
- 792 bytes
- Lines
- 34
- 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_device.hdrm/drm_gem.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __LSDC_GEM_H__
#define __LSDC_GEM_H__
#include <drm/drm_device.h>
#include <drm/drm_gem.h>
struct drm_gem_object *
lsdc_prime_import_sg_table(struct drm_device *ddev,
struct dma_buf_attachment *attach,
struct sg_table *sg);
int lsdc_dumb_create(struct drm_file *file,
struct drm_device *ddev,
struct drm_mode_create_dumb *args);
void lsdc_gem_init(struct drm_device *ddev);
int lsdc_show_buffer_object(struct seq_file *m, void *arg);
struct drm_gem_object *
lsdc_gem_object_create(struct drm_device *ddev,
u32 domain,
size_t size,
bool kerenl,
struct sg_table *sg,
struct dma_resv *resv);
#endif
Annotation
- Immediate include surface: `drm/drm_device.h`, `drm/drm_gem.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.