nand_sync(9)
π nand_sync(9) β the kernel API manual, but make it make sense π
okay so bestie, we're in section 9 of the Kernel API Manual, and today's main character is nand_sync. it lives in ./drivers/mtd/nand/raw/nand_base.c, it's part of the [MTD Interface], and honestly? it's a vibe. let's get into it β¨
πΈ NAME πΈ
nand_sync β the [MTD Interface] sync. that's it, that's the name, and she's serving exactly what the label says π
π¦ SYNOPSIS π¦
void nand_sync (struct mtd_info *mtd );
no return value, one argument, zero drama. she takes her pointer and she goes π
π ARGUMENTS π
mtdβ the MTD device structure. like, the actual MTD device. hand it yourstruct mtd_info *and you're genuinely set π«Ά
β¨ DESCRIPTION β¨
okay so here's the tea π₯ "sync" sounds all fancy and synchronization-y, right? nope. bestie, sync here is actually just a wait for chip ready function. that's the whole personality. it waits for the chip to be ready. no cap. it's giving "the function name is aspirational, the function body is a vibe check" π
π SEE ALSO π
the friend group is LARGE and we love every single one of them, so here's the full squad, no one left out π
nand_extract_bits(9),nand_select_target(9),nand_deselect_target(9),nand_release_device(9)nand_bbm_get_next_page(9),nand_block_bad(9),nand_region_is_secured(9),nand_get_device(9)nand_check_wp(9),nand_fill_oob(9),nand_do_write_oob(9),nand_default_block_markbad(9)nand_markbad_bbm(9),nand_block_markbad_lowlevel(9),nand_block_isreserved(9),nand_block_checkbad(9)nand_soft_waitrdy(9),nand_gpio_waitrdy(9),panic_nand_wait(9),nand_reset_interface(9)nand_setup_interface(9),nand_choose_best_sdr_timings(9),nand_choose_best_nvddr_timings(9),nand_choose_best_timings(9)nand_choose_interface_config(9),nand_fill_column_cycles(9),nand_read_page_op(9),nand_read_param_page_op(9)nand_change_read_column_op(9),nand_read_oob_op(9),nand_prog_page_begin_op(9),nand_prog_page_end_op(9)nand_prog_page_op(9),nand_change_write_column_op(9),nand_readid_op(9),nand_status_op(9)nand_exit_status_op(9),nand_erase_op(9),nand_set_features_op(9),nand_get_features_op(9)nand_reset_op(9),nand_read_data_op(9),nand_write_data_op(9),struct nand_op_parser_ctx(9)nand_op_parser_must_split_instr(9),nand_op_parser_match_pat(9),nand_op_parser_exec_op(9)nand_subop_get_addr_start_off(9),nand_subop_get_num_addr_cyc(9),nand_subop_get_data_start_off(9),nand_subop_get_data_len(9)nand_reset(9),nand_get_features(9),nand_set_features(9)nand_read_page_raw_notsupp(9),nand_read_page_raw(9),nand_monolithic_read_page_raw(9),nand_read_page_raw_syndrome(9)nand_read_page_swecc(9),nand_read_subpage(9),nand_read_page_hwecc(9),nand_read_page_hwecc_oob_first(9)nand_read_page_syndrome(9),nand_transfer_oob(9),nand_setup_read_retry(9),nand_do_read_ops(9)nand_read_oob_std(9),nand_read_oob_syndrome(9),nand_write_oob_std(9),nand_write_oob_syndrome(9)nand_do_read_oob(9),nand_read_oob(9)nand_write_page_raw_notsupp(9),nand_write_page_raw(9),nand_monolithic_write_page_raw(9),nand_write_page_raw_syndrome(9)nand_write_page_swecc(9),nand_write_page_hwecc(9),nand_write_subpage_hwecc(9),nand_write_page_syndrome(9)nand_write_page(9),nand_do_write_ops(9),panic_nand_write(9),nand_write_oob(9)nand_erase(9),nand_erase_nand(9),nand_block_isbad(9),nand_block_markbad(9)nand_suspend(9),nand_resume(9),nand_shutdown(9),nand_lock(9),nand_unlock(9)rawnand_dt_parse_gpio_cs(9),nand_scan_ident(9),nand_check_ecc_caps(9),nand_match_ecc_req(9)nand_maximize_ecc(9),nand_ecc_choose_conf(9),nand_scan_tail(9),nand_scan_with_ids(9),nand_cleanup(9)
like I said. huge friend group. all iconic π
also go read the source itself at ./drivers/mtd/nand/raw/nand_base.c β iykyk π
π§ sign-off π§
this little page is brought to you by the fine people hanging out in ./drivers/mtd/nand/raw, stamped October 2026, and filed under nand_sync(9). read her, love her, wait for that chip to be ready bestie ππβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms