tee_device_address(3)

πŸ“¦
version 6.2.5 Β· 4 versions
, in epel 10

🌸 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