[PATCH 5/7] add GPMI support for imx28
liu.h.jason at gmail.com
Thu Mar 24 04:26:37 EDT 2011
2011/3/24 Lothar Waßmann <LW at karo-electronics.de>:
>> Most of the time, the timing is really based on a safe timing setting.
>> But in the original GPMI driver in the FREESCALE BSP, there exits some
>> nands need to be set with their own timing setting.
>> So I do not use the safe timing for _ALL_ the nand, and i'd better get
>> it from the
> It should be sufficient to provide timing info from platform_data in
> special cases instead of bloating the nand id database with that
> stuff. Platforms might need to adjust the timing because of
> peculiarities in the HW. Thus the timing info should be provided from
> there, not from the chip database.
No, we can't. since some boards only provide one NAND socket, customer
can place any NAND flash chip they want. And with the NAND tech evolution, some
NAND flash will end-of-line and customer need change another new NAND.
As we all know that RAW NAND flash vendor does not follow the same
rule to encode
ID related information such as page size/oob size/block size etc. Even
with same vendor,
take Sumsung as example, there is not one generic rule to encode the
If you do NAND support with many customers, you will find that
currenly linux NAND driver
(nand_base.c/nand_ids.c) provide very poor support for that.
> Lothar Waßmann
> Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen
> Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
> Geschäftsführer: Matthias Kaussen
> Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
> www.karo-electronics.de | info at karo-electronics.de
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
More information about the linux-mtd