28 Feb, 2015

1 commit


26 Feb, 2015

1 commit


25 Feb, 2015

8 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
     
  • 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
     
  • 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
     

19 Feb, 2015

1 commit


14 Feb, 2015

1 commit


13 Feb, 2015

2 commits


10 Feb, 2015

2 commits


07 Feb, 2015

3 commits


06 Feb, 2015

2 commits


30 Jan, 2015

13 commits

  • Tom Rini
     
  • Add documentation on how to setup a system to use the generic distro
    configs and boot commands. This spells out what is needed to make a
    system conformant, but does not limit the board to only the defaults.

    Signed-off-by: Dennis Gilmore
    [swarren, added concept, user config, BOOT_TARGET_DEVICES sections.
    edited the rest]
    Signed-off-by: Stephen Warren

    Dennis Gilmore
     
  • Since U-Boot can support different offset lengths (0-4 bytes), add a device
    tree property to specify this. This avoids hard-coding it in the driver.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • this is an atempt to make the export of functions typesafe.
    I replaced the jumptable void ** by a struct (jt_funcs) with function pointers.
    The EXPORT_FUNC macro now has 3 fixed parameters and one
    variadic parameter
    The first is the name of the exported function,
    the rest of the parameters are used to format a functionpointer
    in the jumptable,

    the EXPORT_FUNC macros are expanded three times,
    1. to declare the members of the struct
    2. to initialize the structmember pointers
    3. to call the functions in stubs.c

    Signed-off-by: Martin Dorwig
    Acked-by: Simon Glass

    Signed-off-by: Simon Glass
    (resending to the list since my tweaks are not quite trivial)

    Martin Dorwig
     
  • Now that we have new bus features, update README.txt and the SPI docs to
    explain these.
    Signed-off-by: Simon Glass

    Simon Glass
     
  • At present we try to use the 'reg' property and device tree aliases to give
    devices a sequence number. The 'reg' property is often actually a memory
    address, so the sequence numbers thus-obtained are not useful. It would be
    better if the devices were just sequentially numbered in that case. In fact
    neither I2C nor SPI use this feature, so drop it.

    Some devices need us to look up an alias to number them within the uclass.
    Add a flag to control this, so it is not done unless it is needed.

    Adjust the tests to test this new behaviour.

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

    Simon Glass
     
  • The root device corresponds to the root device tree node, so set this up.
    Also add a few notes to the documentation.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • At present the tegra GPIO driver does not fully support the existing device
    tree binding, but add the binding file to cover the existing partial support.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • At present the exynos GPIO driver does not fully support the existing device
    tree binding, but add the binding file to cover the existing partial support.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • Add the binding file that we are about to support.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • Signed-off-by: Guilherme Maciel Ferreira

    Guilherme Maciel Ferreira
     
  • According to fit_image_print(), the "os" property from "image" node is required
    also when "type=ramdisk".

    Signed-off-by: Guilherme Maciel Ferreira

    Guilherme Maciel Ferreira
     
  • Move board/compulab/common/splash.c code to
    common/splash_source.c to make it available for everybody. This move
    renames cl_splash_screen_prepare() to splash_source_load(), and
    the compilation of this code is conditional on CONFIG_SPLASH_SOURCE.

    splash_source features:
    * Provide a standardized way for declaring board specific splash screen
    locations
    * Provide existing routines for auto loading the splash image from the
    locations as declared by the board
    * Introduce the "splashsource" environment variable, which makes it
    possible to select the splash image source.

    cm-t35 and cm-fx6 are updated to use the modified version.

    Signed-off-by: Nikita Kiryanov
    Cc: Stefano Babic
    Cc: Tom Rini
    Cc: Igor Grinberg
    Cc: Anatolij Gustschin
    Reviewed-by: Tom Rini
    Acked-by: Igor Grinberg

    Nikita Kiryanov
     

24 Jan, 2015

6 commits