diff options
author | Huang Shijie <b32955@freescale.com> | 2013-03-15 11:00:59 +0800 |
---|---|---|
committer | David Woodhouse <David.Woodhouse@intel.com> | 2013-04-05 13:20:29 +0100 |
commit | f22d5f638b0ea40e7cceb4639a608bd2c3eff97c (patch) | |
tree | b9966f6920cf6da5273866685cd734ebf2faad90 /drivers/mtd | |
parent | bd247acb77b7a3dcb1075d7c9f09bc46bd242f3b (diff) | |
download | op-kernel-dev-f22d5f638b0ea40e7cceb4639a608bd2c3eff97c.zip op-kernel-dev-f22d5f638b0ea40e7cceb4639a608bd2c3eff97c.tar.gz |
mtd: add new fields to nand_flash_dev{}
As time goes on, we begin to meet the situation that we can not get enough
information from some nand chips's id data. Take some Toshiba's nand chips
for example. I have 4 Toshiba's nand chips in my hand:
TC58NVG2S0F, TC58NVG3S0F, TC58NVG5D2, TC58NVG6D2
When we read these chips' datasheets, we will get the geometry of these chips:
TC58NVG2S0F : 4096 + 224
TC58NVG3S0F : 4096 + 232
TC58NVG5D2 : 8192 + 640
TC58NVG6D2 : 8192 + 640
But we can not parse out the correct oob size for these chips from the id data.
This patch adds some new fields to the nand_flash_dev{}:
@id_len: the valid length of the id data. See the comments in
nand_id_has_period()
@oobsize: the oob size.
Signed-off-by: Huang Shijie <b32955@freescale.com>
Reviewed-by: Brian Norris <computersforpeace@gmail.com>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'drivers/mtd')
0 files changed, 0 insertions, 0 deletions