24 Feb, 2018

2 commits


23 Feb, 2018

1 commit


22 Feb, 2018

3 commits


19 Feb, 2018

2 commits

  • Memory banks with address 0 and size 0 are empty and should not be
    passed to the OS via device tree.

    Signed-off-by: Thierry Reding
    Acked-by: Stephen Warren

    Thierry Reding
     
  • Only ARM and in some configs MIPS really implement arch_fixup_fdt().
    Others just use the same boilerplate which is not good by itself,
    but what's worse if we try to build with disabled CONFIG_CMD_BOOTM
    and enabled CONFIG_OF_LIBFDT we'll hit an unknown symbol which was
    apparently implemented in arch/xxx/lib/bootm.c.

    Now with weak arch_fixup_fdt() right in image-fdt.c where it is
    used we get both items highlighted above fixed.

    Signed-off-by: Alexey Brodkin
    Cc: Daniel Schwierzeck
    Cc: Simon Glass
    Cc: York Sun
    Cc: Stefan Roese
    Reviewed-by: Tom Rini
    Reviewed-by: Daniel Schwierzeck

    Alexey Brodkin
     

15 Feb, 2018

1 commit

  • Migrate the option CONFIG_SPL_FRAMEWORK and make this gate most of the
    current set of options we have in Kconfig. We will need to have some
    options available for SPL and !SPL_FRAMEWORK so this is important. In a
    few cases we re-order existing options so that we have less escapes from
    the SPL_FRAMEWORK guard.

    Signed-off-by: Tom Rini

    Tom Rini
     

14 Feb, 2018

3 commits


13 Feb, 2018

1 commit

  • The fdt_record_loadable()-function was wedged between other functions
    that were guarded by ARCH_FIXUP_FDT_MEMORY. This could lead to linker
    errors on some configurations.

    With this change, fdt_record_loadable() is moved out of the
    ARCH_FIXUP_FDT_MEMORY guard (plus I tried to retain alphabetical
    ordering for functions by placing it appropriately).

    References: 9f45aeb ("spl: fit: implement fdt_record_loadable")
    Signed-off-by: Philipp Tomsich
    Reported-by: Michal Simek
    Tested-by: Michal Simek

    Philipp Tomsich
     

08 Feb, 2018

2 commits

  • The goal of this patch is to clean up the code related to choosing SPL
    MMC boot mode.

    The spl_boot_mode() now is called only in spl_mmc_load_image() function,
    which is only compiled in if CONFIG_SPL_MMC_SUPPORT is enabled.

    To achieve the goal, all per mach/arch implementations eligible for
    unification has been replaced with one __weak implementation.

    Signed-off-by: Lukasz Majewski
    Reviewed-by: Marek Vasut
    Reviewed-by: Stefano Babic
    Acked-by: Michal Simek (For ZynqMP)
    Reviewed-by: Fabio Estevam

    Lukasz Majewski
     
  • The second area of android image was intended to put a 2nd stage
    bootloader but in practice were rarely used (in my knowledge).

    An proposal was made to the AOSP to (re)use the second area as the dtb[1],
    This patch itself doesn't depend on that proposal being accepted but it won't
    be that helpful as well if that proposal won't be accepted. But don't do
    any harm as well.

    [1] https://android-review.googlesource.com/#/c/417447/
    Signed-off-by: Bin Chen
    Reviewed-by: Tom Rini
    Reviewed-by: Kever Yang

    Bin Chen
     

04 Feb, 2018

5 commits

  • The EFI implementation does not fit into any of the existing categories.

    Provide LOGC_EFI so that EFI related message can be filtered.

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass

    Heinrich Schuchardt
     
  • 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
     
  • At present this just outputs the message. Update it to output whatever the
    format requests.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • It is useful to be able to control the output format of log records on the
    console. As a starting point, add definitions for controlling which
    elements of the log record are displayed. Use function and message as the
    default, since these are the most useful fields.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • Category and level both use an enum for their ID values. Add functions to
    convert these IDs to strings and vice versa. This will allow the log to
    output the strings instead of the (inscrutable) values.

    At the same time, add a new 'driver-model' category, to cover core
    driver-model functions and fix an incorrect value for LOGL_MAX.

    Tests will be added with the new 'log' subcommands.

    Signed-off-by: Simon Glass
    (Updated to correct clang warnings)

    Simon Glass
     

30 Jan, 2018

1 commit


29 Jan, 2018

5 commits


28 Jan, 2018

3 commits


25 Jan, 2018

1 commit


24 Jan, 2018

3 commits

  • Change all coldfire arch files to use CONFIG_DISPLAY_CPUINFO.

    Signed-off-by: Angelo Dureghello
    Reviewed-by: Tom Rini
    ---
    Changes for v2:
    - update common/Kconfig to add M68K to the default y list

    Angelo Dureghello
     
  • The hash command function were not flushing the dcache before passing data
    to CAAM/DMA and not invalidating the dcache when getting data back.

    Due the data cache incoherency, HW accelerated hash commands used to fail
    with CAAM errors like "Invalid KEY Command".

    Check if pbuf and pout buffers are properly aligned to the cache line size
    and flush/invalidate the memory regions to address this issue.

    This solution is based in a previous work from Clemens Gruber in
    commit 598e9dccc75d ("crypto/fsl: fix BLOB encapsulation and
    decapsulation")

    Reported-by: Anatolij Gustschin
    Signed-off-by: Breno Lima
    Reviewed-by: York Sun

    Breno Lima
     
  • Adds a VID specific API in init_sequence_f and spl code flow
    namely init_func_vid which is required to adjust core voltage.

    VID specific code is required in spl, hence moving flag CONFIG_VID
    out of spl flags.

    Signed-off-by: Ashish Kumar
    Signed-off-by: Rajesh Bhagat
    Reviewed-by: York Sun

    Rajesh Bhagat
     

20 Jan, 2018

1 commit


16 Jan, 2018

1 commit


15 Jan, 2018

1 commit


12 Jan, 2018

3 commits


03 Jan, 2018

1 commit

  • While we expect to call a pointer to a valid FDT (or NULL) as the
    platform parameter to an ATF, some ATF versions are not U-Boot aware
    and have an insufficiently robust (or an overzealour) parameter
    validation: either way, this may cause a hard-stop with uncooperative
    ATF versions.

    This change adds the option to suppress passing a platform parameter
    and will always pass NULL.

    Debug output from ATF w/ this option disabled (i.e. default):
    INFO: plat_param_from_bl2: 0x291450
    Debug output from ATF w/ this option enabled:
    INFO: plat_param_from_bl2: 0

    Signed-off-by: Philipp Tomsich
    Tested-by: Philipp Tomsich
    Reviewed-by: Kever Yang

    Philipp Tomsich