Eric Lee / smarc-uboot

06 May, 2020

2 commits

07 Feb, 2020

1 commit

  • 8a6ffeda9   video: enable VIDEO_ANSI and all VIDEO_BBP options ... Browse Code »

    This partially reverts changes by commit 2cc393f32fd9
    ("video: make BPP and ANSI configs optional") since it
    caused issues with other boards (missing LCD console
    output on pinebook, x86 platform or sandbox). Enable
    all disabled options again and opt out of not supported
    color depth in board defconfigs.

    Signed-off-by: Anatolij Gustschin
    Reported-by: Vagrant Cascadian

    Anatolij Gustschin
     

23 Jan, 2020

1 commit

06 Dec, 2019

1 commit

  • 2cc393f32   video: make BPP and ANSI configs optional ... Browse Code »
    12

    Many boards do not use all selected framebuffer depth
    configurations, for such boards there is some unused
    code in video and console uclass routines. Make depth
    specific code optional to avoid dead code and slightly
    reduce binary size. Also make ANSI code optional for
    the same reason. When i.e. using only VIDEO_BPP16 the
    code size shrinks (below values when using gcc-7.3.0):

    $ ./tools/buildman/buildman -b video-wip -sS wandboard
    ...
    01: Merge git://git.denx.de/u-boot-sh
    02: video: add guards around 16bpp/32bbp code
    03: video: make BPP and ANSI configs optional
    arm: (for 1/1 boards) all -776.0 bss -8.0 text -768.0

    Signed-off-by: Anatolij Gustschin
    Tested-by: Eugen Hristev
    Tested-by: Patrice Chotard
    Tested-by: Steffen Dirkwinkel

    Anatolij Gustschin
     

04 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 Nov, 2019

1 commit

08 Oct, 2019

2 commits

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
     

30 Apr, 2019

2 commits

26 Mar, 2019

1 commit

  • 14453fbfa   Convert CONFIG_SF_DEFAULT_* to Kconfig ... Browse Code »
    36

    This converts the following to Kconfig:
    CONFIG_SF_DEFAULT_BUS
    CONFIG_SF_DEFAULT_CS
    CONFIG_SF_DEFAULT_MODE
    CONFIG_SF_DEFAULT_SPEED

    I use moveconfig script and then manual check on generated u-boot.cfg
    to solve the remaining issue.

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     

07 Feb, 2019

1 commit

  • 6d8251783   configs: Don't use SPI_FLASH_BAR as default ... Browse Code »
    12

    Now that new SPI NOR layer uses stateless 4 byte opcodes by default,
    don't enable SPI_FLASH_BAR. For SPI controllers that cannot support
    4-byte addressing, (stm32_qspi.c, fsl_qspi.c, mtk_qspi.c, ich.c,
    renesas_rpc_spi.c) add an imply clause to enable SPI_FLASH_BAR so as to
    not break functionality.

    Signed-off-by: Vignesh R
    Tested-by: Simon Goldschmidt
    Tested-by: Stefan Roese
    Tested-by: Horatiu Vultur
    Reviewed-by: Jagan Teki
    Tested-by: Jagan Teki #zynq-microzed

    Vignesh R
     

01 Feb, 2019

1 commit

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
     

14 Nov, 2018

1 commit

04 Sep, 2018

1 commit

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
     

04 Jun, 2018

1 commit

28 Apr, 2018

1 commit

  • f1b1f7706   Convert CONFIG_SPI to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_SPI

    This partly involves updating code that assumes that CONFIG_SPI implies
    things that are specific to the MPC8xx SPI driver. For now, just update
    the CONFIG tests. This also involves reworking the default for
    CONFIG_SYS_DEF_EEPROM_ADDR so that we don't set it when we cannot make a
    reasonable default, as it does not cause any compile failures.

    Signed-off-by: Adam Ford
    Signed-off-by: Tom Rini

    Adam Ford
     

09 Apr, 2018

2 commits

08 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
     

29 Dec, 2017

1 commit

  • b47b70531   imx: Unify CONFIG_BOOTDELAY ... Browse Code »

    In order to provide a consistent user experience for imx board users,
    remove the custom CONFIG_BOOTDELAY values from defconfig files, so that
    all boards can use the default two second delay.

    Signed-off-by: Fabio Estevam
    Reviewed-by: Lukasz Majewski

    Fabio Estevam
     

31 Oct, 2017

1 commit

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
     

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