Hi Peter,
On Tue, Jul 07, 2015 at 06:02:52AM +, Peter Pan 潘栋 (peterpandong) wrote:
> Currently nand_bbt.c is tied with struct nand_chip, and it makes other
> NAND family chips hard to use nand_bbt.c. Maybe it's the reason why
> onenand has own bbt(onenand_bbt.c).
>
> Parameterize a few releva
Hi Peter,
Thank you for your work on this and for considering my suggestions on the code.
This BBT patch is a very good base for the SPI NAND framework work (which will
separate the SPI NAND core from the existing parallel NAND core).
I applied it on the 4.1 kernel and tested it with a GigaDevice
Currently nand_bbt.c is tied with struct nand_chip, and it makes other
NAND family chips hard to use nand_bbt.c. Maybe it's the reason why
onenand has own bbt(onenand_bbt.c).
Parameterize a few relevant device detail information into a new
nand_bbt struct, and set some hooks for chip specified par
3 matches
Mail list logo