1. 16 Sep, 2016 5 commits
  2. 06 Aug, 2016 1 commit
    • Tom Rini's avatar
      omap3: Drop omap3_evm_quick_* targets · 584550d7
      Tom Rini authored
      These config targets were added well before the Kconfig migration began
      as a way to demonstrate how to make these platforms work with cut down
      features.  At this point in time they no longer serve a good purpose so
      remove them.
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      584550d7
  3. 05 Aug, 2016 1 commit
  4. 01 Apr, 2016 1 commit
  5. 29 Feb, 2016 1 commit
  6. 08 Feb, 2016 1 commit
  7. 11 Sep, 2015 3 commits
  8. 02 Sep, 2015 1 commit
  9. 13 Aug, 2015 1 commit
  10. 12 May, 2015 1 commit
  11. 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
  12. 28 Mar, 2015 2 commits
  13. 06 Mar, 2015 1 commit
  14. 24 Feb, 2015 1 commit
  15. 12 Feb, 2015 2 commits
  16. 06 Nov, 2014 1 commit
  17. 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_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
  18. 27 Oct, 2014 1 commit
  19. 23 Oct, 2014 1 commit
  20. 13 Sep, 2014 1 commit
  21. 31 Aug, 2014 1 commit