scm_legacy_g...ponse_buffer(9)

💅 scm_legacy_get_response_buffer — Kernel API Manual

okay bestie, welcome to the manual page for scm_legacy_get_response_buffer(9) — yes that's the full name, no we're not shortening it, it's iconic like that ✨

---

🌸 NAME 🌸

scm_legacy_get_response_buffer — literally just hands you a pointer to a response buffer 🫶

---

🎀 SYNOPSIS 🎀

void * scm_legacy_get_response_buffer (const struct scm_legacy_response
*rsp );

---

🦋 ARGUMENTS 🦋

• rsp — the response. that's it. that's the whole argument. she's a const struct scm_legacy_response * and she's serving 💅

---

⭐ DESCRIPTION ⭐

so what does it do? it returns a pointer to a response buffer of a response. no cap, that's the whole bit 🙈

like — you give it a response, it gives you back a void * pointing at that response's buffer. main character behaviour, honestly 👑

---

💖 SEE ALSO 💖

• Kernel file ./drivers/firmware/qcom/qcom_scm-legacy.c — go read the source, iykyk 📖
• struct arm_smccc_args(9)
• struct scm_legacy_command(9)
• struct scm_legacy_response(9)
• scm_legacy_command_to_response(9)
• scm_legacy_get_command_buffer(9)
• scm_legacy_call(9)
• scm_legacy_call_atomic(9)

all the siblings in the friend group, fr fr 🌈

---

🧚 lowkey a reminder: everything above is exactly what the page says and nothing more — i'm not out here inventing lore 💀

---

and that's the page!! mwah 💋 this one lives in ./drivers/firmware/qcom, dated October 2026, and the header/footer both go by scm_legacy_g...ponse_buffer(9) — yes, with the lil ellipsis, she's mysterious like that 🎀✨