diff options
author | Brian Norris <computersforpeace@gmail.com> | 2011-05-31 23:31:21 (GMT) |
---|---|---|
committer | Artem Bityutskiy <artem.bityutskiy@intel.com> | 2011-09-11 12:01:56 (GMT) |
commit | 5fb1549dfc40f3b589dae560ea21535cdc5f64e0 (patch) | |
tree | 8449037cb13d3453201950ffaadd65de60cf9399 /arch/arm/mach-davinci/board-dm355-leopard.c | |
parent | a0dc552951dcbb2b28a8a2ffb5fa966613e8c025 (diff) | |
download | linux-5fb1549dfc40f3b589dae560ea21535cdc5f64e0.tar.xz |
mtd: nand: separate chip options / bbt_options
This patch handles the problems we've been having with using conflicting
flags from nand.h and bbm.h in the same nand_chip.options field. We
should try to separate these two spaces a little more clearly, and so I
have added a bbt_options field to nand_chip.
Important notes about nand_chip fields:
* bbt_options field should contain ONLY flags from bbm.h. They should be
able to pass safely to a nand_bbt_descr data structure.
- BBT option flags start with the "NAND_BBT_" prefix.
* options field should contian ONLY flags from nand.h. Ideally, they
should not be involved in any BBT related options.
- NAND chip option flags start with the "NAND_" prefix.
* Every flag should have a nice comment explaining what the flag is. While
this is not yet the case on all existing flags, please be sure to write
one for new flags. Even better, you can help document the code better
yourself!
Please try to follow these conventions to make everyone's lives easier.
Among the flags that are being moved to the new bbt_options field
throughout various drivers, etc. are:
* NAND_BBT_SCANLASTPAGE
* NAND_BBT_SCAN2NDPAGE
and there will be more to come.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'arch/arm/mach-davinci/board-dm355-leopard.c')
0 files changed, 0 insertions, 0 deletions