Eric Lee / smarc-uboot

13 Jan, 2014

2 commits

10 Jan, 2014

29 commits

09 Jan, 2014

9 commits

  • 129168290   arm64: board support of vexpress_aemv8a ... Browse Code »

    Signed-off-by: David Feng
    Signed-off-by: Bhupesh Sharma

    David Feng
     
  • 0ae765312   arm64: core support ... Browse Code »

    Relocation code based on a patch by Scott Wood, which is:
    Signed-off-by: Scott Wood

    Signed-off-by: David Feng

    David Feng
     
  • ec4fa5674   add weak entry definition ... Browse Code »

    Signed-off-by: David Feng

    David Feng
     
  • ab71188ce   mmc: add setdsr support ... Browse Code »

    The eMMC and the SD-Card specifications describe the optional SET_DSR command.
    During measurements at our lab we found that some cards implementing this feature
    having really strong driver strengts per default. This can lead to voltage peaks
    above the specification of the host on signal edges for data sent from a card to
    the host.

    Since availability of a given card type may be shorter than the time a certain
    hardware will be produced it is useful to have support for this command (Alternative
    would be changing termination resistors and adapting the driver strength of the
    host to the used card.)

    Following proposal for an implementation:

    - new field that reflects CSD field DSR_IMP in struct mmc
    - new field for design specific DSR value in struct mmc
    - board code can set DSR value in mmc struct just after registering an controller
    - mmc_startup sends the the stored DSR value before selecting a card, if DSR_IMP is set

    Additionally the mmc command is extended to make is possible to play around with different
    DSR values.

    The concept was tested on a i.MX53 based platform using a Micron eMMC card where the default
    DSR is 0x0400 (12mA) but in our design 0x0100 (0x0100) were enough. To use this feature for
    instance on a mx53loco one have to add a call to mmc_set_dsr() in board_mmc_init() after
    calling fsl_esdhc_initialize() for the eMMC.

    Signed-off-by: Markus Niebel
    Acked-by: Pantelis Antoniou

    Markus Niebel
     
  • 2a7a210e2   mmc/dwmmc: use bounce buffer for data exchange between CPU and MMC controller ... Browse Code »

    Bounce buffer implementation takes care of proper data buffer alignemt
    and correct flush/invalidation of data cache at once so we no longer
    depend on input data variety and make sure CPU and MMC controller deal
    with expected data in case of enabled data cache.

    Bounce buffer requires to add its definition (CONFIG_BOUNCE_BUFFER) in
    board configuration, otherwise corresponding library won't be compiled
    and linker will fail to build resulting executable.

    Difference since v1 - fixed compile-time warning with type casting to
    "void *":

    Slight edit to remove UTF8 characters in the commit message.

    Acked-by: Jaehoon Chung
    Tested-by: Jaehoon Chung
    Acked-by: Pantelis Antoniou

    ====
    passing argument 2 of 'bounce_buffer_start' discards 'const' qualifier
    from pointer target type
    ====

    Signed-off-by: Alexey Brodkin

    Cc: Mischa Jonker
    Cc: Alim Akhtar
    Cc: Rajeshwari Shinde
    Cc: Jaehoon Chung
    Cc: Amar
    Cc: Kyungmin Park
    Cc: Minkyu Kang
    Cc: Simon Glass
    Cc: Pantelis Antoniou
    Cc: Andy Fleming

    Alexey Brodkin
     
  • 6b87abe3a   sh: sh4: Remove CONFIG_SH4A definition from source code ... Browse Code »

    SH4 and SH4A are compatible. But some instructions are different from these.
    In Linux kernel, It is treated as a separate CPU, but for now, I think that
    there is no need to divide especially in the U-Boot.

    This removes CONFIG_SH4A definition from source code, SH4A is treated as SH4.
    And this fix white space.

    Signed-off-by: Nobuhiro Iwamatsu

    Nobuhiro Iwamatsu
     
  • ed3f5a30a   sandbox: tpm: Add TPM emulation ... Browse Code »

    Add a simple TPM emulator for sandbox. It only supports a small subset of
    TPM operations. However, these are enough to perform common tasks.

    Note this is an initial commit to get this working, but it could use
    cleaning up (for example constants instead of open-coded values).

    Signed-off-by: Simon Glass

    Signed-off-by: Simon Glass
    Reviewed-by: Simon Glass

    Simon Glass
     
  • 5c2859cdc   sandbox: Allow reading/writing of RAM buffer ... Browse Code »

    It is useful to be able to save and restore the RAM contents of sandbox
    U-Boot either for setting up tests, for later analysys, or for chaining
    together multiple tests which need to keep the same memory contents.

    Add a function to provide a memory file for U-Boot. This is read on
    start-up and written when shutting down. If the file does not exist
    on start-up, it will be created when shutting down.

    Signed-off-by: Simon Glass
    Signed-off-by: Simon Glass

    Simon Glass
     
  • 91b136c79   sandbox: Allow the console to work earlier ... Browse Code »

    With sandbox, errors and problems may be reported before console_init_f()
    is executed. For example, an argument may not parse correctly or U-Boot may
    panic(). At present this output is swallowed so there is no indication what
    is going wrong.

    Adjust the console to deal with a very early sandbox setup, by detecting that
    there is no global_data yet, and calling os functions in that case.

    Signed-off-by: Simon Glass
    Signed-off-by: Simon Glass

    Simon Glass