STRUCT HYNIX_READ_RETRY(9)

👑 struct hynix_read_retry(9) — read-retry data, bestie

okay so this is a page from the Kernel API Manual, and it's all about struct hynix_read_retry — literally just the lil container that holds read-retry data ✨ no cap, that's the whole vibe.

---

🌸 NAME

struct hynix_read_retry — read-retry data 💅

---

🎀 SYNOPSIS

here's the whole struct, bestie, copy it exactly bestie:

struct hynix_read_retry {
    int nregs;
    const u8 *regs;
    u8 values[];
 };

it's giving very demure, very mindful, very "three fields and we're done" 🦋

---

💖 Members

ok so let's meet the cast 💖

• nregs — the number of register to set when you're applying a new read-retry mode. that's it, that's the count. 🙈
• regs — the register offsets. and heads up, these are NAND chip dependent, so don't go assuming they're the same everywhere, iykyk 🔥
• values — an array of values to set in registers. and the size?? the array size is equal to (nregs * nmodes) — literally just multiply, bestie, the math is mathing 🧮✨

---

🦋 SEE ALSO

go look at these, they're all iconic in their own way 👑

• Kernel file ./drivers/mtd/nand/raw/nand_hynix.c
• struct hynix_nand(9)
• struct hynix_read_retry_otp(9)
• hynix_get_majority(9)

---

fr fr tho, if you forget nmodes when you're sizing values, that's on you and not on me 💀 (nregs * nmodes) — write it down. 🍓

---

and that's the page!! 🫶 huge slay to ./drivers/mtd/nand/raw for being the source, and mark your calendars for October 2026 bestie, that's the date on this one 🌈⭐ mwah, go read the manpage again 💜