1. 26 8月, 2019 1 次提交
  2. 14 8月, 2019 1 次提交
  3. 09 7月, 2019 1 次提交
    • M
      at91, omap2plus: configs: migrate CONFIG_ENV_ to defconfigs · a9221f3e
      Markus Klotzbuecher 提交于
      Enable the extended ENV options for AT91 and OMAP2PLUS in order to be
      able to use CONFIG_ENV_UBI_* on these architectures.
      
      As this change also makes the configs ENV_SIZE, ENV_SECT_SIZE,
      ENV_OFFSET visible to AT91 and OMAP2PLUS, migrate users of these to
      KConfig.
      
      This migration was run using an extended moveconfig.py which evaluates
      expressions such as "(512 << 10)". See patch ("moveconfig: expand
      simple expressions").
      
      All modified boards were built with SOURCE_DATE_EPOCH=0 before and
      after the change and successfully confirmed that the identical binary
      is generated (the only exception was igep00x0, which does not define
      CONFIG_ENV_IS_IN_UBI in the original board header. Once that is
      defined, the test passes too).
      
      hs: rebased patch to:
        68b90e57: "configs: tinker-rk3288 disable CONFIG_SPL_I2C_SUPPORT"
      Signed-off-by: NMarkus Klotzbuecher <markus.klotzbuecher@kistler.com>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Eugen Hristev <eugen.hristev@microchip.com>
      Cc: Tom Rini <trini@konsulko.com>
      a9221f3e
  4. 27 5月, 2019 1 次提交
  5. 18 5月, 2019 1 次提交
  6. 03 5月, 2019 1 次提交
  7. 30 4月, 2019 1 次提交
  8. 09 4月, 2019 1 次提交
    • S
      arm: at91: Remove CONFIG_AT91_HW_WDT_TIMEOUT · 05d4b8e4
      Stefan Roese 提交于
      This patch removes the CONFIG_AT91_HW_WDT_TIMEOUT as its not needed any
      more. The WD timeout value can be provided via the "timeout-sec" DT
      property. If not provided this way, the default value of 2 seconds will
      be used.
      Signed-off-by: NStefan Roese <sr@denx.de>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Andreas Bießmann <andreas@biessmann.org>
      Cc: Eugen Hristev <eugen.hristev@microchip.com>
      05d4b8e4
  9. 08 1月, 2019 1 次提交
  10. 17 11月, 2018 1 次提交
  11. 14 11月, 2018 1 次提交
  12. 04 9月, 2018 1 次提交
  13. 17 8月, 2018 1 次提交
    • T
      configs: Migrate CONFIG_NR_DRAM_BANKS · 86cf1c82
      Tom Rini 提交于
      We have the following cases:
      - CONFIG_NR_DRAM_BANKS was defined, migrate normally
      - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
        CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
      - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
        2), set this to 8.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      86cf1c82
  14. 08 8月, 2018 1 次提交
  15. 23 7月, 2018 1 次提交
  16. 22 7月, 2018 1 次提交
  17. 04 6月, 2018 1 次提交
  18. 12 4月, 2018 1 次提交
  19. 08 4月, 2018 1 次提交
  20. 11 2月, 2018 1 次提交
    • T
      configs: Migrate CONFIG_SYS_TEXT_BASE · 278b90ce
      Tom Rini 提交于
      On the NIOS2 and Xtensa architectures, we do not have
      CONFIG_SYS_TEXT_BASE set.  This is a strict migration of the current
      values into the defconfig and removing them from the headers.
      
      I did not attempt to add more default values in and for now will leave
      that to maintainers.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      278b90ce
  21. 06 2月, 2018 1 次提交
    • T
      cmd: Make CONFIG_CMD_FPGA depend on CONFIG_FPGA · a4fa8114
      Tuomas Tynkkynen 提交于
      cmd/Makefile has:
      
      ifdef CONFIG_FPGA
      obj-$(CONFIG_CMD_FPGA) += fpga.o
      endif
      
      which means that if CONFIG_FPGA is not set, CONFIG_CMD_FPGA silently
      does nothing. Let's remove that Makefile conditional and instead express
      this equivalent dependency in Kconfig, so a lot of redundant
      
       # CONFIG_CMD_FPGA is not set
      
      can be removed from board defconfigs that don't actually have an FPGA.
      Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>
      a4fa8114
  22. 11 10月, 2017 1 次提交
    • T
      cmd: Toggle the default value of CONFIG_CMD_IMLS · ad12dc18
      Tuomas Tynkkynen 提交于
      Having this as a 'default y' is rather annoying because it doesn't
      actually compile unless other options are defined in the board header:
      
      ../cmd/bootm.c: In function 'do_imls_nor':
      ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
         i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {
      
      Make it 'default n' so people who develop new boards that start from a
      blank defconfig have one less compilation failure to debug.
      Signed-off-by: NTuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
      ad12dc18
  23. 05 10月, 2017 1 次提交
    • T
      common: Drop LOGLEVEL to 4 · 6a3e65de
      Tom Rini 提交于
      While this came in with a default value of 6 I am lowering this to 4.
      The MTD/UBI code has a large number of error messages that we include
      now.  In addition, "normally" warning messages are not included so this
      feels like a more natural level to have.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      6a3e65de
  24. 04 10月, 2017 2 次提交
    • M
      printk: collect printk stuff into <linux/printk.h> with loglevel support · b44b3026
      Masahiro Yamada 提交于
      When we import code from Linux, with regular re-sync planned, we want
      to use printk() and pr_*().  U-Boot does not support them in a clean
      way.  So, people end up with local macros, or compat headers here and
      there, then we occasionally see build errors of definition conflicts.
      
      We have include/linux/compat.h, but putting all sorts of unrelated
      things into a single header is just a temporal workaround.  Hence this
      patch, to find the best home for all printk variants.  If you want to
      use printk() and friends, please include <linux/printk.h>.  This header
      is self-contained, and pulls in only a few headers.
      
      When I was testing this clean-up, I noticed the image size exceeded
      its platform limit on some boards.  This is because all pr_*() that
      were previously defined as no-op in include/linux/mtd/mtd.h (unless
      CONFIG_MTD_DEBUG is set), are now enabled.
      
      To make such boards happy, this commit also implements CONFIG_LOGLEVEL.
      The concept is similar to the kernel parameter "loglevel".  (Actually,
      the Kconfig help message was taken from kernel-paremeter.txt of Linux)
      Messages with a loglevel smaller than console loglevel will be printed.
      
      The difference is the loglevel is build-time determined.  To save the
      image size, lower priority pr_*() are compiled out.  I set the default
      of CONFIG_LOGLEVEL to 6, i.e. pr_notice and higher priority messages
      are compiled in.
      
      I adjusted CONFIG_LOGLEVEL to avoid build error for some boards.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      [trini: Add in SPL_LOGLEVEL that is the same as LOGLEVEL]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      b44b3026
    • M
      usb: gadget: Make g_dnl USB settings common · a95aee6a
      Maxime Ripard 提交于
      The g_dnl USB settings for the vendor ID, product ID and manufacturer are
      actually common settings that can and should be shared by all the gadgets.
      
      Make them common by renaming them, and convert all the users.
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      Reviewed-by: NLukasz Majewski <lukma@denx.de>
      Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      a95aee6a
  25. 28 8月, 2017 1 次提交
  26. 20 8月, 2017 1 次提交
  27. 15 8月, 2017 2 次提交
  28. 08 8月, 2017 1 次提交
  29. 01 8月, 2017 1 次提交
  30. 26 7月, 2017 1 次提交
    • S
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass 提交于
      This converts the following to Kconfig:
         CONFIG_ENV_IS_IN_MMC
         CONFIG_ENV_IS_IN_NAND
         CONFIG_ENV_IS_IN_UBI
         CONFIG_ENV_IS_NOWHERE
      
      In fact this already exists for sunxi as a 'choice' config. However not
      all the choices are available in Kconfig yet so we cannot use that. It
      would lead to more than one option being set.
      
      In addition, one purpose of this series is to allow the environment to be
      stored in more than one place. So the existing choice is converted to a
      normal config allowing each option to be set independently.
      
      There are not many opportunities for Kconfig updates to reduce the size of
      this patch. This was tested with
      
         ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC
      
      And then manual updates.  This is because for CHAIN_OF_TRUST boards they
      can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
      now.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      2be29653
  31. 25 7月, 2017 1 次提交
  32. 29 6月, 2017 1 次提交
  33. 19 3月, 2017 1 次提交
  34. 14 3月, 2017 1 次提交
  35. 28 1月, 2017 1 次提交
  36. 26 1月, 2017 1 次提交
  37. 21 1月, 2017 1 次提交
    • T
      ARM: Default to using optimized memset and memcpy routines · 40d5534c
      Tom Rini 提交于
      We have long had available optimized versions of the memset and memcpy
      functions that are borrowed from the Linux kernel.  We should use these
      in normal conditions as the speed wins in many workflows outweigh the
      relatively minor size increase.  However, we have a number of places
      where we're simply too close to size limits in SPL and must be able to
      make the size vs performance trade-off in those cases.
      
      Cc: Philippe Reynes <tremyfr@yahoo.fr>
      Cc: Eric Jarrige <eric.jarrige@armadeus.org>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Magnus Lilja <lilja.magnus@gmail.com>
      Cc: Lokesh Vutla <lokeshvutla@ti.com>
      Cc: Chander Kashyap <k.chander@samsung.com>
      Cc: Akshay Saraswat <akshay.s@samsung.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Stefan Roese <sr@denx.de>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Acked-by: NStefan Roese <sr@denx.de>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      40d5534c
  38. 30 12月, 2016 1 次提交
    • M
      mmc: complete unfinished move of CONFIG_MMC · c2726995
      Masahiro Yamada 提交于
      Commit 7a777f6d ("mmc: Add generic Kconfig option") created
      a Kconfig entry for this option without any actual moves, then
      commit 44c79879 ("sunxi: Use Kconfig CONFIG_MMC") moved
      instances only for SUNXI.
      
      We generally do not like such partial moves.  This kind of work
      is automated by tools/moveconfig.py, so it is pretty easy to
      complete this move.
      
      I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
      This shortens the configs and will ease new board porting.
      
      This commit was created as follows:
      
      [1] Edit Kconfig (remove the "depends on", add the "default",
          copy the prompt and help message from Linux)
      
      [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
      c2726995