Doug / smarc-fsl-linux-kernel

08 Nov, 2011

1 commit

  • e0d65113a   Merge git://git.infradead.org/mtd-2.6 ... Browse Code »

    * git://git.infradead.org/mtd-2.6: (226 commits)
    mtd: tests: annotate as DANGEROUS in Kconfig
    mtd: tests: don't use mtd0 as a default
    mtd: clean up usage of MTD_DOCPROBE_ADDRESS
    jffs2: add compr=lzo and compr=zlib options
    jffs2: implement mount option parsing and compression overriding
    mtd: nand: initialize ops.mode
    mtd: provide an alias for the redboot module name
    mtd: m25p80: don't probe device which has status of 'disabled'
    mtd: nand_h1900 never worked
    mtd: Add DiskOnChip G3 support
    mtd: m25p80: add EON flash EN25Q32B into spi flash id table
    mtd: mark block device queue as non-rotational
    mtd: r852: make r852_pm_ops static
    mtd: m25p80: add support for at25df321a spi data flash
    mtd: mxc_nand: preset_v1_v2: unlock all NAND flash blocks
    mtd: nand: switch `check_pattern()' to standard `memcmp()'
    mtd: nand: invalidate cache on unaligned reads
    mtd: nand: do not scan bad blocks with NAND_BBT_NO_OOB set
    mtd: nand: wait to set BBT version
    mtd: nand: scrub BBT on ECC errors
    ...

    Fix up trivial conflicts:
    - arch/arm/mach-at91/board-usb-a9260.c
    Merged into board-usb-a926x.c
    - drivers/mtd/maps/lantiq-flash.c
    add_mtd_partitions -> mtd_device_register vs changed to use
    mtd_device_parse_register.

    Linus Torvalds
     

01 Nov, 2011

1 commit

11 Sep, 2011

3 commits

  • 0612b9ddc   mtd: rename MTD_OOB_* to MTD_OPS_* ... Browse Code »

    These modes are not necessarily for OOB only. Particularly, MTD_OOB_RAW
    affected operations on in-band page data as well. To clarify these
    options and to emphasize that their effect is applied per-operation, we
    change the primary prefix to MTD_OPS_.

    Signed-off-by: Brian Norris
    Signed-off-by: Artem Bityutskiy

    Brian Norris
     
  • 289c05222   mtd: replace DEBUG() with pr_debug() ... Browse Code »

    Start moving away from the MTD_DEBUG_LEVEL messages. The dynamic
    debugging feature is a generic kernel feature that provides more
    flexibility.

    (See Documentation/dynamic-debug-howto.txt)

    Also fix some punctuation, indentation, and capitalization that went
    along with the affected lines.

    Signed-off-by: Brian Norris
    Signed-off-by: Artem Bityutskiy

    Brian Norris
     
  • 0870066d7   mtd: remove printk's for [kv][mz]alloc failures ... Browse Code »

    When a memory allocation fails, the kernel will print out a backtrace
    automatically. These print statements are unnecessary.

    Signed-off-by: Brian Norris
    Signed-off-by: Artem Bityutskiy

    Brian Norris
     

06 Jan, 2011

1 commit

  • e0c1a921f   mtd: OneNAND: lighten scary initial bad block messages ... Browse Code »

    Initial bad blocks are normal but the messages look like
    errors. Make the messages less scary, make the main
    message an informational message not a warning, make the
    message displaying registers a debug message and include
    the address there instead of in the informational message.

    Signed-off-by: Adrian Hunter
    Acked-by: Kyungmin Park
    Signed-off-by: Artem Bityutskiy
    Signed-off-by: David Woodhouse

    Adrian Hunter
     

04 Dec, 2010

1 commit

  • 01039e4e6   mtd: onenand: bugfix for 2x mode bad block handling ... Browse Code »

    This bug becomes visible in 2x mode when chip->writesize
    is different from mtd->writesize (= 2 * chip->writesize).
    At this case the bad block information is read from
    the first and the third physical pages instead of
    the first and the second as specification states.

    Signed-off-by: Roman Tereshonkov
    Acked-by: Kyungmin Park
    Signed-off-by: David Woodhouse

    Roman Tereshonkov
     

09 Aug, 2010

1 commit

06 Jun, 2009

1 commit

  • 5988af231   mtd: Flex-OneNAND support ... Browse Code »

    Add support for Samsung Flex-OneNAND devices.

    Flex-OneNAND combines SLC and MLC technologies into a single device.
    SLC area provides increased reliability and speed, suitable for storing
    code such as bootloader, kernel and root file system. MLC area
    provides high density and is suitable for storing user data.

    SLC and MLC regions can be configured through kernel parameter.

    [akpm@linux-foundation.org: export flexoand_region and onenand_addr]
    Signed-off-by: Rohit Hagargundgi
    Signed-off-by: Kyungmin Park
    Cc: Vishak G
    Signed-off-by: Andrew Morton
    Signed-off-by: David Woodhouse

    Rohit Hagargundgi
     

22 Apr, 2008

1 commit

07 Feb, 2007

1 commit

01 Feb, 2007

1 commit

22 Jan, 2007

2 commits

10 Jan, 2007

1 commit

29 Nov, 2006

2 commits

16 Nov, 2006

1 commit

29 May, 2006

1 commit

  • 8593fbc68   [MTD] Rework the out of band handling completely ... Browse Code »

    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: Thomas Gleixner

    Thomas Gleixner
     

23 May, 2006

1 commit

  • 28318776a   [MTD] Introduce writesize ... Browse Code »

    At least two flashes exists that have the concept of a minimum write unit,
    similar to NAND pages, but no other NAND characteristics. Therefore, rename
    the minimum write unit to "writesize" for all flashes, including NAND.

    Signed-off-by: Joern Engel

    Joern Engel
     

19 Dec, 2005

1 commit

07 Nov, 2005

1 commit