1. 31 8月, 2021 1 次提交
  2. 29 7月, 2021 2 次提交
  3. 28 6月, 2021 1 次提交
  4. 12 5月, 2021 1 次提交
  5. 28 4月, 2021 1 次提交
  6. 27 4月, 2021 1 次提交
  7. 21 4月, 2021 3 次提交
  8. 07 12月, 2020 1 次提交
  9. 10 10月, 2020 1 次提交
  10. 25 8月, 2020 1 次提交
    • T
      arm: mx6: Make all i.MX6 SoCs user-selectable · f27ffe41
      Tom Rini 提交于
      We have a number of platforms that are a combination of a carrier board
      and System-on-Module (SoM) that in turn allows for the board to have
      different SoCs on it.  In some cases, this is handled via board-specific
      Kconfig options.  In other cases we make use of
      CONFIG_SYS_EXTRA_OPTIONS.  This latter case however can lead to invalid
      configurations as we will not in turn get options that in Kconfig are
      selected by or depend on that setting.
      
      To resolve this, make the SoC option a choice in Kconfig and make boards
      depend on what they can support.  This change opens us up for further
      clean-ups in the cases where a single CONFIG_TARGET_xxx can support
      different SoCs and today they do not, or do not cleanly do so.
      Reported-by: NMatt Porter <mporter@konsulko.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Fabio Estevam <festevam@gmail.com>
      Cc: "NXP i.MX U-Boot Team" <uboot-imx@nxp.com>
      Cc: Soeren Moch <smoch@web.de>
      Cc: Markus Niebel <Markus.Niebel@tq-group.com>
      Cc: Igor Opaniuk <igor.opaniuk@toradex.com>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Hannes Schmelzer <hannes.schmelzer@br-automation.com>
      Cc: Otavio Salvador <otavio@ossystems.com.br>
      Cc: Nikita Kiryanov <nikita@compulab.co.il>
      Cc: Andreas Geisreiter <ageisreiter@dh-electronics.de>
      Cc: Ludwig Zenz <lzenz@dh-electronics.de>
      Cc: Lukasz Majewski <lukma@denx.de>
      Cc: Akshay Bhat <akshaybhat@timesys.com>
      Cc: Ken Lin <Ken.Lin@advantech.com.tw>
      Cc: Ian Ray <ian.ray@ge.com>
      Cc: Tim Harvey <tharvey@gateworks.com>
      Cc: Jagan Teki <jagan@amarulasolutions.com>
      Cc: Raffaele RECALCATI <raffaele.recalcati@bticino.it>
      Cc: Simone CIANNI <simone.cianni@bticino.it>
      Cc: Adam Ford <aford173@gmail.com>
      Cc: Marcin Niestroj <m.niestroj@grinn-global.com>
      Cc: "Eric Bénard" <eric@eukrea.com>
      Cc: Baruch Siach <baruch@tkos.co.il>
      Cc: Jason Liu <jason.hui.liu@nxp.com>
      Cc: Ye Li <ye.li@nxp.com>
      Cc: Eric Nelson <eric@nelint.com>
      Cc: Troy Kisky <troy.kisky@boundarydevices.com>
      Cc: Peng Fan <peng.fan@nxp.com>
      Cc: Parthiban Nallathambi <parthiban@linumiz.com>
      Cc: Marek Vasut <marex@denx.de>
      Cc: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>
      Cc: Christian Gmeiner <christian.gmeiner@gmail.com>
      Cc: Niel Fourie <lusus@denx.de>
      Cc: Martyn Welch <martyn.welch@collabora.com>
      Cc: Richard Hu <richard.hu@technexion.com>
      Cc: Stefan Roese <sr@denx.de>
      Cc: Boris Brezillon <bbrezillon@kernel.org>
      Cc: Arkadiusz Karas <arkadiusz.karas@somlabs.com>
      Cc: Breno Lima <breno.lima@nxp.com>
      Cc: Francesco Montefoschi <francesco.montefoschi@udoo.org>
      Cc: Silvio Fricke <open-source@softing.de>
      Tested-by: Matt Porter <mporter@konsulko.com> [colibri_imx6]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Reviewed-by: NMarcin Niestroj <m.niestroj@grinn-global.com>
      f27ffe41
  11. 11 8月, 2020 1 次提交
  12. 29 7月, 2020 1 次提交
  13. 17 7月, 2020 1 次提交
  14. 07 7月, 2020 1 次提交
  15. 29 4月, 2020 1 次提交
  16. 23 1月, 2020 1 次提交
  17. 05 12月, 2019 1 次提交
  18. 21 11月, 2019 2 次提交
    • T
      env: Finish migration of common ENV options · a09fea1d
      Tom Rini 提交于
      - In ARMv8 NXP Layerscape platforms we also need to make use of
        CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
      - On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
        to 0.
      - Add Kconfig entry for ENV_ADDR.
      - Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
      - Add ENV_xxx_REDUND options that depend on their primary option and
        SYS_REDUNDAND_ENVIRONMENT
      - On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
        for the pre-main-U-Boot environment location.
      - On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
        rather it being non-zero, as it will now be zero by default.
      - Rework the env_offset absolute in env/embedded.o to not use
        CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
        ENV_IS_IN_FLASH.
      - Migrate all platforms.
      
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Cc: Patrick Delaunay <patrick.delaunay@st.com>
      Cc: uboot-stm32@st-md-mailman.stormreply.com
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      Reviewed-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
      a09fea1d
    • T
      env: Add CONFIG_SYS_RELOC_GD_ENV_ADDR symbol · 8d8ee47e
      Tom Rini 提交于
      Today in initr_reloc_global_data() we use some non-obvious tests to
      determine if we need to relocate the env_addr within gd or not.  In
      order to facilitate migration of other symbols to Kconfig we need to
      introduce a new symbol for this particular use case.
      
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      8d8ee47e
  19. 23 9月, 2019 1 次提交
  20. 24 8月, 2019 1 次提交
  21. 23 6月, 2019 1 次提交
  22. 15 5月, 2019 1 次提交
    • J
      net: phy: micrel: Allow KSZ8xxx and KSZ90x1 to be used together · 77b508d3
      James Byrne 提交于
      Commit d397f7c4 ("net: phy: micrel: Separate KSZ9000 drivers from
      KSZ8000 drivers") separated the KSZ8xxx and KSZ90x1 drivers and warns
      that you shouldn't select both of them due to a device ID clash between
      the KSZ9021 and the KS8721, asserting that "it is highly unlikely for a
      system to contain both a KSZ8000 and a KSZ9000 PHY". Unfortunately
      boards like the SAMA5D3xEK do contain both types of PHY, but fortunately
      the Linux Micrel PHY driver provides a solution by using different PHY
      ID and mask values to distinguish these chips.
      
      This commit contains the following changes:
      
      - The PHY ID and mask values for the KSZ9021 and the KS8721 now match
      those used by the Linux driver.
      - The warnings about not enabling both drivers have been removed.
      - The description for PHY_MICREL_KSZ8XXX has been corrected (these are
      10/100 PHYs, not GbE PHYs).
      - PHY_MICREL_KSZ9021 and PHY_MICREL_KSZ9031 no longer select PHY_GIGE
      since this is selected by PHY_MICREL_KSZ90X1.
      - All of the relevant defconfig files have been updated now that
      PHY_MICREL_KSZ8XXX does not default to 'Y'.
      Signed-off-by: NJames Byrne <james.byrne@origamienergy.com>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      77b508d3
  23. 30 4月, 2019 2 次提交
  24. 01 2月, 2019 1 次提交
  25. 19 1月, 2019 1 次提交
    • P
      Kconfig: Migrate BOUNCE_BUFFER · 2acc24fc
      Philipp Tomsich 提交于
      The bounce buffer is used by a few drivers (most of the MMC drivers)
      to overcome limitations in their respective DMA implementation.
      
      This moves the configuration to Kconfig and makes it user-selectable
      (even though it will be a required feature to make those drivers
      work): the expected usage is for drivers depending on this to 'select'
      it unconditionally from their respective Kconfig (see follow-up
      patches).
      
      This commit includes a full migration using moveconfig.py to ensure
      that each commit compiles.  To ensure bisectability we update
      dependencies of various drivers to now select BOUNCE_BUFFER when needed.
      
      [trini: Squash all patches to ensure bisectability]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
      Reviewed-by: Otavio Salvador <otavio@ossystems.com.br> [dw_mmc portion]
      Reviewed-by: Fabio Estevam <festevam@gmail.com> [mxsmmc portion]
      Reviewed-by: Simon Glass <sjg@chromium.org> [tegra portion]
      2acc24fc
  26. 18 8月, 2018 1 次提交
  27. 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
  28. 04 6月, 2018 1 次提交
  29. 09 4月, 2018 2 次提交
  30. 08 4月, 2018 1 次提交
  31. 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
  32. 19 12月, 2017 1 次提交
  33. 18 11月, 2017 1 次提交
  34. 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