devm_qcom_pas_context_alloc(9)

💅 devm_qcom_pas_context_alloc(9) — the kernel API manual, bestie edition ✨

Okay so this is a page from the Kernel API Manual, and it's about devm_qcom_pas_context_alloc — yes that's a whole mouthful, don't worry, we're gonna get through it together 🫶

---

🌸 NAME 🌸

devm_qcom_pas_context_alloc — allocate a peripheral authentication service context for a given peripheral ✨

---

🦋 SYNOPSIS 🦋

struct qcom_pas_context * devm_qcom_pas_context_alloc (struct device
*dev , u32 pas_id , phys_addr_t mem_phys , size_t mem_size );

---

🎀 ARGUMENTS 🎀

• dev — the PAS firmware device 🧚
• pas_id — the peripheral authentication service id, iykyk
• mem_phys — subsystem reserve memory start address, like where the memory begins bestie
• mem_size — subsystem reserve memory size, aka how much we're working with 💖

---

⭐ DESCRIPTION ⭐

So the PAS context is device-resource managed — which is literally the best news ever, because it means the caller does not need to worry about freeing the context memory. Not me having to manually clean up… couldn't be this function 💅 the devres magic handles it, you just vibe 😌

---

👑 RETURN 👑

It gives you back the new PAS context, or ERR_PTR on failure 😭 (so like, check it, bestie, fr fr).

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/firmware/qcom/qcom_pas.c — and the whole squad:

• qcom_pas_init_image(9)
• qcom_pas_metadata_release(9)
• qcom_pas_mem_setup(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 whole page, bestie 🎀 this gem lives in ./drivers/firmware/qcom, stamped October 2026, and its name is — say it with me — devm_qcom_pas_context_alloc(9) 💜 slay, go forth and allocate ✨🦋