[PATCH 3/3] omap3 nand : use NAND_BUSWIDTH_AUTO
tony at atomide.com
Tue Nov 6 13:40:20 EST 2012
* Matthieu CASTET <matthieu.castet at parrot.com> [121106 08:49]:
> Igor Grinberg a écrit :
> > Cc: Tony Lindgren, Afzal Mohammed,
> > On 11/06/12 12:51, Matthieu CASTET wrote:
> >> This allow to clean the omap nand driver that were trying in x8 and x16 bits mode.
> >> This also make work onfi detection on beagleboard :
> >> Before :
> >> [ 1.954803] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit), page size: 2048, OOB size: 64
> >> After :
> >> [ 1.914825] ONFI param page 0 valid
> >> [ 1.919158] ONFI flash detected
> >> [ 1.922515] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron MT29F2G16ABD), page size: 2048, OOB size: 64
> >> platform data devsize is renamed bussize. It now indicate the maximun size of the nand bus.
> >> Signed-off-by: Matthieu CASTET <matthieu.castet at parrot.com>
> > I think, you should base on one of Tony's branches with that kind of patches.
> > Because, for example the omap_nand_flash_init() function does not exist anymore
> > in Tony's master and may be several more things will need to have adjustments.
> > Also, the GPMC related stuff inside the NAND driver
> > should probably be coordinated with Afzal, as he is reworking the whole
> > GPMC related code.
> Thanks for the info.
> Where such tree could be found ?
You should be able to use omap-for-v3.8/cleanup-headers-gpmc
branch as a base for your patches .
Eventually once when we're done with all the clean up, the MTD
driver should be completely separated from the core omap code
and I'll be out of the way.
More information about the linux-mtd