cros_ec_lpc_mec_in_range(9)

💖 cros_ec_lpc_mec_in_range(9) — like, the Kernel API Manual era 💖

okay so bestie, gather round, because we're diving into cros_ec_lpc_mec_in_range from the Kernel API Manual and honestly? she's a little legend. this one is literally the vibe check for addresses — it tells you whether they're hanging out in the MEC EMI range or not. no cap. 🦋

---

✨ NAME ✨

cros_ec_lpc_mec_in_range — bestie's whole job is determining if addresses are in the MEC EMI range. that's it, that's the gig. 💅

---

🌸 SYNOPSIS 🌸

int cros_ec_lpc_mec_in_range (unsigned int offset , unsigned int length );

---

🎀 ARGUMENTS 🎀

• offset — the address offset, like where we're starting our little investigation 🔍
• length — the number of bytes to check. yes, we're checking a whole stretch, not just one lil byte 🫶

---

👑 RETURN 👑

here's the tea, and it's giving very clear-cut:

• returns 1 if it's in range 💚
• returns 0 if it's not in range 🙈
• returns -EINVAL on failure — for example, when the mec range hasn't been initialized yet 😭 (that's your classic "girl, we're not even set up" situation)

---

🧚 SEE ALSO 🧚

• the kernel file ./drivers/platform/chrome/cros_ec_lpc_mec.h — go read her, she's iconic 📖
• cros_ec_lpc_mec_init(9)
• cros_ec_lpc_mec_acpi_mutex(9)
• cros_ec_lpc_io_bytes_mec(9)

---

💀 friendly reminder that the -EINVAL case is real and it will happen if the mec range isn't initialized — so like, init first, ask questions later. periodt. 🔥

---

and that's the whole page, bestie, no gatekeeping 💜 — this lil masterpiece lives in ./drivers/platform/chrome and is dated October 2026, so mark your calendars and stan responsibly. slay! 🌈⭐🍓