STRUCT IWL_TIME_MSMT_PTP_CTX(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct iwl_t...msmt_ptp_ctx(9) β€” Kernel API Manual, but make it make sense

okay bestie, so this is a page from the Kernel API Manual (yes, the actual kernel docs, we're fancy now πŸŽ€) and it's all about struct iwl_time_msmt_ptp_ctx. Say that five times fast. I dare you. 🫢


✨ NAME ✨

struct iwl_time_msmt_ptp_ctx β€” a vendor specific element that literally just exists to allow a space for flexibility for the userspace App πŸ’– (that's the whole job, and honestly? iconic.)


🌸 SYNOPSIS 🌸

ok so here's the shape of it, and no I will not be paraphrasing code, that's illegal in my house:

struct iwl_time_msmt_ptp_ctx {
    union {
      struct {
        u8 element_id;
        u8 length;
        __le16 reserved;
        u8 data[PTP_CTX_MAX_DATA_SIZE];
      } ftm;
      struct {
        u8 element_id;
        u8 length;
        u8 data[PTP_CTX_MAX_DATA_SIZE];
      } tm;
    };
 };

like. look at it. two little structs vibing inside a union. main character energy fr fr πŸ‘‘


πŸ¦‹ Members πŸ¦‹

okay this is the part where we meet the whole cast:

  • {unnamed_union} β€” anonymous. no name. mysterious. doesn't need one. lowkey slay πŸ’€
  • ftm β€” the FTM specific vendor element 🌈
    • ftm.element_id β€” element id of the vendor specific ie
    • ftm.length β€” length of the vendor specific ie
    • ftm.reserved β€” for alignment (the little guy holding the door open so everything lines up πŸ’…)
    • ftm.data β€” vendor specific data blob
  • tm β€” the TM specific vendor element ⭐
    • tm.element_id β€” element id of the vendor specific ie
    • tm.length β€” length of the vendor specific ie
    • tm.data β€” vendor specific data blob
no cap: ftm and tm are the two options inside that union, so it's one or the other, not both. the union said what it said. πŸ’œ

πŸ‘‘ SEE ALSO πŸ‘‘

the friend group (a.k.a. everything in Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/datapath.h that you should also go read, because we support each other):

  • enum iwl_data_path_subcmd_ids(9)
  • struct iwl_mu_group_mgmt_cmd(9)
  • struct iwl_mu_group_mgmt_notif(9)
  • struct iwl_time_sync_cfg_cmd(9)
  • enum iwl_synced_time_operation(9)
  • struct iwl_synced_time_cmd(9)
  • struct iwl_synced_time_rsp(9)
  • struct iwl_time_msmt_notify(9)
  • struct iwl_time_msmt_cfm_notify(9)
  • struct iwl_channel_estimation_cfg(9)
  • enum iwl_thermal_dual_chain_req_events(9)
  • struct iwl_thermal_dual_chain_request(9)
  • struct iwl_rlc_properties(9)
  • struct iwl_sad_properties(9)
  • struct iwl_rlc_config_cmd(9)
  • enum iwl_rx_baid_action(9)
  • struct iwl_rx_baid_cfg_cmd_alloc(9)
  • struct iwl_rx_baid_cfg_cmd_modify(9)
  • struct iwl_rx_baid_cfg_cmd_remove_v1(9)
  • struct iwl_rx_baid_cfg_cmd_remove(9)
  • struct iwl_rx_baid_cfg_cmd(9)
  • struct iwl_rx_baid_cfg_resp(9)
  • enum iwl_scd_queue_cfg_operation(9)
  • struct iwl_scd_queue_cfg_cmd(9)
  • enum iwl_sec_key_flags(9)
  • struct iwl_sec_key_cmd(9)

that's the whole page bestie, you ate that πŸ“βœ¨

source: ./drivers/net/wireless/intel/i... Β· October 2026 Β· struct iwl_t...msmt_ptp_ctx(9) β€” mwah, go read the other ones too πŸ’–πŸ§š

πŸ“¦ where this page comes from