onenand_bloc..._block_erase(9)

💅 NAME 💅

onenand_block_by_block_erase — okay so this is the [INTERN] one, meaning it's an internal helper, not your everyday public-facing bestie ✨ and what it does is erase block(s) using good old regular erase 🧚

(this page lives in the Kernel API Manual, section 9, and the page itself is onenand_bloc..._block_erase(9) — yes the title is truncated with dots, that's just how the header renders it, no cap 💀)

✨ SYNOPSIS ✨

int onenand_block_by_block_erase (struct mtd_info *mtd , struct
     erase_info *instr , struct mtd_erase_region_info *region , unsigned int
     block_size );

🎀 ARGUMENTS 🎀

• mtd — the MTD device structure 🫶 like, the device itself, the main character
• instr — the erase instruction 💌
• region — the erase region 🌸
• block_size — the erase block size, literally the size of the block you're erasing 👑

🦋 DESCRIPTION 🦋

It erases one or more blocks, and it does it one block at a time 💅 like, individually, block by block, that's the whole vibe — no mass multiblock situation here, just steady one-at-a-time energy ✨

🔥 SEE ALSO 🔥

Okay bestie, buckle up, this list is long — but every single one is here because we do not skip 💖 It's the kernel file ./drivers/mtd/nand/onenand/onenand_base.c and then:

onenand_readw(9), onenand_writew(9), onenand_block_address(9), onenand_bufferram_address(9), onenand_page_address(9), onenand_buffer_address(9), flexonenand_block(9), flexonenand_addr(9), onenand_get_density(9), flexonenand_region(9), onenand_command(9), onenand_read_ecc(9), onenand_wait(9), onenand_bufferram_offset(9), onenand_read_bufferram(9), onenand_sync_read_bufferram(9), onenand_write_bufferram(9), onenand_get_2x_blockpage(9), onenand_check_bufferram(9), onenand_update_bufferram(9), onenand_invalidate_bufferram(9), onenand_get_device(9), onenand_release_device(9), onenand_transfer_auto_oob(9), onenand_recover_lsb(9), onenand_mlc_read_ops_nolock(9), onenand_read_ops_nolock(9), onenand_read_oob_nolock(9), onenand_read_oob(9), onenand_bbt_wait(9), onenand_bbt_read_oob(9), onenand_verify_oob(9), onenand_verify(9), onenand_panic_write(9), onenand_fill_auto_oob(9), onenand_write_ops_nolock(9), onenand_write_oob_nolock(9), onenand_write_oob(9), onenand_block_isbad_nolock(9), onenand_multiblock_erase(9), onenand_erase(9), onenand_sync(9), onenand_block_isbad(9), onenand_default_block_markbad(9), onenand_block_markbad(9), onenand_do_lock_cmd(9), onenand_lock(9), onenand_unlock(9), onenand_check_lock_status(9), onenand_unlock_all(9), onenand_otp_command(9), onenand_otp_write_oob_nolock(9), do_otp_read(9), do_otp_write(9), do_otp_lock(9), onenand_otp_walk(9), onenand_get_fact_prot_info(9), onenand_read_fact_prot_reg(9), onenand_get_user_prot_info(9), onenand_read_user_prot_reg(9), onenand_write_user_prot_reg(9), onenand_lock_user_prot_reg(9), onenand_check_features(9), onenand_print_device_info(9), onenand_check_maf(9), flexonenand_get_boundary(9), flexonenand_get_size(9), flexonenand_check_blocks_erased(9), onenand_chip_probe(9), onenand_probe(9), onenand_suspend(9), onenand_resume(9), onenand_scan(9), onenand_release(9)

and that's the whole page, periodt 💅✨ This cutie came from ./drivers/mtd/nand/onenand and it's dated October 2026 — like, future vibes, the page is literally from the future 🦋👑 mwah, love that for us 💖