spi_nor_write_sr(9)
π spi_nor_write_sr β like, the Status Register glow-up
okay so bestie, this is a page from the Kernel API Manual (yes, the kernel has lore too) and it's all about spi_nor_write_sr(9) β the little function that writes the Status Register. periodt.
β¨ NAME β¨
spi_nor_write_sr β Write the Status Register. that's it, that's the whole vibe π
πΈ SYNOPSIS πΈ
int spi_nor_write_sr (struct spi_nor *nor , const u8 *sr , size_t len );
like look at her. three args, returns an int. main character energy fr.
π¦ ARGUMENTS π¦
norβ pointer to'struct spi_nor'. this is your spi_nor bestie, the whole context of the operation π«Άsrβ pointer to a DMA-able buffer to write to the Status Register. emphasis on DMA-able, okay? don't come at her with just any random buffer πlenβ number of bytes to write to the Status Register. how much you're giving her, basically β¨
π RETURN π
0 on success, -errno otherwise. so like, zero means slay, negative means the kernel is telling you exactly what went wrong π
π SEE ALSO π
the kernel file lives at ./drivers/mtd/spi-nor/core.c and honestly the whole friend group is here β 62 functions deep, no cap. go say hi π:
spi_nor_get_cmd_ext(9)spi_nor_spimem_setup_op(9)spi_nor_spimem_bounce(9)spi_nor_spimem_exec_op(9)spi_nor_spimem_read_data(9)spi_nor_read_data(9)spi_nor_spimem_write_data(9)spi_nor_write_data(9)spi_nor_read_any_reg(9)spi_nor_write_any_volatile_reg(9)spi_nor_write_enable(9)spi_nor_write_disable(9)spi_nor_read_id(9)spi_nor_read_sr(9)spi_nor_read_cr(9)spi_nor_set_4byte_addr_mode_en4b_ex4b(9)spi_nor_set_4byte_addr_mode_wren_en4b_ex4b(9)spi_nor_set_4byte_addr_mode_brwr(9)spi_nor_sr_ready(9)spi_nor_use_parallel_locking(9)spi_nor_ready(9)spi_nor_wait_till_ready_with_timeout(9)spi_nor_wait_till_ready(9)spi_nor_global_block_unlock(9)spi_nor_write_sr1_and_check(9)spi_nor_write_16bit_sr_and_check(9)spi_nor_write_16bit_cr_and_check(9)spi_nor_write_16bit_sr_cr_and_check(9)spi_nor_write_sr_and_check(9)spi_nor_write_sr_cr_and_check(9)spi_nor_write_sr2(9)spi_nor_read_sr2(9)spi_nor_erase_die(9)spi_nor_div_by_erase_size(9)spi_nor_find_best_erase_type(9)spi_nor_init_erase_cmd(9)spi_nor_destroy_erase_cmd_list(9)spi_nor_init_erase_cmd_list(9)spi_nor_erase_multi_sectors(9)spi_nor_sr1_bit6_quad_enable(9)spi_nor_sr2_bit1_quad_enable(9)spi_nor_sr2_bit7_quad_enable(9)spi_nor_spimem_check_read_pp_op(9)spi_nor_spimem_check_readop(9)spi_nor_spimem_check_pp(9)spi_nor_spimem_adjust_hwcaps(9)spi_nor_set_erase_type(9)spi_nor_mask_erase_type(9)spi_nor_init_uniform_erase_map(9)spi_nor_select_uniform_erase(9)spi_nor_manufacturer_init_params(9)spi_nor_no_sfdp_init_params(9)spi_nor_init_flags(9)spi_nor_init_fixup_flags(9)spi_nor_late_init_params(9)spi_nor_sfdp_init_params_deprecated(9)spi_nor_init_params_deprecated(9)spi_nor_init_default_params(9)spi_nor_init_params(9)spi_nor_quad_enable(9)spi_nor_set_4byte_addr_mode(9)spi_nor_soft_reset(9)
lowkey the whole spi_nor family eats and leaves no crumbs π read them in order, iykyk.
and that's the page!! this one came from ./drivers/mtd/spi-nor and it's stamped October 2026 β so like, future-era kernel wisdom π mwah, go write that Status Register 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