[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <336aece6-33a0-e528-1d54-17d0d3c38624@ti.com>
Date: Tue, 8 Dec 2020 21:41:21 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Pratyush Yadav <p.yadav@...com>,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
<linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/3] mtd: spi-nor: core: Allow flashes to specify MTD
writesize
Hi Pratyush,
On 12/1/20 3:57 PM, Pratyush Yadav wrote:
> Some flashes like the Cypress S28 family use ECC. Under this ECC scheme,
> multi-pass writes to an ECC block is not allowed. In other words, once
> data is programmed to an ECC block, it can't be programmed again without
> erasing it first.
>
> Upper layers like file systems need to be given this information so they
> do not cause error conditions on the flash by attempting multi-pass
> programming. This can be done by setting 'writesize' in 'struct
> mtd_info'.
>
> Set the default to 1 but allow flashes to modify it in fixup hooks. If
> more flashes show up with this constraint in the future it might be
> worth it to add it to 'struct flash_info', but for now increasing its
> size is not worth it.
>
> Signed-off-by: Pratyush Yadav <p.yadav@...com>
> Reviewed-by: Tudor Ambarus <tudor.ambarus@...rochip.com>
> ---
>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
spi-nor/next, thanks!
[2/3] mtd: spi-nor: core: Allow flashes to specify MTD writesize
https://git.kernel.org/mtd/c/afd473e858
Regards
Vignesh
Powered by blists - more mailing lists