06 Jun, 2019

1 commit

  • U-Boot README recommends initializing SDRAM in board_init_f(). DA850
    was doing it as part of board_init_r() (through call to spl_board_init()
    which calls arch_cpu_init() which calls da850_ddr_setup())

    This worked fine till commit 15b8c7505819 ("davinci:
    da850evm/omapl138-lcdk: Move BSS to SDRAM because SRAM is full") moved
    BSS to SDRAM.

    Functions like mmc_initialize() called in board_init_r() assume BSS is
    available. Since SDRAM was not initialized when arch/arm/lib/crt0.S tried
    to initialize BSS to 0, BSS is not initialized correctly.

    Fix this by simply calling arch_cpu_init() from board_init_f(). Also move
    preloader_console_init() there to help debug issues with board_init_r().

    With this spl_board_init() is no longer needed, we remove it.

    Tested using MMC/SD boot on OMAP-L138 LCDK board.

    Tested-by: Adam Ford #da850evm
    Signed-off-by: Sekhar Nori
    Tested-by: Peter Howard #omapl138_lcdk

    Sekhar Nori
     

30 Apr, 2019

2 commits


26 Mar, 2019

1 commit

  • 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
     

14 Nov, 2018

1 commit

  • Now that CMD_UBI does not select CMD_MTDPARTS we need to make platforms
    that had been enabling it turn it on by hand. This exposed that we had
    not yet migrated CMD_MTDPARTS fully, so do so now.

    Fixes: 86dfa556d927 ("cmd: ubi: Remove useless call to mtdparts_init()")
    Signed-off-by: Tom Rini

    Tom Rini
     

12 Sep, 2018

1 commit


04 Sep, 2018

1 commit


18 Aug, 2018

3 commits


17 Aug, 2018

1 commit

  • 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
     

22 Jul, 2018

1 commit


04 Jun, 2018

1 commit


28 Apr, 2018

1 commit

  • 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
     

17 Apr, 2018

1 commit


08 Apr, 2018

1 commit


23 Mar, 2018

2 commits

  • Enable Driver Model and Device-tree support for omapl138 board
    in U-Boot. Also enable DM_SERIAL and DM_I2C.

    Signed-off-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Lokesh Vutla
     
  • commit 1601dd97edc6 ("davinci: omapl138_lcdk: increase PLL0 frequency")
    changed the PLL0 frequency to 456MHz, which is needed for the LCDC IP
    block. However, in doing so, it caused the PLLOUT clock to be outside
    of the allowable specifications given in the OMAP-L138 data sheet. (It
    says PLLOUT must be 600MHz max). It also uses a PLLM value outside of
    the range given in the TRM (it says PLLM must in the range 0 to 0x1f).

    So here is what we have currently:

    PLLOUT = 24 / (0 + 1) * (37 + 1) = 912MHz (out of spec)
    ^ ^ ^
    CLKIN PREDIV PLLM (out of spec)

    input to PLLDIVn = 912 / (1 + 1) = 456MHz (desired result)
    ^ ^
    PLLOUT POSTDIV

    This changes the PLLM value to 18 and the POSTDIV value to 0 so that
    PLLOUT is now within specification but we still get the desired
    result.

    PLLOUT = 24 / (0 + 1) * (18 + 1) = 456MHz (within spec)
    ^ ^ ^
    CLKIN PREDIV PLLM

    input to PLLDIVn = 456 / (0 + 1) = 456MHz (desired result)
    ^ ^
    PLLOUT POSTDIV

    Fixes: 1601dd97edc6 ("davinci: omapl138_lcdk: increase PLL0 frequency")
    Signed-off-by: David Lechner
    Reported-by: Sekhar Nori
    Tested-by: Sekhar Nori

    David Lechner
     

24 Feb, 2018

1 commit

  • 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

  • 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
     

31 Jan, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_SYS_DV_CLKMODE
    CONFIG_SYS_DA850_PLL0_POSTDIV
    CONFIG_SYS_DA850_PLL0_PLLDIV1
    CONFIG_SYS_DA850_PLL0_PLLDIV2
    CONFIG_SYS_DA850_PLL0_PLLDIV3
    CONFIG_SYS_DA850_PLL0_PLLDIV4
    CONFIG_SYS_DA850_PLL0_PLLDIV5
    CONFIG_SYS_DA850_PLL0_PLLDIV6
    CONFIG_SYS_DA850_PLL0_PLLDIV7
    CONFIG_SYS_DA850_PLL1_POSTDIV
    CONFIG_SYS_DA850_PLL1_PLLDIV1
    CONFIG_SYS_DA850_PLL1_PLLDIV2
    CONFIG_SYS_DA850_PLL1_PLLDIV3

    Signed-off-by: Adam Ford

    Adam Ford
     

23 Jan, 2018

1 commit


12 Jan, 2018

1 commit


21 Oct, 2017

1 commit

  • This converts the following to Kconfig:
    CONFIG_NAND_MXC
    CONFIG_NAND_OMAP_GPMC
    CONFIG_NAND_OMAP_GPMC_PREFETCH
    CONFIG_NAND_OMAP_ELM
    CONFIG_SPL_NAND_AM33XX_BCH
    CONFIG_SPL_NAND_SIMPLE
    CONFIG_SYS_NAND_BUSWIDTH_16BIT

    Signed-off-by: Adam Ford
    Reviewed-by: Heiko Schocher
    [trini: Finish migration of CONFIG_SPL_NAND_SIMPLE, fix some build issues,
    add CONFIG_NAND_MXC so we can do CONFIG_SYS_NAND_BUSWIDTH_16BIT]
    Signed-off-by: Tom Rini

    Adam Ford
     

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
     

05 Oct, 2017

1 commit

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

    Tom Rini
     

04 Oct, 2017

1 commit

  • 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 . 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: Masahiro Yamada
    [trini: Add in SPL_LOGLEVEL that is the same as LOGLEVEL]
    Signed-off-by: Tom Rini

    Masahiro Yamada
     

28 Aug, 2017

1 commit


15 Aug, 2017

1 commit


12 Aug, 2017

1 commit


01 Aug, 2017

1 commit

  • Migrate all remaining instances of CMD_NAND, CMD_NAND_TRIMFFS
    CMD_NAND_LOCK_UNLOCK and CMD_NAND_TORTURE from the headers into the
    defconfig files.

    Tested-by: Adam Ford
    Signed-off-by: Tom Rini
    Reviewed-by: Bin Meng

    Tom Rini
     

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
     

10 Jun, 2017

1 commit


05 Jun, 2017

1 commit

  • Any TFTP or DHCP boot on the Davinci OMAP-L138 LCDK board requires
    that the 'ethaddr' variable be defined. There are no e-fuses to store
    the ethernet mac address for this platform, and neither is a MAC
    address reserved in any format. So enable random MAC address support
    so that networking boot can be supported.

    Signed-off-by: Suman Anna
    Reviewed-by: Tom Rini
    Reviewed-by: Lokesh Vutla

    Anna, Suman
     

04 Jun, 2017

1 commit

  • Now that these symbols are in Kconfig, migrate all users. Use imply on
    a number of platforms that default to having this enabled. As part of
    this we must migrate some straglers for CMD_FAT and DOS_PARTITION.

    Signed-off-by: Tom Rini

    Tom Rini
     

01 Jun, 2017

1 commit

  • Currently these (board agnostic) commands cannot be selected using
    menuconfig and friends. Fix this the obvious way. As part of this,
    don't muddle the meaning of CONFIG_HASH_VERIFY to mean both 'hash -v'
    and "we have a hashing command" as this makes the Kconfig logic odd.

    Signed-off-by: Daniel Thompson
    [trini: Re-apply, add imply for a few cases, run moveconfig.py, also
    migrate CRC32_VERIFY]
    Signed-off-by: Tom Rini

    Daniel Thompson
     

22 May, 2017

2 commits


15 May, 2017

1 commit


12 May, 2017

1 commit

  • Now that we support using TI_COMMON_CMD_OPTIONS,
    we dont have to enable a number of commands explicitly
    in the defconfig if we enable TI_COMMON_CMD_OPTIONS.

    Enable TI_COMMON_CMD_OPTIONS and regenerate the defconfig
    using "make savedefconfig".

    CMD_GPIO has been kept disabled because there is no GPIO
    support (yet) on OMAP-L138 LCDK.

    Signed-off-by: Sekhar Nori
    Reviewed-by: Tom Rini

    Sekhar Nori