doc_set_extra_page_mode(9)

💖 doc_set_extra_page_mode(9) 💖

okay bestie, this little icon is straight from the Kernel API Manual, and the vibe is “let’s go poke the flash page layout.” ✨

🌸 NAME 🌸

doc_set_extra_page_mode — change flash page layout 🎀

✨ SYNOPSIS ✨

int doc_set_extra_page_mode (struct docg3 *docg3 );

🎀 ARGUMENTS 🎀

• docg3 — the device 💻

💅 DESCRIPTION 💅

okay so normally, the flash page is split into the data (512 bytes) and the out of band data (16 bytes). 🫶 For each one, 4 more bytes can be accessed — and that’s literally where the wear leveling counters are stored. 👑

to access this last area of 4 bytes, a special mode must be input to the flash ASIC. that’s the whole assignment, no cap. 💅

and the return tea ☕: returns 0 if no error occurred, -EIO else. periodt. ✨

🦋 SEE ALSO 🦋

Kernel file ./drivers/mtd/devices/docg3.c — and here’s the whole friend group, all linked:

• doc_delay(9)
• doc_read_data_area(9)
• doc_write_data_area(9)
• doc_set_reliable_mode(9)
• doc_set_asic_mode(9)
• doc_set_device_id(9)
• doc_setup_addr_sector(9)
• doc_setup_writeaddr_sector(9)
• doc_read_seek(9)
• doc_write_seek(9)
• doc_read_page_ecc_init(9)
• doc_write_page_ecc_init(9)
• doc_ecc_disable(9)
• doc_hamming_ecc_init(9)
• doc_ecc_bch_fix_data(9)
• doc_read_page_prepare(9)
• doc_read_page_getbytes(9)
• doc_write_page_putbytes(9)
• doc_get_bch_hw_ecc(9)
• doc_page_finish(9)
• doc_read_page_finish(9)
• calc_block_sector(9)
• doc_read_oob(9)
• doc_block_isbad(9)
• doc_get_erase_count(9)
• doc_get_op_status(9)
• doc_write_erase_wait_status(9)
• doc_erase_block(9)
• doc_erase(9)
• doc_write_page(9)
• doc_guess_autoecc(9)
• doc_fill_autooob(9)
• doc_backup_oob(9)
• doc_write_oob(9)
• doc_set_driver_info(9)
• doc_probe_device(9)
• doc_release_device(9)
• docg3_resume(9)
• docg3_suspend(9)
• docg3_probe(9)
• docg3_release(9)

mwah 💋 source/version + date sign-off: ./drivers/mtd/devices · October 2026 · doc_set_extra_page_mode(9). bye bestie 🫶✨