16 May, 2017

1 commit


15 May, 2017

2 commits

  • We make use of CONFIG_OMAP3_EVM today to know when to do a specific
    tweak in MUSB. This can be tested on via CONFIG_TARGET_OMAP3_EVM
    instead, so switch there so we can drop the now unused symbol
    CONFIG_OMAP3_EVM. In investigating what to do about the symbol usage we
    see that the cairo board defines the same function, but never called it
    (as it does not define CONFIG_OMAP3_EVM) and was just returning anyhow,
    so drop that function from that board.

    Cc: "Albert ARIBAUD (3ADEV)"
    Cc: Marek Vasut
    Signed-off-by: Tom Rini

    Tom Rini
     
  • Now CONFIG_GENERIC_MMC and CONFIG_MMC match for all defconfig.
    We do not need two options for the same feature. Deprecate the
    former.

    This commit was generated with the sed script 's/GENERIC_MMC/MMC/'
    and manual fixup of drivers/mmc/Kconfig.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

20 Mar, 2017

1 commit

  • To keep a consistent MMC device mapping in SPL and in u-boot, let's
    register the MMC controllers the same way in u-boot and in the SPL.
    In terms of boot time, it doesn't hurt to register more controllers than
    needed because the MMC device is initialized only prior being accessed for
    the first time.
    Having the same device mapping in SPL and u-boot allows us to use the
    environment in SPL whatever the MMC boot device.

    Signed-off-by: Jean-Jacques Hiblot

    Jean-Jacques Hiblot
     

29 Jan, 2017

1 commit

  • In the cases of some boards, a MACH_TYPE number is used which is either
    not registered upstream or worse (for functionality) is re-using the
    number of a different (or reference) platform instead. Make sure we
    have a comment in these cases.

    Cc: Albert ARIBAUD
    Cc: Walter Schweizer
    Cc: Stefan Roese
    Cc: Fabio Estevam
    Signed-off-by: Tom Rini
    Acked-by: Stefan Roese

    Tom Rini
     

20 Jan, 2017

1 commit

  • commit: 65f83802b7a5b "serial: 16550: Add getfcr accessor"
    breaks u-boot commandline working with long commands
    sending to the board.

    Since the above patch, you have to setup the fcr register.

    For board/archs which enable OF_PLATDATA, the new field
    fcr in struct ns16550_platdata is not filled with a
    default value ...

    This leads in not setting up the uarts fifo, which ends
    in problems, when you send long commands to u-boots
    commandline.

    Detected this issue with automated tbot tests on am335x
    based shc board.

    The error does not popup, if you type commands. You need
    to copy&paste a long command to u-boots commandshell
    (or send a long command with tbot)

    Possible boards/plattforms with problems:
    ./arch/arm/cpu/arm926ejs/lpc32xx/devices.c
    ./arch/arm/mach-tegra/board.c
    ./board/overo/overo.c
    ./board/quipos/cairo/cairo.c
    ./board/logicpd/omap3som/omap3logic.c
    ./board/logicpd/zoom1/zoom1.c
    ./board/timll/devkit8000/devkit8000.c
    ./board/lg/sniper/sniper.c
    ./board/ti/beagle/beagle.c
    ./drivers/serial/serial_rockchip.c

    Signed-off-by: Heiko Schocher
    Signed-off-by: Ladislav Michl
    Tested-by: Adam Ford
    Reviewed-by: Tom Rini

    Heiko Schocher
     

15 Mar, 2016

1 commit

  • A few boards still use ns16550_platdata structures, but assume the structure
    is going to be in a specific order. By explicitly naming each entry,
    this should also help 'future-proof' in the event the structure changes.

    Tested on the Logic PD Torpedo + Wireless.

    I only changed a handful of devices that used the same syntax as the Logic
    board. Appologies if I missed one or stepped on toes. Thanks to Derald Woods
    and Alexander Graf.

    Signed-off-by: Adam Ford

    V6: Add fix to arch/arm/cpu/armv7/am33xx/board.c

    V5: Add fix to arch/arm/cpu/arm926ejs/lpc32xx/devices.c

    V4: Fix subject heading

    V3: Remove reg_offset out in all the structs. It was reverted out, and and if
    it did exist, it would get initialized to 0 by default.

    V2: I hastily copy-pasted the boards without looking at the UART number.
    This addresses 3 boards that use UART3 and not UART1.
    Reviewed-by: Mugunthan V N
    Reviewed-by: Simon Glass

    Adam Ford
     

22 Nov, 2015

1 commit


07 Jul, 2015

1 commit


06 Mar, 2015

1 commit