qcom_mdt_load_no_init(9)

💖 qcom_mdt_load_no_init(9) 💖

okay so bestie, welcome to the Kernel API Manual — yes we're literally in the kernel docs together and it's giving study date energy 🎀 this one is qcom_mdt_load_no_init(9), and no cap it's the icon that loads your firmware when the header's already loaded as fw ✨

---

🌸 NAME 🌸

qcom_mdt_load_no_init — loads the firmware which header is loaded as fw 🫶

---

✨ SYNOPSIS ✨

int qcom_mdt_load_no_init (struct device *dev , const struct firmware
*fw , const char *fw_name , void *mem_region , phys_addr_t mem_phys ,
size_t mem_size , phys_addr_t *reloc_base );

seven args, one int return, main character energy only 💅

---

🦋 ARGUMENTS 🦋

• dev — the device handle, aka where we associate all the resources 🏠
• fw — the firmware object for the mdt file, your little blob of destiny 🍓
• fw_name — name of the firmware, and it's used for construction of the segment file names (so like, the segment names get built off it, iykyk) 🏷️
• mem_region — the allocated memory region we're loading the firmware into, that's its whole vibe 📦
• mem_phys — physical address of that allocated memory region 🔢
• mem_size — size of the allocated memory region, how much room we've got fr fr 📏
• reloc_base — adjusted physical address after relocation, it's the glow-up address 🔥

---

💜 DESCRIPTION 💜

Returns 0 on success, negative errno otherwise. That's it, that's the whole description, she's brief but she ate 💀✨

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/soc/qcom/mdt_loader.c
• qcom_mdt_get_size(9)
• qcom_mdt_read_metadata(9)
• qcom_mdt_load(9)
• qcom_mdt_pas_load(9)

go read the whole friend group, they're all iconic 👑

---

🫶 cute little sign-off: this page lives under ./drivers/soc/qcom, dated October 2026, and it's still the same qcom_mdt_load_no_init(9) you know and love. periodt. 💅🎀