onfi_find_cl...t_nvddr_mode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… onfi_find_closest_nvddr_mode(9) β€” the Kernel API Manual ✨

okay so bestie, welcome to the glow-up of the Kernel API Manual page for onfi_find_closest_nvddr_mode(9). it's short, it's sweet, and it's literally about picking the vibes-closest timing mode. let's get into it πŸŽ€


🌸 NAME 🌸

onfi_find_closest_nvddr_mode β€” derive the closest ONFI NVDDR timing mode given a set of timings ✨

like, you hand it some timings and it goes "okay bestie, which NVDDR mode is the closest match?" and slays the answer back at you. no cap. πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

unsigned int onfi_find_closest_nvddr_mode (const struct
nand_nvddr_timings *spec_timings );

it returns an unsigned int, take that in for a sec. 🌈


πŸŽ€ ARGUMENTS πŸŽ€

  • spec_timings β€” the timings to challenge πŸ”₯ this is the const struct nand_nvddr_timings * you're putting on the spot. it's giving "main character energy" β€” the whole function is basically judging these timings against the mode lineup. the timings to challenge, periodt. πŸ’…

πŸ’œ SEE ALSO πŸ’œ


a lil heads-up bestie: this page is literally just NAME, SYNOPSIS, ARGUMENTS and SEE ALSO β€” no deep-lore DESCRIPTION section, so don't come for me, i'm not inventing extra lore fr fr πŸ™ˆ

and that's the whole page, bestie! 🫢 cute lil sign-off time: this one lives over in ./drivers/mtd/nand/raw 🌸 dated October 2026 πŸ’– and it's filed under onfi_find_cl...t_nvddr_mode(9) β€” the truncated man-page name is iconic in a cursed kind of way, ngl πŸ˜­πŸ’€ go forth and find the closest mode, you absolute legend πŸ‘‘βœ¨

πŸ“¦ where this page comes from