drivers/tee/tee_private.h
Source file repositories/reference/linux-study-clean/drivers/tee/tee_private.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/tee/tee_private.h- Extension
.h- Size
- 942 bytes
- Lines
- 36
- Domain
- Driver Families
- Bucket
- drivers/tee
- 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/cdev.hlinux/completion.hlinux/device.hlinux/dma-buf.hlinux/kref.hlinux/mutex.hlinux/types.h
Detected Declarations
struct tee_shm_dmabuf_ref
Annotated Snippet
struct tee_shm_dmabuf_ref {
struct tee_shm shm;
size_t offset;
struct dma_buf *dmabuf;
struct tee_shm *parent_shm;
};
int tee_shm_get_fd(struct tee_shm *shm);
struct tee_shm *tee_shm_alloc_user_buf(struct tee_context *ctx, size_t size);
struct tee_shm *tee_shm_register_user_buf(struct tee_context *ctx,
unsigned long addr, size_t length);
int tee_heap_update_from_dma_buf(struct tee_device *teedev,
struct dma_buf *dmabuf, size_t *offset,
struct tee_shm *shm,
struct tee_shm **parent_shm);
#endif /*TEE_PRIVATE_H*/
Annotation
- Immediate include surface: `linux/cdev.h`, `linux/completion.h`, `linux/device.h`, `linux/dma-buf.h`, `linux/kref.h`, `linux/mutex.h`, `linux/types.h`.
- Detected declarations: `struct tee_shm_dmabuf_ref`.
- Atlas domain: Driver Families / drivers/tee.
- 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.