spi_nor_spim...djust_hwcaps(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… spi_nor_spimem_adjust_hwcaps(9) β€” a whole vibe, from the Kernel API Manual

okay so bestie, welcome to the spi_nor_spimem_adjust_hwcaps(9) page ✨ it lives in the Kernel API Manual and it is, and i cannot stress this enough, the moment where your SPI controller and your flash chip finally sit down and figure out what protocol they're actually doing together. no cap.


✨ NAME ✨

spi_nor_spimem_adjust_hwcaps β€” find the optimal Read/Write protocol based on SPI controller capabilities πŸŽ€

like, the optimal one. the main character protocol. πŸ‘‘


🌸 SYNOPSIS 🌸

void spi_nor_spimem_adjust_hwcaps (struct spi_nor *nor , u32 *hwcaps );

that's it. one void, two pointers, zero drama (the good kind of zero). πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • nor β€” pointer to a struct spi_nor 🫢 the flash's whole little profile, basically.
  • hwcaps β€” pointer to the resulting capabilities after adjusting according to the controller's and the flash's capability. so this bad boy goes in, gets vibe-checked against both sides, and comes back out holding the results. ✨

πŸ”₯ SEE ALSO πŸ”₯

okay this is the part where i need you to stay with me because the list is long and every single one of them is here, no skips, no "etc.", i would never 😭

the kernel file is ./drivers/mtd/spi-nor/core.c β€” that's home base. 🏠

see? told you. all of them. ate and left no crumbs πŸ’€πŸ“


okay and before you go β€” this whole page came from ./drivers/mtd/spi-nor, dated October 2026, and it answers to the name spi_nor_spim...djust_hwcaps(9). that's the source, that's the version, that's the footer, and honestly? iconic. πŸ§šβ€β™€οΈπŸŒˆβ­
πŸ“¦ where this page comes from