spi_nor_spimem_check_readop(9)
π
spi_nor_spimem_check_readop β Kernel API Manual β¨
okay bestie, settle in, because this one is literally a vibe check for a read operation πΈ β we're looking at spi_nor_spimem_check_readop(9) from the Kernel API Manual, and no cap, it's short but it's important.
β¨ NAME β¨
spi_nor_spimem_check_readop β checks whether this read op is actually supported by the controller π«Ά
π SYNOPSIS π
int spi_nor_spimem_check_readop (struct spi_nor *nor , const struct
spi_nor_read_command *read );
like, that's the whole signature, and yes it returns an int π
π ARGUMENTS π
norβ pointer to astruct spi_norπ¦ (your NOR flash boy, the main character)readβ pointer to the op template that's getting checked π (this is the thing under review, the one on trial)
π₯ DESCRIPTION π₯
Returns 0 if the operation is supported, and -EOPNOTSUPP otherwise π
that's it. that's the whole description. it's giving "small function, big responsibility" and honestly? iconic π
ngl the vibes here are very "yes or no, no in-between" β you get0(slay, supported) or-EOPNOTSUPP(nope, not supported). no other options, periodt π
π SEE ALSO π
this list is long long, so buckle up bestie, we're going through all of them in order, fr fr π§:
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_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_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 where does all this live? in the kernel file ./drivers/mtd/spi-nor/core.c π go read it, iykyk π
okay that's the whole page bestie!! πβ¨ this gem is from the ./drivers/mtd/spi-nor source, dated October 2026, and it's spi_nor_spimem_check_readop(9) forever and always ππ¦ go forth and check those read ops, mwah π
π¦ 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