qcom_mdt_pas_load(9)

🦋 qcom_mdt_pas_load — kernel API manual, but make it make sense 🦋

okay so bestie, this is the man page for qcom_mdt_pas_load(9), straight out of the kernel API manual. yes, the section-9 one, we're in kernel-dev land now and it's honestly kind of iconic 💅

---

✨ NAME ✨

qcom_mdt_pas_load — she loads and authenticates the metadata of the firmware (which is typically chillin' inside the .mdt file), and then goes ahead and loads the actual firmware segments too (think .bXX files, you know the vibe). 🎀

heads up bestie: the authentication of those segments? not her job. that happens in a separate call. don't come for her, she's just the loader. 😭

---

✨ SYNOPSIS ✨

int qcom_mdt_pas_load (struct qcom_pas_context *ctx , const struct firmware *fw , const char *firmware , phys_addr_t *reloc_base );

---

🫶 ARGUMENTS 🫶

• ctx — pointer to the PAS context (that's Peripheral Authentication Service, iykyk) 🔥
• fw — the firmware object representing the .mdt file
• firmware — name of the firmware, used to construct the segment file names (yes, she's building filenames, main character energy)
• reloc_base — physical address, adjusted after relocation

---

🌸 DESCRIPTION 🌸

so the way this works: the PAS context must be initialized using devm_qcom_pas_context_alloc before you go invoking this function. no cap. if you skip that step, that's on you, not on her 💀

---

⭐ RETURN ⭐

0 on success, or a negative error code on failure. that's it, that's the whole vibe check. ✨

---

👑 SEE ALSO 👑

• kernel file ./drivers/soc/qcom/mdt_loader.c
• qcom_mdt_get_size(9)
• qcom_mdt_read_metadata(9)
• qcom_mdt_load_no_init(9)
• qcom_mdt_load(9)

---

and that's the whole page, bestie 💖 this one's living in ./drivers/soc/qcom, dated October 2026, and it's filed under qcom_mdt_pas_load(9) — go forth and load those segments responsibly 🧚‍♀️🌈🍓