tegra_emc_ra...equests_init(9)

✨ NAME ✨

tegra_emc_rate_requests_init — okay so this is the one that initializes EMC rate request tracking 💖 (yes, the whole vibe of the page lives in the Kernel API Manual, welcome bestie 🫶)

---

🌸 SYNOPSIS 🌸

void tegra_emc_rate_requests_init (struct tegra_emc_rate_requests *reqs
, struct device *dev );

That return type is void, so she gives you nothing back — just pure setup energy ✨

---

🎀 ARGUMENTS 🎀

• reqs — the struct tegra_emc_rate_requests you're initializing. This is your baby, hand her over 💅
• dev — the EMC device. The device, the moment, the icon 👑

---

🦋 DESCRIPTION 🦋

So what she actually does: initializes the rate request tracking state, and she does it with the default state — which lowkey means no active requests in there at all 🙈 Clean slate, fresh start, main character energy fr fr.

⚠️ Important bestie: you must call this before using reqs with any other functions. No skipping, no "I'll do it later" — this is the prerequisite, no cap 💀

It's giving setup-before-the-slay. Do it first, thank me later 🧚

---

⭐ SEE ALSO ⭐

• Kernel file ./drivers/memory/tegra/tegra-emc-common.c — the source, go read her 👀
• tegra_emc_set_min_rate(9)
• tegra_emc_set_max_rate(9)

These two are the ones you'll be hanging out with once reqs is initialized — squad goals 🌈

---

And that's the whole page, bestie 💜 source ./drivers/memory/tegra, dated October 2026, from the Kernel API Manual itself. Slay, read responsibly, and always init your structs before you use them 🎀✨