onfi_find_cl...t_nvddr_mode(9)
π 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 theconst 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 π
./drivers/mtd/nand/raw/nand_timings.cβ the kernel file, go peek at it iykyk ποΈonfi_find_closest_sdr_mode(9)β the SDR-flavored sibling π―onfi_fill_nvddr_interface_config(9)β fills in the NVDDR interface config π§onfi_fill_interface_config(9)β the general-issue interface config filler β
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
- 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