drivers/gpu/drm/i915/gt/shmem_utils.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/i915/gt/shmem_utils.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/i915/gt/shmem_utils.h- Extension
.h- Size
- 745 bytes
- Lines
- 27
- 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/types.h
Detected Declarations
struct iosys_mapstruct drm_i915_gem_objectstruct file
Annotated Snippet
#ifndef SHMEM_UTILS_H
#define SHMEM_UTILS_H
#include <linux/types.h>
struct iosys_map;
struct drm_i915_gem_object;
struct file;
struct file *shmem_create_from_data(const char *name, void *data, size_t len);
struct file *shmem_create_from_object(struct drm_i915_gem_object *obj);
void *shmem_pin_map(struct file *file);
void shmem_unpin_map(struct file *file, void *ptr);
int shmem_read_to_iosys_map(struct file *file, loff_t off,
struct iosys_map *map, size_t map_off, size_t len);
int shmem_read(struct file *file, loff_t off, void *dst, size_t len);
int shmem_write(struct file *file, loff_t off, void *src, size_t len);
#endif /* SHMEM_UTILS_H */
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct iosys_map`, `struct drm_i915_gem_object`, `struct file`.
- 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.