On Fri, 21 Aug 2026 10:49:13 -0300, Wagner Popov dos Santos wrote:
> The OMAP GPMC driver does not set oobavail for hardware ECC layouts.
> As a result, the NAND core does not report any OOB space available for
> automatic OOB operations such as JFFS2 cleanmarkers.
>
> Set oobavail for all hardware ECC schemes after reserving ECC bytes and
> the bad-block marker.
>
> [...]
Applied to u-boot/next, thanks!
[1/3] mtd: nand: omap_gpmc: report available OOB bytes
commit: 8abf3d9e1bcd245be51c52482238c98d4f9e6efa
[2/3] mtd: nand: omap_gpmc: fix BCH16 OOB free length
commit: f9b7c7ad77707d7e01f9cdaf61603c0e3acf4c42
[3/3] mtd: nand: omap_gpmc: preserve OOB data during BCH reads
commit: d1f43e5ede79d8045749b1d5b98f8ab6d034ecd3
--
Tom
