spear_mtd_erase(9)

💅 NAME 💅

spear_mtd_erase — bestie, this is the one that actually erases the flash for you, exactly like the user asked 🫶

It's like, the whole point: a flash erase operation performed on behalf of the user. No cap. ✨

---

🌈 SYNOPSIS 🌈

int spear_mtd_erase (struct mtd_info *mtd , struct erase_info *e_info );

Two args in, one int out, and the flash is not the same afterward. Iconic behavior tbh 💫

---

🎀 ARGUMENTS 🎀

• mtd — the struct mtd_info *, and it's lowkey the main character here: it hands over all the memory characteristics so the function knows what it's working with 💖
• e_info — the struct erase_info *, aka the vibe check for the erase: it carries all the erase information. Everything you're asking for lives in here 📋

---

🦋 DESCRIPTION 🦋

Okay so, what it does: it erases an address range on the flash chip. That's the whole assignment and it ate 🔥

And like — important detail — that address range can span one or more erase sectors. So it's not necessarily a single-sector situation, mmkay? It can stretch across more than one 🧚

If something goes wrong while erasing, it returns an error. Not "oh well," not a silent shrug — an actual error comes back at you 😭 so go check your return value, bestie, fr fr.

⚠️ Heads up: this is erasing flash, so like... be sure you meant to do that before you do that. 🙈

---

👑 SEE ALSO 👑

Everything else in the squad, all from the kernel file ./drivers/mtd/devices/spear_smi.c:

• struct spear_smi(9)
• struct spear_snor_flash(9)
• spear_smi_read_sr(9)
• spear_smi_wait_till_ready(9)
• spear_smi_int_handler(9)
• spear_smi_hw_init(9)
• get_flash_index(9)
• spear_smi_write_enable(9)
• spear_smi_erase_sector(9)
• spear_mtd_read(9)
• spear_mtd_write(9)
• spear_smi_probe_flash(9)
• spear_smi_probe(9)
• spear_smi_remove(9)

---

That's the whole page, bestie — mwah 💋 coming to you from ./drivers/mtd/devices, dated October 2026, and yeah, spear_mtd_erase(9) said what it said 💅✨🌸