nanddev_mtd_erase(9)

✨ nanddev_mtd_erase(9) ✨

okay bestie, welcome to the Kernel API Manual 💅 — we're doing the nanddev_mtd_erase(9) page today and honestly? it's a little icon, a tiny helper with big main character energy 🎀

---

✨ NAME ✨

nanddev_mtd_erase — the generic mtd->_erase() implementation for NAND devices, no cap 🦋

---

🌸 SYNOPSIS 🌸

int nanddev_mtd_erase (struct mtd_info *mtd , struct erase_info *einfo );

---

💖 ARGUMENTS 💖

• mtd — the MTD device, literally the thing we're erasing stuff on 🫶
• einfo — the erase request itself, like the lil form you fill out to say "erase this pls" ✨

---

🦋 DESCRIPTION 🦋

so this is a simple mtd->_erase implementation — it just loops over all the blocks that einfo is concerned with and calls nand->ops->erase on each one of them 🎀 lowkey does exactly what it says on the tin, and it ate 💅

⚠️ okay listen up, this part MATTERS: do not directly assign mtd->_erase to this helper, because there's no locking in here 😭 like none. zero. Not the vibe.

NAND specialized layers should instead implement their own wrapper around nanddev_mtd_erase, taking the appropriate lock before calling nanddev_mtd_erase 👑 that's the way, fr fr.

---

🌈 RETURN 🌈

0 in case of success, and a negative error code otherwise 🍓 (yes, that's the whole bit — short and sweet, iykyk)

---

⭐ SEE ALSO ⭐

Kernel file ./drivers/mtd/nand/core.c — go read it, it's giving lore 🧚

• nand_check_erased_buf(9)
• nand_check_erased_ecc_chunk(9)
• nanddev_isbad(9)
• nanddev_markbad(9)
• nanddev_isreserved(9)
• nanddev_erase(9)
• nanddev_mtd_max_bad_blocks(9)
• nanddev_get_ecc_engine(9)
• nanddev_put_ecc_engine(9)
• nanddev_find_ecc_configuration(9)
• nanddev_ecc_engine_init(9)
• nanddev_ecc_engine_cleanup(9)
• nanddev_init(9)
• nanddev_cleanup(9)

---

mwah 💜 that's the whole page — brought to you by ./drivers/mtd/nand, dated October 2026, and yes she's serving kernel-manual realness till the very last line 🎀✨