Eric Lee / smarc-uboot

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
     

13 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
     

15 Apr, 2014

2 commits

  • fef8c6618   embest/mx6boards: use common detect_hdmi ... Browse Code »

    Signed-off-by: Eric Bénard

    Eric Benard
     
  • 3cbeb0f00   RiOTboard and MarSBoard: add new boards support ... Browse Code »

    RiOTboard is produced by Embest/Element 14 and is based on i.MX6 Solo
    The following features are tested :
    - UART2 (console)
    - eMMC
    - SDCard
    - uSDCard
    - Ethernet
    - USB Host (through 4 ports hub)
    - HDMI output
    - I2C 1/2/3
    - LVDS TFT with LCD8000-97C from Embest/Element 14

    Boot on eMMC and through USB loader are tested.

    For more informations on this board : http://www.riotboard.org/

    MarSBoard is produced by Embest/Element 14 and is based on i.MX6 Dual
    The following features are tested :
    - UART2 (console)
    - eMMC
    - uSDCard
    - Ethernet
    - USB Host (through 2 ports hub)
    - HDMI output
    - I2C 1/2
    - SPI NOR Flash
    - LVDS TFT with LCD8000-97C from Embest/Element 14

    Boot on SPI NOR and through USB loader are tested.

    For more informations on this board :
    http://www.embest-tech.com/shop/star/marsboard.html

    Both boards are supported by the same code base as they are based on a
    common trunk of schematics.

    Signed-off-by: Eric Bénard
    Acked-by: Stefano Babic

    Eric Benard