1. 24 10月, 2016 1 次提交
  2. 15 10月, 2016 1 次提交
  3. 12 10月, 2016 2 次提交
  4. 02 10月, 2016 1 次提交
  5. 27 9月, 2016 1 次提交
    • T
      dfu: Migrate to Kconfig · 6828e602
      Tom Rini 提交于
      Introduce a hidden USB_FUNCTION_DFU Kconfig option and select it for
      CMD_DFU (as we must have the DFU command enabled to do anything DFU).
      Make all of the entries in drivers/dfu/Kconfig depend on CMD_DFU and add
      options for all of the back end choices that DFU can make use of.
      
      Cc: Lukasz Majewski <l.majewski@samsung.com>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Acked-by: NLukasz Majewski <l.majewski@samsung.com>
      6828e602
  6. 20 9月, 2016 1 次提交
  7. 17 9月, 2016 3 次提交
  8. 10 9月, 2016 2 次提交
  9. 09 9月, 2016 1 次提交
  10. 26 7月, 2016 1 次提交
  11. 26 4月, 2016 4 次提交
  12. 20 4月, 2016 3 次提交
  13. 26 3月, 2016 1 次提交
  14. 21 1月, 2016 1 次提交
  15. 20 1月, 2016 1 次提交
  16. 25 11月, 2015 1 次提交
  17. 22 11月, 2015 1 次提交
  18. 19 11月, 2015 1 次提交
  19. 23 10月, 2015 2 次提交
  20. 19 8月, 2015 1 次提交
  21. 26 6月, 2015 2 次提交
  22. 11 6月, 2015 1 次提交
  23. 01 6月, 2015 1 次提交
  24. 13 5月, 2015 1 次提交
  25. 19 4月, 2015 1 次提交
    • M
      dm: select CONFIG_DM* options · 58d423b8
      Masahiro Yamada 提交于
      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: NMasahiro Yamada <yamada.masahiro@socionext.com>
      58d423b8
  26. 16 3月, 2015 1 次提交
  27. 05 3月, 2015 1 次提交
  28. 30 1月, 2015 1 次提交
  29. 24 10月, 2014 1 次提交
    • S
      dm: am335x: Remove serial options from CONFIG_SYS_EXTRA_OPTIONS · 1f0d883a
      Simon Glass 提交于
      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: NSimon Glass <sjg@chromium.org>
      Acked-by: NTom Rini <trini@ti.com>
      1f0d883a