qcom_pas_mem_setup(9)

💅 qcom_pas_mem_setup — Kernel API Manual, section 9 🎀

okay so bestie, welcome to qcom_pas_mem_setup(9), the function that gets a peripheral's memory all cute and ready so the firmware can slide in and do its thing ✨

---

🌸 NAME 🌸

qcom_pas_mem_setup — prepares the memory that belongs to a given peripheral so the firmware can be loaded into it 🫶

---

⭐ SYNOPSIS ⭐

int qcom_pas_mem_setup (u32 pas_id , phys_addr_t addr , phys_addr_t size );

like, that's the whole signature, no cap. three args, one int coming back at you 💖

---

🦋 ARGUMENTS 🦋

• pas_id — the peripheral authentication service id 👑 it's literally the name tag for which peripheral we're talking about.
• addr — the start address of the memory area we're getting ready 🎀
• size — how big that memory area is, i.e. how much we're preparing 🌸

---

✨ RETURN ✨

returns 0 on success 💖 that's it, that's the whole return story, and honestly? iconic.

---

🌈 SEE ALSO 🌈

the kernel file lives right here, go look at it, iykyk:

./drivers/firmware/qcom/qcom_pas.c

and these are the besties it runs with 👑:

• devm_qcom_pas_context_alloc(9)
• qcom_pas_init_image(9)
• qcom_pas_metadata_release(9)
• qcom_pas_get_rsc_table(9)
• qcom_pas_auth_and_reset(9)
• qcom_pas_prepare_and_auth_reset(9)
• qcom_pas_set_remote_state(9)
• qcom_pas_shutdown(9)
• qcom_pas_supported(9)
• qcom_pas_is_available(9)

---

and that's the page, bestie!! 💀🫶 it came from ./drivers/firmware/qcom, it's dated October 2026, and it goes by qcom_pas_mem_setup(9) — periodt, no notes 💅⭐