Eric Lee / smarc-uboot

23 Feb, 2019

1 commit

20 Feb, 2019

2 commits

10 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
     

16 Jan, 2019

1 commit

26 Nov, 2018

2 commits

  • 9f407d4ef   Add core support for a bloblist to convey data from SPL ... Browse Code »

    At present there is no standard way in U-Boot to pass information from SPL
    to U-Boot proper. But sometimes SPL wants to convey information to U-Boot
    that U-Boot cannot easily figure out. For example, if SPL sets up SDRAM
    then it might want to pass the size of SDRAM, or the location of each
    bank, to U-Boot proper.

    Add a new 'bloblist' feature which provides this. A bloblist is set up in
    the first phase of U-Boot that runs (i.e. TPL or SPL). The location of
    this info may be in SRAM or CAR (x86 cache-as-RAM) or somewhere else.

    Information placed in this region is preserved (with a checksum) through
    TPL and SPL and ends up in U-Boot. At this point it is copied into SDRAM
    so it can be used after relocation.

    Reviewed-by: Tom Rini
    Signed-off-by: Simon Glass
    Acked-by: Andreas Dannenberg

    Simon Glass
     
  • 4d8d3056f   spl: Add support for logging in SPL and TPL ... Browse Code »

    It is sometimes useful to log information in SPL and TPL. Add support for
    this.

    Reviewed-by: Tom Rini
    Signed-off-by: Simon Glass

    Simon Glass
     

21 Nov, 2018

1 commit

05 Oct, 2018

1 commit

29 Sep, 2018

1 commit

26 Sep, 2018

1 commit

25 Aug, 2018

1 commit

  • 87c814d4c   common: kconfig: Mark AVB_VERIFY as dependent on PARTITION_UUIDS ... Browse Code »

    Avoid below compiler [1] errors, reproduced with configuration [2]:

    common/avb_verify.c: In function ‘get_unique_guid_for_partition’:
    common/avb_verify.c:692:31: error: ‘disk_partition_t {aka struct disk_partition}’ has no member named ‘uuid’
    uuid_size = sizeof(part->info.uuid);
    ^
    common/avb_verify.c:696:29: error: ‘disk_partition_t {aka struct disk_partition}’ has no member named ‘uuid’
    memcpy(guid_buf, part->info.uuid, uuid_size);
    ^
    LD drivers/built-in.o
    make[2]: *** [scripts/Makefile.build:278: common/avb_verify.o] Error 1

    [1] aarch64-linux-gnu-gcc (Linaro GCC 7.2-2017.11)
    [2] r8a7795_ulcb_defconfig, plus:
    CONFIG_AVB_VERIFY=y
    CONFIG_PARTITION_UUIDS=y
    CONFIG_UDP_FUNCTION_FASTBOOT=y
    CONFIG_LIBAVB=y

    Signed-off-by: Eugeniu Rosca
    Reviewed-by: Igor Opaniuk

    Eugeniu Rosca
     

18 Aug, 2018

1 commit

30 Jul, 2018

1 commit

24 Jul, 2018

1 commit

  • b0aa74a26   avb2.0: add proper dependencies ... Browse Code »

    1. Since libavb library alone is highly portable, introduce dedicated
    Kconfig symbol for AVB bootloader-dependent operations, so it's possible
    to build libavb separately. AVB bootloader-dependent operations include:
    * Helpers to process strings in order to build OS bootargs.
    * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
    * Helpers to alloc/init/free avb ops.
    2. Add CONFIG_FASTBOOT dependency, as fastboot buffer is
    re-used in partition verification operations.

    Reported-by: Eugeniu Rosca
    Signed-off-by: Igor Opaniuk
    Reviewed-by: Eugeniu Rosca
    Tested-by: Eugeniu Rosca

    Igor Opaniuk
     

22 Jul, 2018

1 commit

21 Jul, 2018

1 commit

28 Apr, 2018

1 commit

09 Apr, 2018

3 commits

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
     

14 Feb, 2018

1 commit

04 Feb, 2018

1 commit

  • 3707c6ee0   log: Add a way to log error-return values ... Browse Code »

    When functions return an error it propagates up the stack to the point
    where it is reported. Often the error code provides enough information
    about the root cause of the error that this is obvious what went wrong.

    However in some cases the error may be hard to trace. For example if a
    driver uses several devices to perform an operation, it may not be
    obvious which one failed.

    Add a log_ret() macro to help with this. This can be used to wrap any
    error-return value. The logging system will then output a log record when
    the original error is generated, making it easy to trace the call stack
    of the error.

    This macro can significantly impact code size, so its use is controlled
    by a Kconfig option, which is enabled for sandbox.

    Signed-off-by: Simon Glass

    Simon Glass
     

24 Jan, 2018

1 commit

08 Dec, 2017

3 commits

18 Nov, 2017

1 commit

  • b6251db8c   Kconfig: Introduce USE_BOOTCOMMAND and migrate BOOTCOMMAND ... Browse Code »
    54

    We first introduce CONFIG_USE_BOOTCOMMAND, similar to
    CONFIG_USE_BOOTARGS. We then migrate CONFIG_BOOTCOMMAND for most
    CONFIG_DISTRO_DEFAULT users. In some cases platforms have a complex
    scheme around this usage, and these have been defered for the moment so
    that platform maintainers can work on a migration plan.

    Signed-off-by: Tom Rini
    Reviewed-by: Lukasz Majewski

    Tom Rini
     

06 Oct, 2017

1 commit

05 Oct, 2017

1 commit

  • 6a3e65dea   common: Drop LOGLEVEL to 4 ... Browse Code »

    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

  • b44b30260   printk: collect printk stuff into <linux/printk.h> with loglevel support ... Browse Code »

    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
     

16 Sep, 2017

2 commits

15 Aug, 2017

2 commits

01 Aug, 2017

2 commits

31 Jul, 2017

1 commit