29 Nov, 2016

1 commit

  • When I tried to deactivate VIDEO support for the Wandboard, it still
    tried to initialize the Framebuffer and so on. That is the reason for
    the added ifdefs. CONFIG_VIDEO is enabled in the configuration as default
    and therefore nothing changes for the default user.

    The structs mx6dl_i2c2_pad_info and mx6q_i2c2_pad_info are only available
    when CONFIG_IPUV3 are set and should not be tried to access, when that
    define is not defined.

    Signed-off-by: Sven Ebenfeld

    Sven Ebenfeld
     

06 Nov, 2016

1 commit

  • Since commit ce412b79e7255770 ("drivers: net: phy: atheros: add separate
    config for AR8031") ethernet does not work on mx6sabresd.

    This commit correctly assigns ar8031_config() as the configuration
    function for AR8031 in the same way as done in the Linux kernel.

    However, on wandboard design we need some additional configuration,
    such as enabling the 125 MHz AR8031 output that needs to be done
    in the board file.

    This also aligns with the same method that the kernel performs
    the AR8031 fixup in arch/arm/mach-imx/mach-imx6q.c.

    Signed-off-by: Fabio Estevam
    Acked-by: Joe Hershberger

    Fabio Estevam
     

04 Oct, 2016

1 commit

  • A kernel hang is observed when running wandboard 3.14 kernel and
    going to the lowest operational point of cpufreq:

    # ifconfig eth0 down
    # echo 1 > /sys/class/graphics/fb0/blank

    The problem is caused by incorrect setting of the REFR field
    of register MDREF. Setting it to 4 refresh commands per refresh
    cycle fixes the hang.

    Signed-off-by: Fabio Estevam

    Fabio Estevam
     

24 Sep, 2016

1 commit


07 Sep, 2016

1 commit

  • Currently MX6 SPL DDR initialization hardcodes the REF_SEL and
    REFR fields of the MDREF register as 1 and 7, respectively for
    DDR3 and 0 and 3 for LPDDR2.

    Looking at the MDREF initialization done via DCD we see that
    boards do need to initialize these fields differently:

    $ git grep 0x021b0020 board/
    board/bachmann/ot1200/mx6q_4x_mt41j128.cfg:DATA 4 0x021b0020 0x00005800
    board/ccv/xpress/imximage.cfg:DATA 4 0x021b0020 0x00000800 /* MMDC0_MDREF */
    board/freescale/mx6qarm2/imximage.cfg:DATA 4 0x021b0020 0x7800
    board/freescale/mx6qarm2/imximage.cfg:DATA 4 0x021b0020 0x00005800
    board/freescale/mx6qarm2/imximage_mx6dl.cfg:DATA 4 0x021b0020 0x00005800
    board/freescale/mx6qarm2/imximage_mx6dl.cfg:DATA 4 0x021b0020 0x00005800
    board/freescale/mx6qsabreauto/imximage.cfg:DATA 4 0x021b0020 0x00005800
    board/freescale/mx6qsabreauto/mx6dl.cfg:DATA 4 0x021b0020 0x00005800
    board/freescale/mx6qsabreauto/mx6qp.cfg:DATA 4 0x021b0020 0x00005800
    board/freescale/mx6sabresd/mx6dlsabresd.cfg:DATA 4 0x021b0020 0x00005800
    board/freescale/mx6sabresd/mx6q_4x_mt41j128.cfg:DATA 4 0x021b0020 0x00005800
    board/freescale/mx6slevk/imximage.cfg:DATA 4 0x021b0020 0x00001800
    board/freescale/mx6sxsabreauto/imximage.cfg:DATA 4 0x021b0020 0x00000800
    board/freescale/mx6sxsabresd/imximage.cfg:DATA 4 0x021b0020 0x00000800
    board/warp/imximage.cfg:DATA 4 0x021b0020 0x00001800

    So introduce a mechanism for users to be able to configure
    REFSEL and REFR fields as needed.

    Keep all the mx6 SPL users in their current REF_SEL and REFR values,
    so no functional changes for the existing users.

    Signed-off-by: Fabio Estevam
    Reviewed-by: Eric Nelson

    Fabio Estevam
     

28 Jul, 2016

2 commits


12 Jul, 2016

1 commit


06 Feb, 2016

1 commit

  • Correct spelling of "U-Boot" shall be used in all written text
    (documentation, comments in source files etc.).

    Signed-off-by: Bin Meng
    Reviewed-by: Heiko Schocher
    Reviewed-by: Simon Glass
    Reviewed-by: Minkyu Kang

    Bin Meng
     

12 Jan, 2016

1 commit


08 Jan, 2016

1 commit

  • As per the AR8031 datasheet:

    "For a reliable power on reset, suggest to keep asserting the reset
    low long enough (10ms) to ensure the clock is stable and clock-to-reset
    1ms requirement is satisfied."

    So do as suggested and also add a 100us delay after deasserting the
    reset line to guarantee that the PHY ID can be read correctly and the
    Atheros 8031 PHY driver can be loaded automatically.

    This results in a simpler code.

    Signed-off-by: Fabio Estevam
    Acked-by: Joe Hershberger

    Fabio Estevam
     

13 Sep, 2015

1 commit

  • Remove duplicated SYS_SOC Kconfig entry from board Kconfig,
    because we have this entry in arch/arm/cpu/armv7/mx6/Kconfig.

    Signed-off-by: Peng Fan
    Cc: Stefano Babic
    Cc: Heiko Schocher
    Cc: Christian Gmeiner
    Cc: Stefan Roese
    Cc: Troy Kisky
    Cc: Nikita Kiryanov
    Cc: "Eric Bénard"
    Cc: Fabio Estevam
    Cc: Tim Harvey
    Cc: Marek Vasut
    Cc: Markus Niebel
    Cc: Otavio Salvador
    Acked-by: Stefan Roese
    Acked-by: Marek Vasut
    Acked-by: Christian Gmeiner
    Acked-by: Markus Niebel
    Acked-by: Troy Kisky
    Acked-by: Igor Grinberg

    Peng Fan
     

08 Jun, 2015

1 commit


22 May, 2015

1 commit

  • Currently we need to build one U-boot image for each of the wandboard
    variants: quad, dual-lite and solo.

    By switching to SPL we can support all these variants with a single binary,
    which is very convenient.

    Based on the work from Richard Hu.

    Tested kernel booting on the three boards.

    Signed-off-by: Richard Hu
    Signed-off-by: Fabio Estevam
    Tested-by: Vagrant Cascadian
    Reviewed-by: Stefano Babic

    Fabio Estevam
     

20 Nov, 2014

1 commit


29 Oct, 2014

1 commit

  • This commit introduces a Kconfig symbol for each ARM CPU:
    CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,
    CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.
    Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selected
    for CPU_ARM1176 and CPU_V7.

    For each target, the corresponding CPU is selected and the definition of
    SYS_CPU in the corresponding Kconfig file is removed.

    Also, it removes redundant "string" type in some Kconfig files.

    Signed-off-by: Georges Savoundararadj
    Acked-by: Albert ARIBAUD
    Cc: Masahiro Yamada

    Georges Savoundararadj
     

14 Sep, 2014

1 commit

  • Now the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}
    are specified in arch/Kconfig.

    We can delete the ones in arch and board Kconfig files.

    This commit can be easily reproduced by the following command:

    find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '
    /config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ {
    N
    s/\n[[:space:]]*string//
    }
    '

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

30 Jul, 2014

2 commits

  • We have switched to Kconfig and the boards.cfg file is going to
    be removed. We have to retrieve the board status and maintainers
    information from it.

    The MAINTAINERS format as in Linux Kernel would be nice
    because we can crib the scripts/get_maintainer.pl script.

    After some discussion, we chose to put a MAINTAINERS file under each
    board directory, not the top-level one because we want to collect
    relevant information for a board into a single place.

    TODO:
    Modify get_maintainer.pl to scan multiple MAINTAINERS files.

    Signed-off-by: Masahiro Yamada
    Suggested-by: Tom Rini
    Acked-by: Simon Glass

    Masahiro Yamada
     
  • This commit adds:
    - arch/${ARCH}/Kconfig
    provide a menu to select target boards
    - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
    - configs/${TARGET_BOARD}_defconfig
    default setting of each board

    (This commit was automatically generated by a conversion script
    based on boards.cfg)

    In Linux Kernel, defconfig files are located under
    arch/${ARCH}/configs/ directory.
    It works in Linux Kernel since ARCH is always given from the
    command line for cross compile.

    But in U-Boot, ARCH is not given from the command line.
    Which means we cannot know ARCH until the board configuration is done.
    That is why all the "*_defconfig" files should be gathered into a
    single directory ./configs/.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada
     

09 May, 2014

1 commit


14 Mar, 2014

1 commit


05 Mar, 2014

4 commits


13 Jan, 2014

1 commit


13 Nov, 2013

3 commits


10 Nov, 2013

1 commit

  • Conflicts:
    arch/arm/cpu/arm926ejs/mxs/Makefile
    board/compulab/cm_t35/Makefile
    board/corscience/tricorder/Makefile
    board/ppcag/bg0900/Makefile
    drivers/bootcount/Makefile
    include/configs/omap4_common.h
    include/configs/pdnb3.h

    Makefile conflicts are due to additions/removals of
    object files on the ARM branch vs KBuild introduction
    on the main branch. Resolution consists in adjusting
    the list of object files in the main branch version.
    This also applies to two files which are not listed
    as conflicting but had to be modified:

    board/compulab/common/Makefile
    board/udoo/Makefile

    include/configs/omap4_common.h conflicts are due to
    the OMAP4 conversion to ti_armv7_common.h on the ARM
    side, and CONFIG_SYS_HZ removal on the main side.
    Resolution is to convert as this icludes removal of
    CONFIG_SYS_HZ.

    include/configs/pdnb3.h is due to a removal on ARM side.
    Trivial resolution is to remove the file.

    Note: 'git show' will also list two files just because
    they are new:

    include/configs/am335x_igep0033.h
    include/configs/omap3_igep00x0.h

    Albert ARIBAUD
     

04 Nov, 2013

1 commit


01 Nov, 2013

1 commit


31 Jul, 2013

1 commit


27 Jul, 2013

1 commit


24 Jul, 2013

1 commit


26 Jun, 2013

1 commit


03 Jun, 2013

1 commit


16 May, 2013

1 commit


28 Apr, 2013

1 commit

  • PUE requires PKE to mean something, as do pull values with PUE, so do not
    compell users to explicitly use PKE and PUE everywhere. This is also what is
    done on Linux and what has already been done for i.MX51.

    By the way, remove some unused pad control definitions.

    There is no change of behavior.

    Note that SPI_PAD_CTRL was defined by several boards with a pull value, but
    without PKE or PUE, which means that no pull was actually enabled in the pad.
    This might be a bug in those boards, but this patch does not change the
    behavior, so it just removes the meaningless pull value from those definitions.

    Signed-off-by: Benoît Thébaudeau

    Benoît Thébaudeau
     

26 Apr, 2013

1 commit