tee_device_address(3)
πΈ NAME πΈ
okay so this page is tee_device_address(3) from the Library Functions Manual, and the NAME is literally tee_device_address β no cap, bestie. π
β¨ SYNOPSIS β¨
#include <metee.h>
π Public Types π
enum { TEE_DEVICE_TYPE_NONE = 0, TEE_DEVICE_TYPE_PATH = 1,
TEE_DEVICE_TYPE_HANDLE = 2, TEE_DEVICE_TYPE_GUID = 3,
TEE_DEVICE_TYPE_BDF = 4, TEE_DEVICE_TYPE_MAX = 5 }
π Data Fields π
enum tee_device_address:: { ... } type
union {
const char * path
const GUID * guid
TEE_DEVICE_HANDLE handle
struct {
enum HECI_HW_TYPE { HECI_HW_TYPE_PCH, HECI_HW_TYPE_GFX_GSC,
HECI_HW_TYPE_GFX_CSC }
struct {
uint32_t segment
uint32_t bus
uint32_t device
uint32_t function
} value
enum tee_device_address:: { ... } ::HECI_HW_TYPE hw_type
} bdf
} data
π¦ Detailed Description π¦
The whole vibe is Device address passed to the init function. Thatβs the description, and itβs giving βthis is the address-y thing you hand over to initβ energy. π
Definition at line 129 of file metee.h.
π Member Enumeration Documentation π
anonymous enum
Device address type β¨
Enumerator
TEE_DEVICE_TYPE_NONEβ Select first available device π«ΆTEE_DEVICE_TYPE_PATHβ Use device by path (char*) πTEE_DEVICE_TYPE_HANDLEβ Use device by pre-opend handle (yes,pre-opend, exactly like the original, bestie β Iβm not fixing it) πTEE_DEVICE_TYPE_GUIDβ Select first device by GUID (Windows only) πͺTEE_DEVICE_TYPE_BDFβ Use BDF to work with HECI, EFI only π₯TEE_DEVICE_TYPE_MAXβ upper sentinel π
Definition at line 132 of file metee.h.
π Field Documentation π
uint32_t tee_device_address::bus
The doc text is literally HECI device Segment β yes, thatβs the mapping, and Iβm keeping it exactly as printed, no cap. π
Definition at line 149 of file metee.h.
union { ... } tee_device_address::data
Device address β thatβs the whole note for this one, bestie. π¦
uint32_t tee_device_address::device
The doc text is literally HECI device Bus β again, exactly as printed. πΈ
Definition at line 150 of file metee.h.
uint32_t tee_device_address::function
The doc text is literally HECI device Device β yes, βdevice Device,β and Iβm not editing the originalβs chaos. π
Definition at line 151 of file metee.h.
const GUID* tee_device_address::guid
The doc text is literally < Path to device β with that little < in front, exactly as shown. π
Definition at line 144 of file metee.h.
TEE_DEVICE_HANDLE tee_device_address::handle
The doc text is literally Device GUID (Windows only) Pre-opend handle β and yes, pre-opend is spelled that way in the original, so it stays. π
Definition at line 145 of file metee.h.
const char* tee_device_address::path
No description text here β just the definition-line receipt. π§Ύ
Definition at line 143 of file metee.h.
uint32_t tee_device_address::segment
No description text here either β just the line number. β¨
Definition at line 148 of file metee.h.
enum { ... } tee_device_address::type
Device address type β thatβs the note, and thereβs no definition-line line printed for this one in the original. π«Ά
π Author π
Generated automatically by Doxygen for metee from the source code. π€π
π Cute sign-off: source/version is metee; the footerβs date slot isnβt printed in the original page, so Iβm not inventing a date β and the footer also carries tee_device_address(3), periodt. π
π¦ where this page comes from
- epel 10: intel-metee-devel 6.2.5-1.el10_3 Β· Apache-2.0 AND BSD-3-Clause AND ((GPL-2.0-only WITH Linux-syscall-note) OR BSD-3-Clause)
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms