17 Jul, 2015

1 commit

  • All the mux configurations needs to be done as part of the IODelay
    sequence to avoid glitch.
    Adding all the mux configuration for DRA72-evm.
    MANUAL/VIRTUAL mode settings will be added once the data is available.

    Signed-off-by: Lokesh Vutla

    Lokesh Vutla
     

15 Jul, 2015

6 commits


11 Jul, 2015

1 commit

  • Commit 2b42c9317db ("ahci: support LBA48 data reads for 2+TB drives")
    introduced conditional code which triggers a warning when compiled
    with DEBUG enabled:

    In file included from common/cmd_scsi.c:12:0:
    common/cmd_scsi.c: In function 'scsi_read':
    include/common.h:109:4: warning: 'smallblks' may be used uninitialized in this function [-Wmaybe-uninitialized]
    ...

    Since this is for debug only, take the easy way and initialize the
    variable explicitly on declaration to avoid the warning.
    (Fix a nearby whitespace error on the way.)

    Tested-by: Bin Meng
    Signed-off-by: Andre Przywara

    Andre Przywara
     

10 Jul, 2015

17 commits


09 Jul, 2015

15 commits

  • Because it is possible for the MTD number to change, causing a
    filesystem mount failure, we should use the volume name instead
    of the MTD number and let Linux resolve the correct one.

    Signed-off-by: Mike Scherban

    Michael Scherban
     
  • On STM32F429 gpio PC6/PC7 can be allocated for USART6, as
    reported in the comment.
    But current code in
    drivers/serial/serial_stm32.c
    uses a different gpio mapping (PG14/PG9) for USART6.

    Fix the comment to match current code in the driver.

    Signed-off-by: Antonio Borneo
    To: u-boot@lists.denx.de
    To: Kamil Lulko
    Cc: Tom Rini

    Antonio Borneo
     
  • Signed-off-by: Antonio Borneo
    To: u-boot@lists.denx.de
    To: Kamil Lulko
    Cc: Tom Rini

    Antonio Borneo
     
  • When "scripts/get_maintainer.pl" parses "board/.../MAINTAINERS",
    it uses the line containing board name as delimiter.
    Without this line, the script happily mixes the lines from current
    board MAINTAINERS file with lines from another file.

    Fix it by adding a reasonable board name.

    Tested by comparing output of:
    cat board/st/stm32f429-discovery/MAINTAINERS
    ./scripts/get_maintainer.pl -f board/st/stm32f429-discovery

    Signed-off-by: Antonio Borneo
    To: u-boot@lists.denx.de
    To: Kamil Lulko
    Cc: Tom Rini

    Antonio Borneo
     
  • Use one mtd partition for rootfs and configuration by
    means of ubi volumes and get rid of configuration partition.
    We can use partition layout for both 256MB and 512MB flash.

    Signed-off-by: Samuel Egli
    Cc: Heiko Schocher
    Cc: Roger Meier
    Reviewed-by: Tom Rini
    Acked-by: Heiko Schocher

    Egli, Samuel
     
  • Specify proper U-Boot offset, enable prefetch mode,
    increase bootm size and add FIT fallback, if board_name
    is not present in kernel-fit.itb image.

    Signed-off-by: Yegor Yefremov

    Yegor Yefremov
     
  • This action is need to make I2C communication with PMIC
    stable for low temperature. Print current I2C speed in
    SPL for visual control.

    Signed-off-by: Yegor Yefremov

    Yegor Yefremov
     
  • Signed-off-by: Yegor Yefremov
    Reviewed-by: Simon Glass

    Yegor Yefremov
     
  • Add CONFIG_SYS_GENERIC_BOARD to board's config header.

    Boot-tested on am3517_evm board.

    Signed-off-by: Yegor Yefremov

    Yegor Yefremov
     
  • If board is booted with transitions happening on DCAN1 pins then
    the following warning is seen in the kernel at boot when the
    hwmod layer initializes.

    "omap_hwmod: dcan1: _wait_target_disable failed"

    This is because DCAN1 module's SWAKEUP mechanism is broken
    and it fails to correctly turn OFF if it sees a transition on the
    DCAN1 pins. Suggested workaround is to keep DCAN1 pins in safe mode
    while enabling/disabling DCAN1 module.

    The hwmod layer enables and disables all modules at boot
    and we have no opportunity to put the DCAN1 pins in safe mode
    at that point.

    DCAN1 is not used by u-boot so it doesn't matter to it if these
    pins are in safe mode. The kernel driver correctly configures
    the right mode when DCAN1 is active.

    Signed-off-by: Roger Quadros
    [trini: s/PULLUP/PULL_UP/ based on DRA7xx EVM version of this patch]
    Signed-off-by: Tom Rini

    Roger Quadros
     
  • If board is booted with transitions happening on DCAN1 pins then
    the following warning is seen in the kernel at boot when the
    hwmod layer initializes.

    "omap_hwmod: dcan1: _wait_target_disable failed"

    This is because DCAN1 module's SWAKEUP mechanism is broken
    and it fails to correctly turn OFF if it sees a transition on the
    DCAN1 pins. Suggested workaround is to keep DCAN1 pins in safe mode
    while enabling/disabling DCAN1 module.

    The hwmod layer enables and disables all modules at boot
    and we have no opportunity to put the DCAN1 pins in safe mode
    at that point.

    DCAN1 is not used by u-boot so it doesn't matter to it if these
    pins are in safe mode. The kernel driver correctly configures
    the right mode when DCAN1 is active.

    Signed-off-by: Roger Quadros

    Roger Quadros
     
  • -fdelete-null-pointer-checks flag controls global dataflow analyses and
    eliminate useless checks for null pointers; It assume that if a pointer is
    checked after it has already been dereferenced, it cannot be null.
    This flag is enabled by default.

    gcc v4.9 has more optimizations added to this option. Hence it is very
    aggressive with GCC v4.9 series. Add -fno-delete-null-pointer-checks to
    disable the optimization

    Signed-off-by: Rohit Dharmakan
    Signed-off-by: Prabhakar Kushwaha

    Prabhakar Kushwaha
     
  • This also came from Linux - according to this thread it has a GPL v2
    license like arch/arm/mach-omap2/mux.h:

    http://lists.denx.de/pipermail/u-boot/2015-June/217827.html

    Signed-off-by: Simon Glass
    Reported-by: Ingrid Viitanen
    Reviewed-by: Tom Rini

    Simon Glass
     
  • The word "partition" is doubled. Keep decent forms for the
    following lines.

    Also, fix some other typos while we are here.

    Signed-off-by: Masahiro Yamada
    Acked-by: Stephen Warren

    Masahiro Yamada
     
  • bf533-stamp, bf538f-ezkit, and cm-bf548 are very space limited.

    This was introduced by:
    6e0d26c0502e (net: Handle ethaddr changes as an env callback)
    by enabling CONFIG_REGEX, which is too big for these boards.

    This patch disables CONFIG_REGEX at the expense of working with more
    than the first ethaddr.

    Signed-off-by: Joe Hershberger

    Joe Hershberger