ENUM IWL_FW_INI_TIME_POINT(9)
๐ NAME
enum iwl_fw_ini_time_point โ lowkey the time point type, bestie. That's it, that's the vibe check โจ
โจ SYNOPSIS โจ
enum iwl_fw_ini_time_point {
IWL_FW_INI_TIME_POINT_INVALID ,
IWL_FW_INI_TIME_POINT_EARLY ,
IWL_FW_INI_TIME_POINT_AFTER_ALIVE ,
IWL_FW_INI_TIME_POINT_POST_INIT ,
IWL_FW_INI_TIME_POINT_FW_ASSERT ,
IWL_FW_INI_TIME_POINT_FW_HW_ERROR ,
IWL_FW_INI_TIME_POINT_FW_TFD_Q_HANG ,
IWL_FW_INI_TIME_POINT_FW_DHC_NOTIFICATION ,
IWL_FW_INI_TIME_POINT_FW_RSP_OR_NOTIF ,
IWL_FW_INI_TIME_POINT_USER_TRIGGER ,
IWL_FW_INI_TIME_POINT_PERIODIC ,
IWL_FW_INI_TIME_POINT_RESERVED ,
IWL_FW_INI_TIME_POINT_HOST_ASSERT ,
IWL_FW_INI_TIME_POINT_HOST_ALIVE_TIMEOUT ,
IWL_FW_INI_TIME_POINT_HOST_DEVICE_ENABLE ,
IWL_FW_INI_TIME_POINT_HOST_DEVICE_DISABLE ,
IWL_FW_INI_TIME_POINT_HOST_D3_START ,
IWL_FW_INI_TIME_POINT_HOST_D3_END ,
IWL_FW_INI_TIME_POINT_MISSED_BEACONS ,
IWL_FW_INI_TIME_POINT_ASSOC_FAILED ,
IWL_FW_INI_TIME_POINT_TX_FAILED ,
IWL_FW_INI_TIME_POINT_TX_WFD_ACTION_FRAME_FAILED ,
IWL_FW_INI_TIME_POINT_TX_LATENCY_THRESHOLD ,
IWL_FW_INI_TIME_POINT_HANG_OCCURRED ,
IWL_FW_INI_TIME_POINT_EAPOL_FAILED ,
IWL_FW_INI_TIME_POINT_FAKE_TX ,
IWL_FW_INI_TIME_POINT_DEASSOC ,
IWL_FW_INI_TIME_POINT_PRESET_OVERRIDE_EXT_REQ ,
IWL_FW_INI_TIME_POINT_PRESET_OVERRIDE_START ,
IWL_FW_INI_TIME_SCAN_FAILURE ,
IWL_FW_INI_TIME_ESR_LINK_UP ,
IWL_FW_INI_TIME_ESR_LINK_DOWN ,
IWL_FW_INI_TIME_POINT_NUM
};
๐ Constants ๐
Bestie, here's the full roster โ every single one, no skips, no "and the rest", okay? ๐ซถ
IWL_FW_INI_TIME_POINT_INVALIDโ the invalid timepoint, aka the "girl what" option ๐IWL_FW_INI_TIME_POINT_EARLYโ happens pre loading the FW, before the firmware even wakes up ๐คIWL_FW_INI_TIME_POINT_AFTER_ALIVEโ first cmd from host after alive notif, the lil "hi I'm here" moment ๐IWL_FW_INI_TIME_POINT_POST_INITโ the last cmd in the series of init sequence, closing out the whole routine ๐IWL_FW_INI_TIME_POINT_FW_ASSERTโ FW assert, she's having a crisis ๐ญIWL_FW_INI_TIME_POINT_FW_HW_ERRORโ FW HW error, hardware said nope ๐IWL_FW_INI_TIME_POINT_FW_TFD_Q_HANGโ TFD queue hang, the queue is stuck and being dramaticIWL_FW_INI_TIME_POINT_FW_DHC_NOTIFICATIONโ DHC cmd response and notif ๐ฌIWL_FW_INI_TIME_POINT_FW_RSP_OR_NOTIFโ FW response or notification; thedatafield holds id and group ๐IWL_FW_INI_TIME_POINT_USER_TRIGGERโ user trigger time point, you did this, main character energy ๐IWL_FW_INI_TIME_POINT_PERIODICโ periodic timepoint that fires in constant intervals; thedatafield holds the interval time in msec โฐIWL_FW_INI_TIME_POINT_RESERVEDโ reserved, not for us bestie ๐ซIWL_FW_INI_TIME_POINT_HOST_ASSERTโ literally marked "Unused", she's just vibing there ๐ฆIWL_FW_INI_TIME_POINT_HOST_ALIVE_TIMEOUTโ alive timeout, the firmware ghosted us ๐IWL_FW_INI_TIME_POINT_HOST_DEVICE_ENABLEโ device enable โIWL_FW_INI_TIME_POINT_HOST_DEVICE_DISABLEโ device disable โIWL_FW_INI_TIME_POINT_HOST_D3_STARTโ D3 start ๐IWL_FW_INI_TIME_POINT_HOST_D3_ENDโ D3 end ๐IWL_FW_INI_TIME_POINT_MISSED_BEACONSโ missed beacons, she's not picking up the signal ๐กIWL_FW_INI_TIME_POINT_ASSOC_FAILEDโ association failure, the connection didn't slay ๐IWL_FW_INI_TIME_POINT_TX_FAILEDโ Tx frame failed, frame never made it out the door ๐ฌIWL_FW_INI_TIME_POINT_TX_WFD_ACTION_FRAME_FAILEDโ wifi direct action frame failed ๐ถIWL_FW_INI_TIME_POINT_TX_LATENCY_THRESHOLDโ Tx latency threshold, the vibes got too slow ๐IWL_FW_INI_TIME_POINT_HANG_OCCURREDโ hang occurred, everything froze, iconic in the worst way ๐IWL_FW_INI_TIME_POINT_EAPOL_FAILEDโ EAPOL failed ๐IWL_FW_INI_TIME_POINT_FAKE_TXโ fake Tx, pretend transmission, we're manifesting โจIWL_FW_INI_TIME_POINT_DEASSOCโ de association, it's giving breakup ๐ญIWL_FW_INI_TIME_POINT_PRESET_OVERRIDE_EXT_REQโ request to override preset ๐IWL_FW_INI_TIME_POINT_PRESET_OVERRIDE_STARTโ start handling override preset request ๐IWL_FW_INI_TIME_SCAN_FAILUREโ failed scan channel list, the scan said no ๐IWL_FW_INI_TIME_ESR_LINK_UPโ EMLSR is active (several links are activated) ๐IWL_FW_INI_TIME_ESR_LINK_DOWNโ EMLSR is inactive (only one active link left) ๐ชซIWL_FW_INI_TIME_POINT_NUMโ number of time points, the lil counter at the end ๐งฎ
๐ Description ๐
So here's the tea: these are hard coded time points in which the driver can send hcmd or perform dump collection. That's the whole point โ fixed moments in the timeline where the driver's allowed to do its thing. No cap ๐ฅ
๐ธ SEE ALSO ๐ธ
Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/dbg-tlv.h โ and the whole squad lives there too, bestie:
struct iwl_fw_ini_hcmd(9), struct iwl_fw_ini_header(9), struct iwl_fw_ini_addr_size(9), struct iwl_fw_ini_region_dev_addr_range(9), struct iwl_fw_ini_region_dev_addr(9), struct iwl_fw_ini_region_fifos(9), struct iwl_fw_ini_region_err_table(9), struct iwl_fw_ini_region_special_device_memory(9), struct iwl_fw_ini_region_internal_buffer(9), struct iwl_fw_ini_region_tlv(9), struct iwl_fw_ini_debug_info_tlv(9), struct iwl_fw_ini_allocation_tlv(9), struct iwl_fw_ini_trigger_tlv(9), struct iwl_fw_ini_hcmd_tlv(9), struct iwl_fw_ini_addr_val(9), struct iwl_fw_ini_conf_set_tlv(9), enum iwl_fw_ini_config_set_type(9), enum iwl_fw_ini_allocation_id(9), enum iwl_fw_ini_buffer_location(9), enum iwl_fw_ini_region_type(9), enum iwl_fw_ini_trigger_apply_policy(9), enum iwl_fw_ini_trigger_reset_fw_policy(9), enum iwl_fw_ini_dump_policy(9), enum iwl_fw_ini_dump_type(9)
Okay that's the whole page, go read the source next, iykyk ๐ง๐
And finally โ mwah, this little page came from ./drivers/net/wireless/intel/i... and she's dated October 2026. Slay, periodt. ๐๐
๐ฆ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms