11 Feb, 2018

1 commit

  • 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
     

11 Oct, 2017

1 commit

  • 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
     

27 Sep, 2017

1 commit


16 Sep, 2017

1 commit

  • The CONFIG_BOOTSTAGE_USER_COUNT option is no-longer needed since we can now
    support any number of user IDs. Also BOOTSTAGE_ID_COUNT is not needed now.

    Drop these unused options.

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng

    Simon Glass
     

02 Sep, 2017

1 commit


28 Aug, 2017

2 commits


15 Aug, 2017

1 commit


12 Aug, 2017

1 commit


26 Jul, 2017

1 commit

  • 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
     

19 Jun, 2017

1 commit


06 Jun, 2017

1 commit


23 May, 2017

1 commit


22 May, 2017

3 commits


11 May, 2017

1 commit

  • Since this driver can be used for rk8xx series pmic,
    let's rename rk808 to rk8xx, to make it clear.

    Configs parts are done by sed -i "s/RK808/RK8XX/g" `grep RK808 -lr ./`

    Signed-off-by: Jacob Chen

    Jacob Chen
     

10 May, 2017

1 commit

  • Those tests check:
    - the ability for a phy-user to get a phy based on its name or its index
    - the ability of a phy device (provider) to manage multiple ports
    - the ability to perform operations on the phy (init,deinit,on,off)
    - the behavior of the uclass when optional operations are not implemented

    Signed-off-by: Jean-Jacques Hiblot
    Reviewed-by: Simon Glass

    Jean-Jacques Hiblot
     

01 May, 2017

5 commits


30 Apr, 2017

1 commit


28 Apr, 2017

1 commit

  • Unfortunately a test for the PWM uclass was not included when it was
    submitted. This was noticed when trying to add more functionality:

    http://patchwork.ozlabs.org/patch/748172/

    Add a simple test to get us started.

    Signed-off-by: Simon Glass

    Simon Glass
     

15 Apr, 2017

1 commit


18 Mar, 2017

1 commit

  • Boards with an apparent need for the md5sum command had the connected
    config symbol defined in their board header file.
    Move this over to the respective defconfig files now that md5sum is
    configured via Kconfig.
    (This is a manual effort, which differs from moveconfig.py, not sure
    who is right here. Boards except sandbox loose the md5sum command with
    moveconfig.py, though it was explicitly mentioned in their config.h's)

    Signed-off-by: Andre Przywara
    Reviewed-by: Simon Glass
    [trini: migrate stih410-b2260]
    Signed-off-by: Tom Rini

    Andre Przywara
     

14 Mar, 2017

1 commit


31 Jan, 2017

1 commit

  • [1] Rename CONFIG_SANDBOX_MMC to CONFIG_MMC_SANDBOX for consistency
    I want all MMC driver options prefixed with CONFIG_MMC_.

    [2] Fix dependency
    Add necessary depends on to avoid compile error.
    Instead "depends on MMC" is unneeded because this config entry
    resides inside of "if MMC".

    [3] Currently, this config symbol is not referenced at all.
    Use it to enable/disable the driver in Makefile.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

28 Jan, 2017

3 commits


24 Jan, 2017

1 commit


22 Jan, 2017

1 commit


30 Dec, 2016

1 commit

  • Commit 7a777f6d6f35 ("mmc: Add generic Kconfig option") created
    a Kconfig entry for this option without any actual moves, then
    commit 44c798799f66 ("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: Masahiro Yamada
    Reviewed-by: Jaehoon Chung

    Masahiro Yamada
     

04 Dec, 2016

1 commit

  • A number of platforms had been using the distro default feature before
    it was moved to Kconfig but did not enable the new Kconfig option when
    it was enabled. This caused a regression in terms of features and this
    introduces breakage when more things move to Kconfig.

    Signed-off-by: Tom Rini

    Tom Rini
     

28 Oct, 2016

1 commit


24 Oct, 2016

2 commits


20 Sep, 2016

1 commit

  • This reverts commit 90c08d9e08c7a108ab904f3bbdeb558081757892.

    I took a closer look at this after the commit was applied, and found
    CONFIG_SYS_MALLOC_F_LEN=0x2000 was too much. 8KB memory for SPL is
    actually too big for some boards. Perhaps 0x800 is enough, but the
    situation varies board by board.

    Let's postpone our decision until we come up with a better idea.

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Simon Glass

    Masahiro Yamada