omap_elm_correct_data(9)

🎀 NAME 🎀

This is the omap_elm_correct_data(9) page from the Kernel API Manual, and bestie, it's giving "tiny function, very specific job." 💅

• omap_elm_correct_data — corrects page data area in case error reported.

---

✨ SYNOPSIS ✨

int omap_elm_correct_data (struct nand_chip *chip , u_char *data ,
       u_char *read_ecc , u_char *calc_ecc );

---

🦋 ARGUMENTS 🦋

Okay so it takes four things, no cap:

• chip — NAND chip object.
• data — page data.
• read_ecc — ecc read from nand flash.
• calc_ecc — ecc read from HW ECC registers.

---

🌸 DESCRIPTION 🌸

Calculated ecc vector is reported as zero in case of non-error pages. If the ecc vector is non-zero, it first filters out erased-pages, and then processes data via ELM to detect bit-flips. Literally that's the whole vibe check. ✨

Like, zero ecc vector = non-error page, reported as zero. Non-zero ecc vector = first filter out erased-pages, then process data via ELM to detect bit-flips. Facts only, bestie. 💖

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/mtd/nand/raw/omap2.c and the whole squad:

• omap_prefetch_enable(9)
• omap_nand_data_in_pref(9)
• omap_nand_data_out_pref(9)
• omap_nand_data_in_dma_pref(9)
• omap_nand_data_out_dma_pref(9)
• gen_true_ecc(9)
• omap_compare_ecc(9)
• omap_correct_data(9)
• omap_calculate_ecc(9)
• omap_enable_hwecc(9)
• omap_enable_hwecc_bch(9)
• _omap_calculate_ecc_bch(9)
• omap_calculate_ecc_bch_sw(9)
• omap_calculate_ecc_bch_multi(9)
• erased_sector_bitflips(9)
• omap_write_page_bch(9)
• omap_write_subpage_bch(9)
• omap_read_page_bch(9)
• is_elm_present(9)

---

💖 cute little sign-off moment: source/version line is ./drivers/mtd/nand/raw, the date is October 2026, and the page is omap_elm_correct_data(9). Bye bestie, go correct some page data area in case error reported! 🫶🎀