Eric Lee / smarc-uboot

24 Nov, 2014

1 commit

29 Oct, 2014

1 commit

  • 2e07c249a   kconfig: arm: introduce symbol for ARM CPUs ... Browse Code »
    215

    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
     

21 Oct, 2014

1 commit

09 Oct, 2014

1 commit

06 Oct, 2014

18 commits

24 Sep, 2014

1 commit

  • 155fa9af9   spi: mxc: fix sf probe when using mxc_spi ... Browse Code »
    134

    MXC SPI driver has a feature whereas a GPIO line can be used to force CS high
    across multiple transactions. This is set up by embedding the GPIO information
    in the CS value:

    cs = (cs | gpio << 8)

    This merge of cs and gpio data into one value breaks the sf probe command:
    if the use of gpio is required, invoking "sf probe " will not work, because
    the CS argument doesn't have the GPIO information in it. Instead, the user must
    use "sf probe << 8>". For example, if bank 2 gpio 30 is used to force
    cs high on cs 0, bus 0, then instead of typing "sf probe 0" the user now must
    type "sf probe 15872".

    This is inconsistent with the description of the sf probe command, and forces
    the user to be aware of implementaiton details.

    Fix this by introducing a new board function: board_spi_cs_gpio(), which will
    accept a naked CS value, and provide the driver with the relevant GPIO, if one
    is necessary.

    Cc: Eric Nelson
    Cc: Eric Benard
    Cc: Fabio Estevam
    Cc: Tim Harvey
    Cc: Stefano Babic
    Cc: Tom Rini
    Cc: Marek Vasut
    Reviewed-by: Marek Vasut
    Signed-off-by: Nikita Kiryanov
    Reviewed-by: Jagannadha Sutradharudu Teki

    Nikita Kiryanov
     

14 Sep, 2014

1 commit

  • 461be2f96   kconfig: remove redundant "string" type in arch and board Kconfigs ... Browse Code »
    43

    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
     

11 Aug, 2014

1 commit

30 Jul, 2014

2 commits

  • 93d4334f7   Add board MAINTAINERS files ... Browse Code »

    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
     
  • dd84058d2   kconfig: add board Kconfig and defconfig files ... Browse Code »

    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
     

23 Jul, 2014

1 commit

  • 0a11d6f29   mx6: Remove duplication of iomuxc structure ... Browse Code »

    There is no need to keep iomuxc_base_regs structure as it serves the exact same
    purpose of the iomuxc structure, which is to provide access to the GPR
    registers.

    The additional fields of iomuxc_base_regs are not used. Other advantage of
    'iomuxc' is that it has a shorter name and the variable declarations can fit
    into a single line.

    So remove iomuxc_base_regs structure and use iomuxc instead.

    Signed-off-by: Fabio Estevam
    Acked-by: Stefano Babic

    Fabio Estevam
     

28 Apr, 2014

1 commit

15 Apr, 2014

2 commits

19 Feb, 2014

2 commits

06 Feb, 2014

1 commit

  • f016f8ca3   usb: mv_udc: Rename to ci_udc ... Browse Code »

    The mv_udc is not marvell-specific anymore. The mv_udc is used to drive
    generic ChipIdea CI13xxx series OTG cores, so rename the driver to ci_udc
    instead.

    Signed-off-by: Marek Vasut
    Cc: Eric Nelson
    Cc: Stefano Babic

    Marek Vasut
     

26 Jan, 2014

2 commits

18 Dec, 2013

1 commit

13 Nov, 2013

1 commit

10 Nov, 2013

1 commit

  • 85b8c5c4b   Merge branch 'iu-boot/master' into 'u-boot-arm/master' ... Browse Code »

    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
     

01 Nov, 2013

1 commit