1. 20 Apr, 2016 3 commits
  2. 25 Mar, 2016 1 commit
  3. 21 Jan, 2016 1 commit
  4. 20 Jan, 2016 1 commit
  5. 25 Nov, 2015 1 commit
  6. 22 Nov, 2015 1 commit
  7. 18 Nov, 2015 1 commit
  8. 22 Oct, 2015 2 commits
  9. 18 Aug, 2015 1 commit
  10. 26 Jun, 2015 2 commits
  11. 11 Jun, 2015 1 commit
  12. 01 Jun, 2015 1 commit
  13. 12 May, 2015 1 commit
  14. 18 Apr, 2015 1 commit
    • Masahiro Yamada's avatar
      dm: select CONFIG_DM* options · 58d423b8
      Masahiro Yamada authored
      As mentioned in the previous commit, adding default values in each
      Kconfig causes problems because it does not co-exist with the
      "depends on" syntax.  (Please note this is not a bug of Kconfig.)
      We should not do so unless we have a special reason.  Actually,
      for CONFIG_DM*, we have no good reason to do so.
      
      Generally, CONFIG_DM is not a user-configurable option.  Once we
      convert a driver into Driver Model, the board only works with Driver
      Model, i.e. CONFIG_DM must be always enabled for that board.
      So, using "select DM" is more suitable rather than allowing users to
      modify it.  Another good thing is, Kconfig warns unmet dependencies
      for "select" syntax, so we easily notice bugs.
      
      Actually, CONFIG_DM and other related options have been added
      without consistency: some into arch/*/Kconfig, some into
      board/*/Kconfig, and some into configs/*_defconfig.
      
      This commit prefers "select" and cleans up the following issues.
      
      [1] Never use "CONFIG_DM=n" in defconfig files
      
      It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
      It is more common to use "# CONFIG_FOO is not set".  But here, we
      do not even have to do it.
      Less than half of OMAP3 boards have been converted to Driver Model.
      Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
      weird.  Instead, add "select DM" only to appropriate boards, which
      eventually eliminates "CONFIG_DM=n", etc.
      
      [2] Delete redundant CONFIGs
      
      Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
      in configs/sandbox_defconfig.
      Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
      defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      58d423b8
  15. 15 Mar, 2015 1 commit
  16. 04 Mar, 2015 1 commit
  17. 30 Jan, 2015 1 commit
  18. 24 Oct, 2014 1 commit
    • Simon Glass's avatar
      dm: am335x: Remove serial options from CONFIG_SYS_EXTRA_OPTIONS · 1f0d883a
      Simon Glass authored
      With these options in place it is not possible to change the serial port
      using 'make menuconfig' or similar. It seems to result in duplicate
      defines.
      
      For example:
      
      In file included from include/linux/kconfig.h:4:0,
                       from <command-line>:0:
      include/generated/autoconf.h:20:0: note: this is the location of the previous definition
       #define CONFIG_CONS_INDEX 2
       ^
      
      The default option seems to be 1 anyway, in board/ti/am335x/Kconfig.
      
      Remove the options so that we can adjust the serial port if required.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Acked-by: default avatarTom Rini <trini@ti.com>
      1f0d883a
  19. 25 Sep, 2014 2 commits
  20. 30 Jul, 2014 1 commit
    • 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