Skip to content
Snippets Groups Projects
  1. Feb 28, 2015
  2. Feb 24, 2015
    • Masahiro Yamada's avatar
      kconfig: remove unneeded dependency on !SPL_BUILD · d648964f
      Masahiro Yamada authored
      
      Now CONFIG_SPL_BUILD is not defined in Kconfig, so
      "!depends on SPL_BUILD" and "if !SPL_BUILD" are redundant.
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      d648964f
    • Masahiro Yamada's avatar
      kconfig: switch to single .config configuration · e02ee254
      Masahiro Yamada authored
      
      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 cbdd9a97 (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 b724bd7d (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: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      e02ee254
    • Masahiro Yamada's avatar
      ARM: UniPhier: set CONFIG_SYS_MALLOC_F to the global default value · 6d4d05b1
      Masahiro Yamada authored
      
      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: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      6d4d05b1
    • chenhui zhao's avatar
      arm: ls102xa: workaround for cache coherency problem · 9f076be7
      chenhui zhao authored
      
      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: default avatarChenhui Zhao <chenhui.zhao@freescale.com>
      Reviewed-by: default avatarYork Sun <yorksun@freescale.com>
      9f076be7
    • Minghuan Lian's avatar
      arm/ls102xa: create TLB to map PCIe region · 636ef956
      Minghuan Lian authored
      
      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:
          -------  <---- 0GB
         |       |
         |       |
         |-------| <---- 0x24000000
         |///////|  ===> 192MB VA map for PCIe1 with offset 0x40_0000_0000
         |-------| <---- 0x300000000
         |       |
         |-------| <---- 0x34000000
         |///////|  ===> 192MB VA map for PCIe2 with offset 0x48_0000_0000
         |-------| <---- 0x40000000
         |       |
         |-------| <---- 0x80000000 DDR0 space start
         |\\\\\\\|
         |\\\\\\\|  ===> 2GB VA map for 2GB DDR0 Memory space
         |\\\\\\\|
         -------  <---- 4GB DDR0 space end
      
      Signed-off-by: default avatarMinghuan Lian <Minghuan.Lian@freescale.com>
      Reviewed-by: default avatarYork Sun <yorksun@freescale.com>
      636ef956
  3. Feb 21, 2015
    • Stephen Warren's avatar
      bcm2836 SoC support (used in Raspberry Pi 2 model B) · db75356f
      Stephen Warren authored
      
      The bcm2835 and bcm2836 are essentially identical, except:
      - The CPU is an ARM1176 v.s. a quad-core Cortex-A7.
      - The physical address of many IO controllers has moved.
      
      Rather than introducing a whole new bcm2836 value for $(SOC) or $(ARCH),
      update the existing bcm2835 code to handle the minor differences, and
      plumb it into the ARMv7 CPU architecture.
      
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      db75356f
    • Masahiro Yamada's avatar
      ARM: keystone: move SoC sources to mach-keystone · 39a72345
      Masahiro Yamada authored
      
      Move
      arch/arm/cpu/armv7/keystone/* -> arch/arm/mach-keystone/*
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Tom Rini <trini@ti.com>
      39a72345
    • Masahiro Yamada's avatar
      ARM: highbank: move SoC sources to mach-highbank · 72a8ff4b
      Masahiro Yamada authored
      
      Move
      arch/arm/cpu/armv7/highbank/* -> arch/arm/mach-highbank/*
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Rob Herring <robh@kernel.org>
      72a8ff4b
    • Masahiro Yamada's avatar
      ARM: tegra: collect SoC sources into mach-tegra · 09f455dc
      Masahiro Yamada authored
      
      This commit moves files as follows:
      
       arch/arm/cpu/arm720t/tegra20/*      -> arch/arm/mach-tegra/tegra20/*
       arch/arm/cpu/arm720t/tegra30/*      -> arch/arm/mach-tegra/tegra30/*
       arch/arm/cpu/arm720t/tegra114/*     -> arch/arm/mach-tegra/tegra114/*
       arch/arm/cpu/arm720t/tegra124*      -> arch/arm/mach-tegra/tegra124/*
       arch/arm/cpu/arm720t/tegra-common/* -> arch/arm/mach-tegra/*
       arch/arm/cpu/armv7/tegra20/*        -> arch/arm/mach-tegra/tegra20/*
       arch/arm/cpu/armv7/tegra30/*        -> arch/arm/mach-tegra/tegra30/*
       arch/arm/cpu/armv7/tegra114/*       -> arch/arm/mach-tegra/tegra114/*
       arch/arm/cpu/armv7/tegra124/*       -> arch/arm/mach-tegra/tegra124/*
       arch/arm/cpu/armv7/tegra-common/*   -> arch/arm/mach-tegra/*
       arch/arm/cpu/tegra20-common/*       -> arch/arm/mach-tegra/tegra20/*
       arch/arm/cpu/tegra30-common/*       -> arch/arm/mach-tegra/tegra30/*
       arch/arm/cpu/tegra114-common/*      -> arch/arm/mach-tegra/tegra114/*
       arch/arm/cpu/tegra124-common/*      -> arch/arm/mach-tegra/tegra124/*
       arch/arm/cpu/tegra-common/*         -> arch/arm/mach-tegra/*
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Tested-by: Simon Glass <sjg@chromium.org> [ on nyan-big ]
      Cc: Stephen Warren <swarren@nvidia.com>
      Cc: Tom Warren <twarren@nvidia.com>
      09f455dc
    • Masahiro Yamada's avatar
      ARM: at91: collect SoC sources into mach-at91 · 62011840
      Masahiro Yamada authored
      
      This commit moves source files as follows:
      
        arch/arm/cpu/arm920t/at91/*   -> arch/arm/mach-at91/arm920t/*
        arch/arm/cpu/arm926ejs/at91/* -> arch/arm/mach-at91/arm926ejs/*
        arch/arm/cpu/armv7/at91/*     -> arch/arm/mach-at91/armv7/*
        arch/arm/cpu/at91-common/*    -> arch/arm/mach-at91/*
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarAndreas Bießmann <andreas.devel@googlemail.co>
      62011840
  4. Feb 16, 2015
  5. Feb 13, 2015
  6. Feb 12, 2015
  7. Feb 10, 2015
  8. Feb 07, 2015
  9. Feb 06, 2015
Loading