26 Feb, 2015

1 commit


25 Feb, 2015

24 commits

  • This is still a non-generic board.

    Signed-off-by: Masahiro Yamada
    Acked-by: Sughosh Ganu
    Cc: Syed Mohammed Khasim
    Acked-by: Marek Vasut

    Masahiro Yamada
     
  • This is still a non-generic board.

    Signed-off-by: Masahiro Yamada
    Cc: Chan-Taek Park
    Acked-by: Marek Vasut

    Masahiro Yamada
     
  • This is still a non-generic board.

    Signed-off-by: Masahiro Yamada
    Cc: Po-Yu Chuang
    Acked-by: Marek Vasut

    Masahiro Yamada
     
  • These are still non-generic boards.

    Signed-off-by: Masahiro Yamada
    Cc: Greg Ungerer
    Acked-by: Marek Vasut

    Masahiro Yamada
     
  • This is still a non-generic board.

    Signed-off-by: Masahiro Yamada
    Cc: Lei Wen
    Acked-by: Marek Vasut

    Masahiro Yamada
     
  • This is still a non-generic board.

    Signed-off-by: Masahiro Yamada
    Cc: Matthias Weisser
    Acked-by: Marek Vasut

    Masahiro Yamada
     
  • Now CONFIG_SPL_BUILD is not defined in Kconfig, so
    "!depends on SPL_BUILD" and "if !SPL_BUILD" are redundant.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     
  • When Kconfig for U-boot was examined, one of the biggest issues was
    how to support multiple images (Normal, SPL, TPL). There were
    actually two options, "single .config" and "multiple .config".
    After some discussions and thought experiments, I chose the latter,
    i.e. to create ".config", "spl/.config", "tpl/.config" for Normal,
    SPL, TPL, respectively.

    It is true that the "multiple .config" strategy provided us the
    maximum flexibility and helped to avoid duplicating CONFIGs among
    Normal, SPL, TPL, but I have noticed some fatal problems:

    [1] It is impossible to share CONFIG options across the images.
    If you change the configuration of Main image, you often have to
    adjust some SPL configurations correspondingly. Currently, we
    cannot handle the dependencies between them. It means one of the
    biggest advantages of Kconfig is lost.

    [2] It is too painful to change both ".config" and "spl/.config".
    Sunxi guys started to work around this problem by creating a new
    configuration target. Commit cbdd9a9737cc (sunxi: kconfig: Add
    %_felconfig rule to enable FEL build of sunxi platforms.) added
    "make *_felconfig" to enable CONFIG_SPL_FEL on both images.
    Changing the configuration of multiple images in one command is a
    generic demand. The current implementation cannot propose any
    good solution about this.

    [3] Kconfig files are getting ugly and difficult to understand.
    Commit b724bd7d6349 (dm: Kconfig: Move CONFIG_SYS_MALLOC_F_LEN to
    Kconfig) has sprinkled "if !SPL_BUILD" over the Kconfig files.

    [4] The build system got more complicated than it should be.
    To adjust Linux-originated Kconfig to U-Boot, the helper script
    "scripts/multiconfig.sh" was introduced. Writing a complicated
    text processor is a shell script sometimes caused problems.

    Now I believe the "single .config" will serve us better. With it,
    all the problems above would go away. Instead, we will have to add
    some CONFIG_SPL_* (and CONFIG_TPL_*) options such as CONFIG_SPL_DM,
    but we will not have much. Anyway, this is what we do now in
    scripts/Makefile.spl.

    I admit my mistake with my apology and this commit switches to the
    single .config configuration.

    It is not so difficult to do that:

    - Remove unnecessary processings from scripts/multiconfig.sh
    This file will remain for a while to support the current defconfig
    format. It will be removed after more cleanups are done.

    - Adjust some makefiles and Kconfigs

    - Add some entries to include/config_uncmd_spl.h and the new file
    scripts/Makefile.uncmd_spl. Some CONFIG options that are not
    supported on SPL must be disabled because one .config is shared
    between SPL and U-Boot proper going forward. I know this is not
    a beautiful solution and I think we can do better, but let's see
    how much we will have to describe them.

    - update doc/README.kconfig

    More cleaning up patches will follow this.

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

    Masahiro Yamada
     
  • It is true that malloc is necessary for Driver Model before
    relocation, but there is no good reason to reserve the malloc
    space more than enough. The default value 0x400 works well.

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

    Masahiro Yamada
     
  • There 4 JRs, 4 RTICs and 8 DECOs, and set them the same stream id
    for using the same SMMU3 on LS1021A.

    Signed-off-by: Xiubo Li
    Signed-off-by: Alison Wang
    Reviewed-by: York Sun

    Alison Wang
     
  • The RCPM FSM may not be reset after power-on, for example,
    in the cases of cold boot and wakeup from deep sleep.
    It causes cache coherency problem and may block deep sleep.
    Therefore, reset them if they are not be reset.

    Signed-off-by: Chenhui Zhao
    Reviewed-by: York Sun

    chenhui zhao
     
  • Signed-off-by: Minghuan Lian
    Reviewed-by: York Sun

    Minghuan Lian
     
  • LS1021A's PCIe1 region begins 0x40_00000000; PCIe2 begins
    0x48_00000000. In order to access PCIe device, we must create
    TLB to map the 40bit physical address to 32bit virtual address.
    This patch will enable MMU after DDR is available and creates MMU
    table in DRAM to map all 4G space; then, re-use the reserved space
    to map PCIe region. The following the mapping layout.

    VA mapping:
    ------- 192MB VA map for PCIe1 with offset 0x40_0000_0000
    |-------| 192MB VA map for PCIe2 with offset 0x48_0000_0000
    |-------| 2GB VA map for 2GB DDR0 Memory space
    |\\\\\\\|
    -------
    Reviewed-by: York Sun

    Minghuan Lian
     
  • This patch is to define default values for some CCSR macros
    to make header files cleaner.

    Signed-off-by: Alison Wang
    Reviewed-by: York Sun

    Alison Wang
     
  • Upgrade Manage Complex (MC) flib API to 0.5.2. Rename directory
    fsl_mc to fsl-mc. Change the fsl-mc node in Linux device tree
    from "fsl,dprcr" to "fsl-mc". Print MC version info when
    appropriate.

    Signed-off-by: J. German Rivera
    Signed-off-by: Lijun Pan
    Reviewed-by: York Sun

    J. German Rivera
     
  • Erratum A008514 appleis to ls2085a.

    Signed-off-by: York Sun

    York Sun
     
  • Erratum A008336 applied to LS2085A.

    Signed-off-by: York Sun

    York Sun
     
  • FSL-LSCH3 platforms can have multiple DDR clocks. LS2085A has one clock for
    general DDR controlers, and another clock for DP-DDR. DDR driver needs to
    change to support multiple clocks.

    Signed-off-by: York Sun

    York Sun
     
  • Erratum A008336 requires setting EDDRTQCR1[2] in DDRC DCSR space
    for 64-bit DDR controllers.

    Signed-off-by: York Sun

    York Sun
     
  • This patch adds the fdt-fixup logic for the clock frequency of the
    NS16550A related device tree nodes.

    Signed-off-by: Bhupesh Sharma
    Reviewed-by: York Sun

    Bhupesh Sharma
     
  • Flushing L3 cache in CCN-504 requries d-cache to be disabled. Using
    assembly function to guarantee stack is not used before flushing is
    completed. Timeout is needed for simualtor on which CCN-504 is not
    implemented. Return value can be checked for timeout situation.

    Change bootm.c to disable dcache instead of simply flushing, required
    by flushing L3.

    Signed-off-by: York Sun

    York Sun
     
  • U-Boot should only add "enable-method" and "cpu-release-address"
    properties to the "cpu" node of the online cores.

    Signed-off-by: Arnab Basu
    Signed-off-by: York Sun

    Arnab Basu
     
  • According to hardware implementation, a single outer shareable global
    coherence group is defined. Inner shareable has not bee enabled.

    Signed-off-by: York Sun

    York Sun
     
  • This patch ensures that the TZPC (BP147) and TZASC-400 programming
    happens for LS2085A SoC only when the desired config flags are
    enabled and ensures that the TZPC programming is done to allow Non-secure
    (NS) + secure (S) transactions only for DCGF registers.

    The TZASC component is not present on LS2085A-Rev1, so the TZASC-400
    config flag is turned OFF for now.

    Signed-off-by: Bhupesh Sharma
    Reviewed-by: York Sun

    Bhupesh Sharma
     

22 Feb, 2015

1 commit


21 Feb, 2015

14 commits