spi_nor_write_sr1_and_check(9)
π spi_nor_write_sr1_and_check(9) β Kernel API Manual, bestie edition β¨
okay so picture this: you're deep in the Linux kernel, specifically the SPI-NOR flash situation in ./drivers/mtd/spi-nor, and you need to write exactly one lil byte into Status Register 1 β and then, and this is the main character part, verify that the byte the chip sent back actually matches what you wrote. no cap, that's the whole gig. π
β¨ NAME β¨
spi_nor_write_sr1_and_check β writes one byte to the Status Register 1 and then makes sure that byte matches the value it got back. like, accountability queen behavior π
πΈ SYNOPSIS πΈ
int spi_nor_write_sr1_and_check (struct spi_nor *nor , u8 sr1 );
π¦ ARGUMENTS π¦
norβ a pointer to astruct spi_nor. yeah. that one. the whole flash device situation, right there π«Άsr1β the byte value you want written to the Status Register. one byte. that's it. iconic of it honestly β
π RETURN π
Returns 0 on success, or -errno otherwise. so like, zero means slay, anything negative means the universe said no π
π SEE ALSO π
bestie the friend group here is huge, so buckle in π β all of these live in the Kernel file ./drivers/mtd/spi-nor/core.c:
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_sr(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)
and that's the whole page, bestie!! go forth and write that one byte, then check it. we love a function with trust issues π
sign-off era: this cutie came out of ./drivers/mtd/spi-nor, dated October 2026 β same vibes, same facts, streamed straight from the Kernel API Manual πβ¨
π¦ 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