Skip to content
Snippets Groups Projects
  1. Jan 21, 2017
    • Uri Mashiach's avatar
      status_led: Kconfig migration · 2d8d190c
      Uri Mashiach authored
      
      Move all of the status LED feature to drivers/led/Kconfig.
      The LED status definitions were moved from the board configuration
      files to the defconfig files.
      
      TBD: Move all of the definitions in the include/status_led.h to the
      relevant board's defconfig files.
      
      Tested boards: CL-SOM-AM57x, CM-T335
      
      Signed-off-by: default avatarUri Mashiach <uri.mashiach@compulab.co.il>
      2d8d190c
  2. Dec 19, 2014
  3. Oct 29, 2014
    • 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_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: default avatarGeorges Savoundararadj <savoundg@gmail.com>
      Acked-by: default avatarAlbert ARIBAUD <albert.u.boot@aribaud.net>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
      2e07c249
  4. Sep 29, 2014
  5. Sep 13, 2014
  6. Jul 30, 2014
    • 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.
      
      TODO:
      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>
      93d4334f
    • 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>
      dd84058d
  7. Nov 01, 2013
  8. Sep 10, 2013
    • Marek Vasut's avatar
      ARM: mxs: Receive r0 and r1 passed from BootROM · 7b8657e2
      Marek Vasut authored and Stefano Babic's avatar Stefano Babic committed
      
      Make sure value in register r0 and r1 is preserved and passed to
      the board_init_ll() and mxs_common_spl_init() where it can be
      processed further. The value in r0 can be configured during the
      BootStream generation to arbitary value, r1 contains pointer to
      return value from CALL'd function.
      
      This patch also clears the value in r0 before returning to BootROM
      to make sure the BootROM is not confused by this value.
      
      Finally, this patch cleans up some comments in the start.S file.
      
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Stefano Babic <sbabic@denx.de>
      7b8657e2
  9. Jul 24, 2013
  10. May 06, 2013
  11. May 05, 2013
  12. Mar 07, 2013
  13. Jan 28, 2013
  14. Jan 21, 2013
Loading