Eric Lee / smarc-uboot

23 Jan, 2020

1 commit

05 Dec, 2019

1 commit

21 Nov, 2019

2 commits

  • a09fea1d2   env: Finish migration of common ENV options ... Browse Code »
    1

    - 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
    Cc: Joe Hershberger
    Cc: Patrick Delaunay
    Cc: uboot-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Tom Rini
    Acked-by: Joe Hershberger
    Reviewed-by: Simon Goldschmidt

    Tom Rini
     
  • 8d8ee47e0   env: Add CONFIG_SYS_RELOC_GD_ENV_ADDR symbol ... Browse Code »
    24

    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
    Cc: Joe Hershberger
    Signed-off-by: Tom Rini

    Tom Rini
     

08 Oct, 2019

1 commit

23 Sep, 2019

1 commit

24 Aug, 2019

1 commit

23 Jun, 2019

1 commit

15 May, 2019

1 commit

  • 77b508d34   net: phy: micrel: Allow KSZ8xxx and KSZ90x1 to be used together ... Browse Code »

    Commit d397f7c45b0b ("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: James Byrne
    Acked-by: Joe Hershberger

    James Byrne
     

05 May, 2019

1 commit

  • 623de3f08   Convert CONFIG_SUPPORT_EMMC_BOOT to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_SUPPORT_EMMC_BOOT

    As requested by Michal Simek , these boards
    have no eMMC so CONFIG_SUPPORT_EMMC_BOOT has not been migrated:

    xilinx_zynqmp_zc1275_revB
    xilinx_zynqmp_zc1751_xm018_dc4
    xilinx_zynqmp_zc1751_xm019_dc5
    xilinx_zynqmp_zcu100_revC
    xilinx_zynqmp_zcu102_rev1_0
    xilinx_zynqmp_zcu102_revA
    xilinx_zynqmp_zcu102_revB
    xilinx_zynqmp_zcu104_revA
    xilinx_zynqmp_zcu104_revC
    xilinx_zynqmp_zcu106_revA
    xilinx_zynqmp_zcu111_revA

    Signed-off-by: Alex Kiernan
    Acked-by: Lukasz Majewski
    Acked-by: Patrick Delaunay
    Acked-by: Ramon Fried
    Reviewed-by: Andy Shevchenko
    Tested-by: Sébastien Szymanski

    Alex Kiernan
     

30 Apr, 2019

2 commits

13 Mar, 2019

4 commits

19 Jan, 2019

1 commit

  • 2acc24fc2   Kconfig: Migrate BOUNCE_BUFFER ... Browse Code »

    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: Tom Rini
    Signed-off-by: Philipp Tomsich
    Reviewed-by: Otavio Salvador [dw_mmc portion]
    Reviewed-by: Fabio Estevam [mxsmmc portion]
    Reviewed-by: Simon Glass [tegra portion]

    Philipp Tomsich
     

11 Jan, 2019

1 commit

08 Jan, 2019

1 commit

14 Sep, 2018

7 commits

  • 9ddd1cd59   pico-imx6ul: Add Falcon mode support ... Browse Code »

    Falcon mode boots the kernel directly from SPL, without loading
    the full U-Boot.

    As pico-imx6ul does not have a GPIO for selecting Falcon versus normal
    mode, enter in Falcon mode when the customer selects the
    CONFIG_SPL_OS_BOOT option in menuconfig.

    Signed-off-by: Otavio Salvador

    Otavio Salvador
     
  • f6d805504   pico-imx6ul: Add bootmenu to choose the baseboard ... Browse Code »

    Currently the baseboards do not offer a way to autodetect which one is
    in use, so we ask the user if no value has been set.

    Signed-off-by: Otavio Salvador

    Otavio Salvador
     
  • 136f46056   pico-imx6ul: Sync defconfig with new changes ... Browse Code »

    Due the changes in previous commits, we need to resync the defconfig
    to reduce noise in next commits.

    Signed-off-by: Otavio Salvador

    Otavio Salvador
     
  • 558a37ce8   pico-imx6ul: Add bmode support ... Browse Code »

    The 'bmode' command is helpful for switching the boot media.

    In the case of pico-imx6ul there are two possible boot media:
    eMMC or USB.

    To boot from eMMC:

    => bmode emmc

    To boot from USB (via Serial Download Protocol):

    => bmode usb

    Signed-off-by: Fabio Estevam
    Signed-off-by: Fabio Berton
    Signed-off-by: Otavio Salvador

    Fabio Estevam
     
  • 3e8cdb990   pico-imx6ul: Add fastboot support ... Browse Code »

    fastboot tool is a convenient way to flash the eMMC, so
    add support for it.

    Examples of usages:

    On the pico-imx6ul U-Boot prompt:

    => fastboot 0

    On the Linux PC connected via USB:

    1. Retrieving the U-Boot version

    $ sudo fastboot getvar bootloader-version -i 0x0525
    bootloader-version: U-Boot 2018.07-rc2-00130-g0881835-dirty
    finished. total time: 0.000s

    2. Resetting the board

    $ sudo fastboot reboot -i 0x0525

    (this causes the pico-imx6ul to reboot)

    Signed-off-by: Fabio Estevam
    Signed-off-by: Fabio Berton
    Signed-off-by: Otavio Salvador

    Fabio Estevam
     
  • 82a8a9332   pico-imx6ul: Convert to SPL ... Browse Code »

    There are two versions of imx6ul pico SOMs: one with 256MB and another
    one with 512MB of RAM.

    Convert to SPL so that both versions can be supported. This patch
    doesn't rework the clock initialization to avoid changing the behavior
    in this same patch, so it will be cleaned up in future.

    Currently only the 256MB is tested/supported.

    Signed-off-by: Fabio Estevam
    Signed-off-by: Fabio Berton
    Signed-off-by: Otavio Salvador

    Fabio Estevam
     
  • 636941ff4   pico-imx6ul: Convert to distro config ... Browse Code »

    Instead of keeping a custom environment, use a more generic approach
    by switching to distro config.

    Signed-off-by: Fabio Estevam
    Signed-off-by: Otavio Salvador

    Fabio Estevam
     

18 Aug, 2018

1 commit

17 Aug, 2018

1 commit

  • 86cf1c828   configs: Migrate CONFIG_NR_DRAM_BANKS ... Browse Code »
    13

    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: Tom Rini

    Tom Rini
     

09 Apr, 2018

1 commit

24 Feb, 2018

1 commit

  • d021e9421   Convert CONFIG_BOOTP_BOOTPATH et al to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_BOOTP_BOOTPATH
    CONFIG_BOOTP_DNS
    CONFIG_BOOTP_GATEWAY
    CONFIG_BOOTP_HOSTNAME
    CONFIG_BOOTP_PXE
    CONFIG_BOOTP_SUBNETMASK
    CONFIG_CMDLINE_EDITING
    CONFIG_AUTO_COMPLETE
    CONFIG_SYS_LONGHELP
    CONFIG_SUPPORT_RAW_INITRD
    CONFIG_ENV_VARS_UBOOT_CONFIG

    Signed-off-by: Adam Ford
    [trini: Re-run the migration]
    Signed-off-by: Tom Rini

    Adam Ford
     

11 Feb, 2018

1 commit

  • 278b90ce7   configs: Migrate CONFIG_SYS_TEXT_BASE ... Browse Code »
    15

    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: Tom Rini

    Tom Rini
     

20 Nov, 2017

2 commits

11 Oct, 2017

1 commit

  • ad12dc184   cmd: Toggle the default value of CONFIG_CMD_IMLS ... Browse Code »

    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: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

04 Oct, 2017

1 commit

  • a95aee6af   usb: gadget: Make g_dnl USB settings common ... Browse Code »

    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: Simon Glass
    Reviewed-by: Lukasz Majewski
    Signed-off-by: Maxime Ripard

    Maxime Ripard
     

28 Aug, 2017

1 commit

15 Aug, 2017

1 commit

08 Aug, 2017

2 commits

26 Jul, 2017

1 commit

  • 2be296538   Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig ... Browse Code »
    20

    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: Simon Glass
    Signed-off-by: Tom Rini

    Simon Glass