tegra_emc_set_max_rate(9)

✨ tegra_emc_set_max_rate(9) ✨

okay so this is a page from the Kernel API Manual bestie, and today's main character is tegra_emc_set_max_rate 💅

---

🌸 NAME 🌸

tegra_emc_set_max_rate — updates the maximum rate request for a request type 🎀

---

🦋 SYNOPSIS 🦋

int tegra_emc_set_max_rate (struct tegra_emc_rate_requests *reqs ,
unsigned long rate , enum tegra_emc_rate_request_type type );

---

💖 ARGUMENTS 💖

• reqs — the rate request tracking state, like the group chat where all the requests live 🙈
• rate — the new maximum rate in Hz that's being requested by type ⚡
• type — which type of request this is, iykyk 🌈

---

🔥 DESCRIPTION 🔥

So basically it records rate as the new maximum rate request for type, then recalculates the target rate based on all the requests (not just this one, bestie, it's a whole vibe check across the board ✨) and applies that new rate through the OPP API. slay.

---

🧚 CONTEXT 🧚

It sleeps. 😴 And requests to the same reqs are synchronized via mutex, so no chaotic overlapping energy — everything stays cute and orderly 🫶

---

👑 RETURN 👑

• 0 — success, we ate 💅
• -ERANGE — the request would cause the minimum rate request to be higher than the maximum rate request 😭 (yes that's a problem, it's giving broken vibes)
• other — setting the new rate just... failed 💀

---

🌟 SEE ALSO 🌟

• Kernel file ./drivers/memory/tegra/tegra-emc-common.c
• tegra_emc_rate_requests_init(9)
• tegra_emc_set_min_rate(9)

---

and that's the whole page, no cap 🎀 this cutie lives under ./drivers/memory/tegra, dated October 2026, and it's literally tegra_emc_set_max_rate(9) — go forth and rate-request responsibly bestie 💜🦋