26 Sep, 2012

1 commit


22 Sep, 2012

3 commits


21 Sep, 2012

4 commits


20 Sep, 2012

1 commit

  • This patch adds a driver for Freescale Colfire Queued SPI bus.
    Coded to work with 8 bits per transfer to use with SPI flash.
    CPOL, CPHA, and CS_ACTIVE_HIGH can be configured.

    Tested with MCF5270 which have 4 chip selects.

    Activate by #define CONFIG_CF_QSPI in board config.

    Signed-off-by: Richard Retanubun

    Richard Retanubun
     

19 Sep, 2012

4 commits

  • Tom Rini
     
  • The MPC8308RDB Reference Manual states that no bits in the SPMODE
    register are allowed to change while the enable (EN) bit is set.

    This driver changes the character length bits (LEN) while the enable
    (EN) bit is set. Clearing the EN bit while changing the LEN bits makes
    the driver work correctly on MPC8308RDB.

    Signed-off-by: Ira W. Snyder
    Signed-off-by: Kim Phillips

    Ira W. Snyder
     
  • greth.c: In function ‘greth_recv’:
    greth.c:507:3: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘unsigned int’ [-Wformat]
    greth.c:507:3: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘unsigned int’ [-Wformat]
    greth.c:541:6: warning: pointer targets in assignment differ in signedness [-Wpointer-sign]
    greth.c: In function ‘greth_initialize’:
    greth.c:623:2: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘struct greth_regs *’ [-Wformat]
    greth.c:655:3: warning: format ‘%x’ expects argument of type ‘unsigned int’, but argument 2 has type ‘struct greth_regs *’ [-Wformat]
    greth.c:684:2: warning: format ‘%x’ expects argument of type ‘unsigned int’, but argument 2 has type ‘struct greth_regs *’ [-Wformat]

    Signed-off-by: Marek Vasut
    Cc: Joe Hershberger
    Cc: Daniel Hellstrom
    Cc: u-boot-dm@lists.denx.de

    Marek Vasut
     
  • In board_nand_init() we only need the 'tmp' variable if MXC_NFC_V2_1 is
    defined.

    Signed-off-by: Tom Rini

    Tom Rini
     

18 Sep, 2012

15 commits


13 Sep, 2012

1 commit


11 Sep, 2012

5 commits


08 Sep, 2012

3 commits

  • Some eMMC devices contain boot partitions, but do not set the PART_SUPPORT
    bit in EXT_CSD_PARTITIONING_SUPPORT. Allow partition selection on such
    devices, by enabling partition switching when EXT_CSD_BOOT_MULT is set.

    Note that the Linux kernel enables access to boot partitions solely based
    on the value of EXT_CSD_BOOT_MULT; EXT_CSD_PARTITIONING_SUPPORT only
    influences access to "general" partitions.

    eMMC devices affected by this issue exist on various NVIDIA Tegra
    platforms (and presumably many others too), such as Harmony (plug-in eMMC),
    Seaboard, Springbank, and Whistler (plug-in eMMC).

    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Stephen Warren
     
  • A device tree is used to configure the NAND, including memory
    timings and block/pages sizes.

    If this node is not present or is disabled, then NAND will not
    be initialized.

    Signed-off-by: Jim Lin
    Signed-off-by: Simon Glass
    Signed-off-by: Tom Warren

    Jim Lin
     
  • The NAND layer needs to use cache-aligned buffers by default. Towards this
    goal. align the default buffers and their members according to the minimum
    DMA alignment defined for the architecture.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Warren
    Acked-by: Scott Wood

    Simon Glass
     

07 Sep, 2012

1 commit

  • There were a couple of drivers that were actually using the flags
    field of the cmd structure, despite the fact that no one ever
    *set* that field. When we removed the field, those drivers failed
    to compile. Replaced the references with the correct usage of
    resp_type.

    Signed-off-by: Andy Fleming

    Andy Fleming
     

06 Sep, 2012

2 commits

  • This patch prevents dcache-related problem. The problem manifested
    itself on the SPI driver, this is just a port to the MMC driver.

    The scenario is the same. In case an "mmc read" is issued to a
    buffer which was written right before it and data cache is enabled,
    the cache eviction might happen during the DMA transfer into the
    buffer, therefore corrupting the buffer. Clear any cache lines that
    might contain the buffer to prevent such issue.

    Signed-off-by: Marek Vasut
    Cc: Fabio Estevam
    Cc: Otavio Salvador
    Cc: Stefano Babic

    Marek Vasut
     
  • It turns out that in order for the SPI DMA to properly support
    continuous transfers longer than 65280 bytes, there are some very
    important parts that were left out from the documentation.

    Firstly, the XFER_SIZE register is not written with the whole length
    of a transfer, but is written by each and every chained descriptor
    with the length of the descriptors data buffer.

    Next, unlike the demo code supplied by FSL, which only writes one PIO
    word per descriptor, this does not apply if the descriptors are chained,
    since the XFER_SIZE register must be written. Therefore, it is essential
    to use four PIO words, CTRL0, CMD0, CMD1, XFER_SIZE. CMD0 and CMD1 are
    written with zero, since they don't apply. The DMA programs the PIO words
    in an incrementing order, so four PIO words.

    Finally, unlike the demo code supplied by FSL, the SSP_CTRL0_IGNORE_CRC
    must not be set during the whole transfer, but it must be set only on the
    last descriptor in the chain.

    Signed-off-by: Marek Vasut
    Cc: Fabio Estevam
    Cc: Otavio Salvador
    Cc: Stefano Babic

    Marek Vasut