1. 13 1月, 2015 1 次提交
  2. 20 9月, 2014 3 次提交
  3. 16 9月, 2014 5 次提交
  4. 20 8月, 2014 2 次提交
  5. 15 7月, 2014 1 次提交
  6. 10 5月, 2014 1 次提交
    • B
      mtd: nand: refactor erase_cmd() to return chip status · 49c50b97
      Brian Norris 提交于
      The nand_chip::erase_cmd callback previously served a dual purpose; for
      one, it allowed a per-flash-chip override, so that AG-AND devices could
      use a different erase command than other NAND. These AND devices were
      dropped in commit 14c65786 (mtd: nand:
      remove AG-AND support). On the other hand, some drivers (denali and
      doc-g4) need to use this sort of callback to implement
      controller-specific erase operations.
      
      To make the latter operation easier for some drivers (e.g., ST's new BCH
      NAND driver), it helps if the command dispatch and wait functions can be
      lumped together, rather than called separately.
      
      This patch does two things:
       1. Pull the call to chip->waitfunc() into chip->erase_cmd(), and return
          the status from this callback
       2. Rename erase_cmd() to just erase(), since this callback does a
          little more than just send a command
      Signed-off-by: NBrian Norris <computersforpeace@gmail.com>
      Tested-by: NLee Jones <lee.jones@linaro.org>
      49c50b97
  7. 12 1月, 2014 1 次提交
  8. 04 1月, 2014 1 次提交
  9. 28 10月, 2013 2 次提交
  10. 31 8月, 2013 1 次提交
  11. 15 11月, 2012 1 次提交
  12. 07 7月, 2012 1 次提交
    • J
      mtd: nand: teach write_page and write_page_raw return an error code · fdbad98d
      Josh Wu 提交于
      There is an implemention of hardware ECC write page function which may return an
      error indication.
      For instance, using Atmel HW PMECC to write one page into a nand flash, the hardware
      engine will compute the BCH ecc code for this page. so we need read a the
      status register to theck whether the ecc code is generated.
      But we cannot assume the status register always can be ready, for example,
      incorrect hardware configuration or hardware issue, in such case we need
      write_page() to return a error code.
      
      Since the definition of 'write_page' function in struct nand_ecc_ctrl is 'void'.
      So this patch will:
        1. add return 'int' value for 'write_page' function.
        2. to be consitent, add return 'int' value for 'write_page_raw' fuctions too.
        3. add code to test the return value, and if negative, indicate an
        error happend when write page with ECC.
        4. fix the compile warning in all impacted nand flash driver.
      
      Note: I couldn't compile-test all of these easily, as some had ARCH dependencies.
      Signed-off-by: NJosh Wu <josh.wu@atmel.com>
      Signed-off-by: NArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      fdbad98d
  13. 14 5月, 2012 4 次提交
  14. 27 3月, 2012 1 次提交
    • M
      mtd: flash drivers set ecc strength · 6a918bad
      Mike Dunn 提交于
      Flash device drivers initialize 'ecc_strength' in struct mtd_info, which is the
      maximum number of bit errors that can be corrected in one writesize region.
      
      Drivers using the nand interface intitialize 'strength' in struct nand_ecc_ctrl,
      which is the maximum number of bit errors that can be corrected in one ecc step.
      Nand infrastructure code translates this to 'ecc_strength'.
      
      Also for nand drivers, the nand infrastructure code sets ecc.strength for ecc
      modes NAND_ECC_SOFT, NAND_ECC_SOFT_BCH, and NAND_ECC_NONE.  It is set in the
      driver for all other modes.
      Signed-off-by: NMike Dunn <mikedunn@newsguy.com>
      Signed-off-by: NArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      6a918bad
  15. 11 9月, 2011 4 次提交
  16. 25 5月, 2011 5 次提交
  17. 31 3月, 2011 1 次提交
  18. 25 10月, 2010 1 次提交
  19. 12 8月, 2010 4 次提交