06 Nov, 2017

1 commit


04 Oct, 2017

1 commit

  • U-Boot widely uses error() as a bit noisier variant of printf().

    This macro causes name conflict with the following line in
    include/linux/compiler-gcc.h:

    # define __compiletime_error(message) __attribute__((error(message)))

    This prevents us from using __compiletime_error(), and makes it
    difficult to fully sync BUILD_BUG macros with Linux. (Notice
    Linux's BUILD_BUG_ON_MSG is implemented by using compiletime_assert().)

    Let's convert error() into now treewide-available pr_err().

    Done with the help of Coccinelle, excluing tools/ directory.

    The semantic patch I used is as follows:

    //
    @@@@
    -error
    +pr_err
    (...)
    //

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Simon Glass
    [trini: Re-run Coccinelle]
    Signed-off-by: Tom Rini

    Masahiro Yamada
     

22 Sep, 2017

2 commits


01 Jun, 2017

1 commit

  • These support the flat device tree. We want to use the dev_read_..()
    prefix for functions that support both flat tree and live tree. So rename
    the existing functions to avoid confusion.

    In the end we will have:

    1. dev_read_addr...() - works on devices, supports flat/live tree
    2. devfdt_get_addr...() - current functions, flat tree only
    3. of_get_address() etc. - new functions, live tree only

    All drivers will be written to use 1. That function will in turn call
    either 2 or 3 depending on whether the flat or live tree is in use.

    Note this involves changing some dead code - the imx_lpi2c.c file.

    Signed-off-by: Simon Glass

    Simon Glass
     

15 Mar, 2017

1 commit

  • Add SDHCI host controller found on STMicroelectronics SoCs

    On some ST SoCs, i.e. STiH407/STiH410, the MMC devices can live
    inside a dedicated flashSS sub-system that provides an extend subset
    of registers that can be used to configure the Arasan MMC/SD Host
    Controller.

    This means, that the SDHCI Arasan Controller can be configured to be
    eMMC4.5 or 4.3 spec compliant.

    W/o these settings the SDHCI will configure and use the MMC/SD
    controller with limited features e.g. PIO mode, no DMA, no HS etc.

    Signed-off-by: Patrice Chotard
    Reviewed-by: Simon Glass
    Reviewed-by: Jaehoon Chung

    Patrice Chotard