30 Jun, 2015

10 commits

  • Signed-off-by: Tom Rini

    Tom Rini
     
  • If flash pointer is used free it, before probing a new
    flash and storing it in flash.

    Signed-off-by: Heiko Schocher
    Tested-by: Jagannadh Teki
    Reviewed-by: Jagannadh Teki

    Heiko Schocher
     
  • With this patch, it is possible to get the offset and size information
    from the mtdpartiton setting in "mtdparts", similiar to the
    "nand" commandos.

    => sf
    sf - SPI flash sub-system

    Usage:
    sf probe [[bus:]cs] [hz] [mode] - init flash device on given SPI bus
    and chip select
    sf read addr offset|partition len - read `len' bytes starting at
    `offset' to memory at `addr'
    sf write addr offset|partition len - write `len' bytes from memory
    at `addr' to flash at `offset'
    sf erase offset|partition [+]len - erase `len' bytes from `offset'
    `+len' round up `len' to block size
    sf update addr offset|partition len - erase and write `len' bytes from memory
    at `addr' to flash at `offset'
    =>
    for example "env" is defined in mtdparts:

    => sf read 13000000 env
    device 0 offset 0xd0000, size 0x10000
    SF: 65536 bytes @ 0xd0000 Read: OK

    zynq-uboot> mtdparts add nor0 0x10000@0x0 env
    zynq-uboot> sf erase env 0x10000
    SF: 65536 bytes @ 0x0 Erased: OK

    zynq-uboot> sf write 0x100 env
    device 0 offset 0x0, size 0x10000
    SF: 65536 bytes @ 0x0 Written: OK

    zynq-uboot> sf read 0x40000 env
    device 0 offset 0x0, size 0x10000
    SF: 65536 bytes @ 0x0 Read: OK

    Signed-off-by: Heiko Schocher
    Tested-by: Jagannadh Teki
    Reviewed-by: Jagannadh Teki

    Heiko Schocher
     
  • Move common functions from cmd_nand.c (for calculating offset
    and size from cmdline paramter) to common place, so they could
    used from other commands which use mtd partitions.

    For onenand the arg_off_size() is left in common/cmd_onenand.c.
    It should use now the common arg_off() function, but as I could
    not test onenand I let it there ...

    Signed-off-by: Heiko Schocher
    Acked-by: Scott Wood
    Reviewed-by: Jagannadh Teki

    Heiko Schocher
     
  • Add MTD layer driver for spi, original patch from:
    http://git.denx.de/?p=u-boot/u-boot-mips.git;a=commitdiff;h=bb246819cdc90493dd7089eaa51b9e639765cced

    Changes from Heiko Schocher against this patch:
    - Remove compile error if not defining CONFIG_SPI_FLASH_MTD:

    LD drivers/mtd/spi/built-in.o
    drivers/mtd/spi/sf_probe.o: In function `spi_flash_mtd_unregister':
    /home/hs/abb/imx6/u-boot/drivers/mtd/spi/sf_internal.h:168: multiple definition of `spi_flash_mtd_unregister'
    drivers/mtd/spi/sf_params.o:/home/hs/abb/imx6/u-boot/drivers/mtd/spi/sf_internal.h:168: first defined here
    drivers/mtd/spi/sf_ops.o: In function `spi_flash_mtd_unregister':
    /home/hs/abb/imx6/u-boot/drivers/mtd/spi/sf_internal.h:168: multiple definition of `spi_flash_mtd_unregister'
    drivers/mtd/spi/sf_params.o:/home/hs/abb/imx6/u-boot/drivers/mtd/spi/sf_internal.h:168: first defined here
    make[1]: *** [drivers/mtd/spi/built-in.o] Fehler 1
    make: *** [drivers/mtd/spi] Fehler 2

    - Add a README entry.
    - Add correct writebufsize, to fit with Linux v3.14
    MTD, UBI/UBIFS sync.

    Note (From Jagan): For testing raw mtd parition erase/read/write operations
    using cmd_sf, sf_mtd should be required to register the spi flash device to
    MTD layer but the sf_mtd_info ops were not required until and unless if we
    use any flash filesystem layer say for example UBI. Due to this the foot-print
    got increased ~290bytes in non-UBI case here that should be acceptible.

    Signed-off-by: Daniel Schwierzeck
    Signed-off-by: Heiko Schocher
    Tested-by: Jagannadh Teki
    Reviewed-by: Jagannadh Teki

    Daniel Schwierzeck
     
  • PI and QSPI only work when boot from QSPI on ls1021a.
    This patch only enable options in qspi boot defconfig.

    Signed-off-by: Haikun Wang
    Tested-by: Haikun Wang
    Signed-off-by: Jagan Teki

    Haikun Wang
     
  • Enable Driver Model SPI for ls1021atwr board.
    DSPI and QSPI only be enabled when boot from QSPI.
    DSPI and QSPI are compatible under Driver Model SPI.

    Signed-off-by: Haikun Wang
    Tested-by: Review Code-CDREVIEW
    Tested-by: Haikun Wang
    Reviewed-by: Prabhakar Kushwaha
    Reviewed-by: Jagan Teki

    Haikun Wang
     
  • Enable Driver Model SPI for ls1021aqds board.
    DSPI and QSPI is enabled only when boot from QSPI.
    DSPI and QSPI are compatible under Driver Model SPI.

    Signed-off-by: Haikun Wang
    Tested-by: Haikun Wang
    Reviewed-by: Jagan Teki

    Haikun Wang
     
  • The type of DSPI flash on ls1021aqds is AT45DB021, it has specail
    commands and page-size.
    Use the special spi flash driver instead of "spi_flash_std" driver.

    Signed-off-by: Haikun Wang
    Tested-by: Haikun Wang
    Reviewed-by: Simon Glass
    Reviewed-by: Jagan Teki

    Haikun Wang
     
  • Atmel DataFlash chips have commands different from common spi
    flash commands.
    Atmel DataFlash also have special page-size.
    This driver add support for accessing Atmel DataFlash.
    It is based on the Driver Model.
    Example:
    => sf probe 1:0
    SPI DataFlash: Detected AT45DB021B with page size 264 Bytes, erase size 264 Bytes, total 264 KiB, revision d
    => sf erase 0 42000
    SF: 270336 bytes @ 0x0 Erased: OK
    => mw.l 82000000 45444342 20000
    => sf write 82000000 0 42000
    SF: 270336 bytes @ 0x0 Written: OK
    => sf read 83000000 0 42000
    SF: 270336 bytes @ 0x0 Read: OK
    => cmp.b 82000000 83000000 42000
    Total of 270336 byte(s) were the same

    Signed-off-by: Haikun Wang
    Tested-by: Haikun Wang
    Reviewed-by: Simon Glass
    Reviewed-by: Chakra Divi
    Reviewed-by: Jagan Teki

    Haikun Wang
     

29 Jun, 2015

1 commit


28 Jun, 2015

3 commits


26 Jun, 2015

7 commits


20 Jun, 2015

15 commits


19 Jun, 2015

4 commits

  • When we're polling and thus handling key-repeat in software, make sure
    to disable idle reports, some keyboards may have these enabled by default
    messing up our software keyrepeat.

    Signed-off-by: Hans de Goede

    Hans de Goede
     
  • Without this we loose every other interrupt packet. We never noticed this
    because with keyboards the packets which we were loosing would normally
    be key release packets.

    But now that we do keyrepeat in software instead of relying on the hid
    idle functionality, missing a release will result in key repeat triggering.

    This commit fixes this.

    Signed-off-by: Hans de Goede

    Hans de Goede
     
  • There is no harm in declaring the function prototypes even if nothing
    implements them, and when CONFIG_DM_USB=y the various usb functions are
    available regardless of any controller drivers being enabled.

    This fixes compile warnings due to missing prototypes on ARCHs where
    the ARCH Kconfig always enables CONFIG_DM_USB and various usb drivers.

    One could argue that in the case of no controllers CONFIG_DM_USB should not
    be set, but this problem is typically seen during bringup of boards which
    do actually have usb controllers.

    Signed-off-by: Hans de Goede

    Hans de Goede
     
  • With the change to make sure that CONFIG_CMD_NET is enabled this board
    no longer fits into the linker script:

    powerpc-linux-ld.bfd: section .resetvec loaded at [fffffffc,ffffffff] overlaps section .u_boot_list loaded at [ffffff58,00000723]
    powerpc-linux-ld.bfd: u-boot: section .resetvec lma 0xfffffffc adjusted to 0x724
    powerpc-linux-ld.bfd: u-boot: section `.resetvec' can't be allocated in segment 0
    LOAD: .data.init .text .rodata .reloc .data .u_boot_list .resetvec
    powerpc-linux-ld.bfd: final link failed: File truncated

    Drop CONFIG_SYS_LONGHELP to free up space.

    Cc: Matthias Fuchs
    Signed-off-by: Tom Rini

    Tom Rini