onenand_read_ops_nolock(9)

💅 NAME 💅

Hii bestie 💖 welcome to the Kernel API Manual page for onenand_read_ops_nolock(9). The title is literally right there, and the NAME section is giving:

onenand_read_ops_nolock - [OneNAND Interface] OneNAND read main and/or out-of-band

---

✨ SYNOPSIS ✨

No cap, here's the exact signature — don't come for me about the spacing, it's copied character for character:

int onenand_read_ops_nolock (struct mtd_info *mtd , loff_t from , struct
mtd_oob_ops *ops );

---

🎀 ARGUMENTS 🎀

• mtd — MTD device structure. That's the device baddie this whole thing hangs off of.
• from — offset to read from. Like, where in the data are we starting? This is the spot.
• ops — oob operation description structure. The little descriptor that says what the out-of-band operation is doing.

---

🦋 DESCRIPTION 🦋

OneNAND read main and/or out-of-band data.

That's the whole description, and honestly? Iconic minimalism. It reads main data, out-of-band data, or both — main and/or out-of-band is right there in the NAME and the DESCRIPTION, so we're not inventing anything extra. Periodt 💅

---

🌈 SEE ALSO 🌈

The kernel file is ./drivers/mtd/nand/onenand/onenand_base.c, and the full SEE ALSO friend group is:

• 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_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_block_by_block_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)

---

mwah 💋✨ — source/version: ./drivers/mtd/nand/onenand; date: October 2026. That's the whole page, ily, bye! 🫶