hl_fw_init_cpu(9)

💖 hl_fw_init_cpu — the one where the device CPU wakes up 💖

okay so first things first, this is a kernel API page, like, section 9 of the manual manual, and the star of the show is hl_fw_init_cpu. bestie, we're literally in the habanalabs firmware interface files, this is the glow-up arc of the whole boot process. let's get into it 🎀

---

✨ SYNOPSIS ✨

int hl_fw_init_cpu (struct hl_device *hdev );

yeah that's it, that's the whole signature. int going in, int going out, iconic behavior 🙈

---

🫶 ARGUMENTS 🫶

• hdev — pointer to the struct hl_device (the habanalabs device structure, iykyk). like, it's just a pointer. to the device struct. she's the main character and we hand her over 💅

---

🌸 DESCRIPTION 🌸

okay so what does she actually do? two things, both big:

1. return 0 on success, otherwise non-zero error code — no cap, that's the whole return contract. 0 = slay. anything else = something went sideways 😭
2. she performs the necessary initializations for the device's CPU 🔥 and here's the cute part: she takes into account if the init protocol is static or dynamic. so she's checking which vibe the init protocol is giving before she commits. flexible queen energy fr fr 👑

---

👑 SEE ALSO 👑

alright buckle up, this list is long, but every single one of these is a reference and we are NOT skipping any of them:

the kernel file itself:

• Kernel file ./drivers/accel/habanalabs/common/firmware_if.c — the actual source, go read her 💖

the whole friend group:

• hl_fw_version_cmp(9)
• extract_u32_until_given_char(9)
• hl_get_sw_major_minor_subminor(9)
• hl_get_preboot_major_minor(9)
• hl_release_firmware(9)
• hl_fw_copy_fw_to_device(9)
• hl_fw_copy_msg_to_device(9)
• hl_fw_load_fw_to_device(9)
• hl_fw_send_cpu_message(9)
• hl_fw_preboot_update_state(9)
• hl_fw_dynamic_report_error_status(9)
• hl_fw_dynamic_send_cmd(9)
• hl_fw_dynamic_extract_fw_response(9)
• hl_fw_dynamic_wait_for_status(9)
• hl_fw_dynamic_send_clear_cmd(9)
• hl_fw_dynamic_send_protocol_cmd(9)
• hl_fw_compat_crc32(9)
• hl_fw_dynamic_validate_memory_bound(9)
• hl_fw_dynamic_validate_descriptor(9)
• hl_fw_dynamic_read_and_validate_descriptor(9)
• hl_fw_dynamic_request_descriptor(9)
• hl_fw_dynamic_read_device_fw_version(9)
• hl_fw_dynamic_copy_image(9)
• hl_fw_dynamic_copy_msg(9)
• hl_fw_boot_fit_update_state(9)
• hl_fw_dynamic_load_image(9)
• hl_fw_linux_update_state(9)
• hl_fw_dynamic_send_msg(9)
• hl_fw_dynamic_init_cpu(9)
• hl_fw_static_init_cpu(9)

not me listing thirty of them, but that's the canon, bestie — the static path and the dynamic path both show up at the end there, which makes total sense given what we said in DESCRIPTION 😌

💀 real talk though: this is kernel API territory. if you're poking at firmware init without knowing what you're doing, that's not a cute look. read the source and the related pages first, okay? 🫶

---

🌈 sign-off 🌈

and that's the page!! brought to you by the fine folks in ./drivers/accel/habanalabs/common, dated October 2026, and yes the version/date lives at the bottom like a little footer bow 🎀 mwah, go init some CPUs responsibly 💜✨