drivers/gpu/drm/ttm/ttm_pool_internal.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/ttm/ttm_pool_internal.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/ttm/ttm_pool_internal.h- Extension
.h- Size
- 600 bytes
- Lines
- 26
- 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/ttm/ttm_allocation.hdrm/ttm/ttm_pool.h
Detected Declarations
function ttm_pool_uses_dma_allocfunction ttm_pool_uses_dma32function ttm_pool_beneficial_order
Annotated Snippet
#ifndef _TTM_POOL_INTERNAL_H_
#define _TTM_POOL_INTERNAL_H_
#include <drm/ttm/ttm_allocation.h>
#include <drm/ttm/ttm_pool.h>
static inline bool ttm_pool_uses_dma_alloc(struct ttm_pool *pool)
{
return pool->alloc_flags & TTM_ALLOCATION_POOL_USE_DMA_ALLOC;
}
static inline bool ttm_pool_uses_dma32(struct ttm_pool *pool)
{
return pool->alloc_flags & TTM_ALLOCATION_POOL_USE_DMA32;
}
static inline unsigned int ttm_pool_beneficial_order(struct ttm_pool *pool)
{
return pool->alloc_flags & 0xff;
}
#endif
Annotation
- Immediate include surface: `drm/ttm/ttm_allocation.h`, `drm/ttm/ttm_pool.h`.
- Detected declarations: `function ttm_pool_uses_dma_alloc`, `function ttm_pool_uses_dma32`, `function ttm_pool_beneficial_order`.
- 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.