1. 20 9月, 2009 1 次提交
  2. 06 6月, 2009 3 次提交
  3. 06 4月, 2009 1 次提交
  4. 11 12月, 2008 1 次提交
    • R
      [MTD] [NAND] remove excess kernel-doc notation · d3af0f04
      Randy Dunlap 提交于
      Delete extra kernel-doc notation for struct fields and function
      parameters that don't exist:
      
      Warning(include/linux/mtd/nand.h:428): Excess struct/union/enum/typedef member 'wq' description in 'nand_chip'
      Warning(include/linux/mtd/nand.h:428): Excess struct/union/enum/typedef member 'datbuf' description in 'nand_chip'
      Warning(include/linux/mtd/nand.h:428): Excess struct/union/enum/typedef member 'oobbuf' description in 'nand_chip'
      Warning(include/linux/mtd/nand.h:428): Excess struct/union/enum/typedef member 'oobdirty' description in 'nand_chip'
      Warning(include/linux/mtd/nand.h:428): Excess struct/union/enum/typedef member 'data_poi' description in 'nand_chip'
      Warning(drivers/mtd/nand/nand_base.c:2527): Excess function parameter 'maxchips' description in 'nand_scan_tail'
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      d3af0f04
  5. 10 12月, 2008 1 次提交
    • A
      [MTD] update internal API to support 64-bit device size · 69423d99
      Adrian Hunter 提交于
      MTD internal API presently uses 32-bit values to represent
      device size.  This patch updates them to 64-bits but leaves
      the external API unchanged.  Extending the external API
      is a separate issue for several reasons.  First, no one
      needs it at the moment.  Secondly, whether the implementation
      is done with IOCTLs, sysfs or both is still debated.  Thirdly
      external API changes require the internal API to be accepted
      first.
      
      Note that although the MTD API will be able to support 64-bit
      device sizes, existing drivers do not and are not required
      to do so, although NAND base has been updated.
      
      In general, changing from 32-bit to 64-bit values cause little
      or no changes to the majority of the code with the following
      exceptions:
          	- printk message formats
          	- division and modulus of 64-bit values
          	- NAND base support
      	- 32-bit local variables used by mtdpart and mtdconcat
      	- naughtily assuming one structure maps to another
      	in MEMERASE ioctl
      Signed-off-by: NAdrian Hunter <ext-adrian.hunter@nokia.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      69423d99
  6. 21 8月, 2008 1 次提交
  7. 30 7月, 2008 1 次提交
  8. 25 7月, 2008 1 次提交
  9. 07 6月, 2008 1 次提交
  10. 05 6月, 2008 1 次提交
  11. 23 7月, 2007 1 次提交
  12. 08 5月, 2007 1 次提交
  13. 18 4月, 2007 1 次提交
  14. 09 2月, 2007 1 次提交
  15. 29 11月, 2006 1 次提交
  16. 31 10月, 2006 1 次提交
  17. 22 10月, 2006 1 次提交
  18. 26 9月, 2006 4 次提交
  19. 29 6月, 2006 2 次提交
  20. 21 6月, 2006 1 次提交
    • T
      [MTD] NAND: Fix breakage all over the place · 7bc3312b
      Thomas Gleixner 提交于
      Following problems are addressed:
      
      - wrong status caused early break out of nand_wait()
      - removed the bogus status check in nand_wait() which
        is a relict of the abandoned support for interrupted
        erase.
      - status check moved to the correct place in read_oob
      - oob support for syndrom based ecc with strange layouts
      - use given offset in the AUTOOOB based oob operations
      
      Partially based on a patch from Vitaly Vool <vwool@ru.mvista.com>
      Thanks to Savin Zlobec <savin@epico.si> for tracking down the
      status problem.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      7bc3312b
  21. 29 5月, 2006 3 次提交
    • T
      [MTD] Rework the out of band handling completely · 8593fbc6
      Thomas Gleixner 提交于
      Hopefully the last iteration on this!
      
      The handling of out of band data on NAND was accompanied by tons of fruitless
      discussions and halfarsed patches to make it work for a particular
      problem. Sufficiently annoyed by I all those "I know it better" mails and the
      resonable amount of discarded "it solves my problem" patches, I finally decided
      to go for the big rework. After removing the _ecc variants of mtd read/write
      functions the solution to satisfy the various requirements was to refactor the
      read/write _oob functions in mtd.
      
      The major change is that read/write_oob now takes a pointer to an operation
      descriptor structure "struct mtd_oob_ops".instead of having a function with at
      least seven arguments.
      
      read/write_oob which should probably renamed to a more descriptive name, can do
      the following tasks:
      
      - read/write out of band data
      - read/write data content and out of band data
      - read/write raw data content and out of band data (ecc disabled)
      
      struct mtd_oob_ops has a mode field, which determines the oob handling mode.
      
      Aside of the MTD_OOB_RAW mode, which is intended to be especially for
      diagnostic purposes and some internal functions e.g. bad block table creation,
      the other two modes are for mtd clients:
      
      MTD_OOB_PLACE puts/gets the given oob data exactly to/from the place which is
      described by the ooboffs and ooblen fields of the mtd_oob_ops strcuture. It's
      up to the caller to make sure that the byte positions are not used by the ECC
      placement algorithms.
      
      MTD_OOB_AUTO puts/gets the given oob data automaticaly to/from the places in
      the out of band area which are described by the oobfree tuples in the ecclayout
      data structre which is associated to the devicee.
      
      The decision whether data plus oob or oob only handling is done depends on the
      setting of the datbuf member of the data structure. When datbuf == NULL then
      the internal read/write_oob functions are selected, otherwise the read/write
      data routines are invoked.
      
      Tested on a few platforms with all variants. Please be aware of possible
      regressions for your particular device / application scenario
      
      Disclaimer: Any whining will be ignored from those who just contributed "hot
      air blurb" and never sat down to tackle the underlying problem of the mess in
      the NAND driver grown over time and the big chunk of work to fix up the
      existing users. The problem was not the holiness of the existing MTD
      interfaces. The problems was the lack of time to go for the big overhaul. It's
      easy to add more mess to the existing one, but it takes alot of effort to go
      for a real solution.
      
      Improvements and bugfixes are welcome!
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      8593fbc6
    • T
      [MTD] NAND Replace oobinfo by ecclayout · 5bd34c09
      Thomas Gleixner 提交于
      The nand_oobinfo structure is not fitting the newer error correction
      demands anymore. Replace it by struct nand_ecclayout and fixup the users
      all over the place. Keep the nand_oobinfo based ioctl for user space
      compability reasons.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      5bd34c09
    • T
      [MTD] NAND Fix platform structure and NDFC driver · 8be834f7
      Thomas Gleixner 提交于
      The platform structure was lacking an oobinfo field.
      The NDFC driver had some remains from another tree.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      8be834f7
  22. 27 5月, 2006 1 次提交
  23. 25 5月, 2006 3 次提交
  24. 24 5月, 2006 2 次提交
  25. 23 5月, 2006 5 次提交