rx51_secure_dispatcher(9)

💅 rx51_secure_dispatcher — like, the whole vibe

Okay bestie, welcome to section 9 of the Kernel API Manual ✨ — today's main character is rx51_secure_dispatcher, and its entire job description is "Routine to dispatch secure PPA API calls". That's it. That's the girl. 🎀

---

✨ SYNOPSIS ✨

u32 rx51_secure_dispatcher (u32 idx , u32 process , u32 flag , u32 nargs
, u32 arg1 , u32 arg2 , u32 arg3 , u32 arg4 );

Not me counting the args — there are literally eight, and she returns a u32. Slay. 💅

---

🌸 ARGUMENTS 🌸

• idx — The PPA API index. Think of it as the little number that tells everyone which API we're calling. 🔢
• process — Process ID. Yes, the whole process gets an ID card. Iconic. 🪪
• flag — The flag indicating criticality of operation. Like, is this a big deal or not? 🚨
• nargs — Number of valid arguments out of four. So: arg1, arg2, arg3, args4 — those are the parameters passed to the secure API. Count carefully, bestie. 🧮
• arg1 — -- undescribed -- 🙈
• arg2 — -- undescribed -- 🙈
• arg3 — -- undescribed -- 🙈
• arg4 — -- undescribed -- 🙈

Fr fr the docs just say -- undescribed -- for those last four. Not me making up lore. I would never. 💀

---

🦋 DESCRIPTION 🦋

Return the non-zero error value on failure. That's the whole description, and honestly? She said what she said. ✨

---

👑 NOTE 👑

rx51_secure_dispatcher differs from omap_secure_dispatcher because it calling omap_smc3 instead omap_smc2 and param[0] is nargs+1.

Lowkey the two big flexes here: different SMC call, and param[0] gets that extra +1. Highkey important. 🔥

---

🧚 SEE ALSO 🧚

• Kernel file ./arch/arm/mach-omap2/omap-secure.c
• omap_secure_dispatcher(9)
• rx51_secure_update_aux_cr(9)
• rx51_secure_rng_call(9)

Go read your sisters' pages, iykyk. 📚

---

That's the whole page, bestie — brought to you from ./arch/arm/mach-omap2, dated October 2026, and yes the page header said rx51_secure_dispatcher(9) in the Kernel API Manual the whole time. Periodt. 💜✨