1. 01 Apr, 2016 1 commit
  2. 13 Sep, 2015 2 commits
  3. 02 Sep, 2015 1 commit
  4. 17 Feb, 2015 1 commit
  5. 24 Nov, 2014 1 commit
  6. 29 Oct, 2014 1 commit
    • Georges Savoundararadj's avatar
      kconfig: arm: introduce symbol for ARM CPUs · 2e07c249
      Georges Savoundararadj authored
      This commit introduces a Kconfig symbol for each ARM CPU:
      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: default avatarGeorges Savoundararadj <savoundg@gmail.com>
      Acked-by: default avatarAlbert ARIBAUD <albert.u.boot@aribaud.net>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
  7. 21 Oct, 2014 1 commit
  8. 06 Oct, 2014 18 commits
  9. 24 Sep, 2014 1 commit
    • Nikita Kiryanov's avatar
      spi: mxc: fix sf probe when using mxc_spi · 155fa9af
      Nikita Kiryanov authored
      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 <cs>" will not work, because
      the CS argument doesn't have the GPIO information in it. Instead, the user must
      use "sf probe <cs | gpio << 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 <eric.nelson@boundarydevices.com>
      Cc: Eric Benard <eric@eukrea.com>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Tim Harvey <tharvey@gateworks.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Tom Rini <trini@ti.com>
      Cc: Marek Vasut <marex@denx.de>
      Reviewed-by: default avatarMarek Vasut <marex@denx.de>
      Signed-off-by: default avatarNikita Kiryanov <nikita@compulab.co.il>
      Reviewed-by: default avatarJagannadha Sutradharudu Teki <jaganna@xilinx.com>
  10. 13 Sep, 2014 1 commit
  11. 30 Jul, 2014 2 commits
    • Masahiro Yamada's avatar
      Add board MAINTAINERS files · 93d4334f
      Masahiro Yamada authored
      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.
      Modify get_maintainer.pl to scan multiple MAINTAINERS files.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Suggested-by: default avatarTom Rini <trini@ti.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
    • Masahiro Yamada's avatar
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada authored
      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: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
  12. 23 Jul, 2014 1 commit
  13. 28 Apr, 2014 1 commit
  14. 15 Apr, 2014 2 commits
  15. 19 Feb, 2014 1 commit
  16. 06 Feb, 2014 1 commit
    • Marek Vasut's avatar
      usb: mv_udc: Rename to ci_udc · f016f8ca
      Marek Vasut authored
      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
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Eric Nelson <eric.nelson@boundarydevices.com>
      Cc: Stefano Babic <sbabic@denx.de>
  17. 26 Jan, 2014 2 commits
  18. 17 Dec, 2013 1 commit
  19. 13 Nov, 2013 1 commit