1. 14 1月, 2015 2 次提交
    • T
      ARM: OMAP3: Remove legacy support for am3517crane · 6b7720f9
      Tony Lindgren 提交于
      This board is working with device tree based booting so there should
      not be any need to keep the legacy booting support around. People
      using this board can boot it with appended DTB with existing bootloader.
      
      By removing the 3517 legacy booting support we can get a bit closer to
      making all of omap3 boot in device tree only mode.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      6b7720f9
    • T
      ARM: OMAP3: Remove legacy support for am3517-evm · 4d62dbda
      Tony Lindgren 提交于
      This board is working with device tree based booting so there should
      not be any need to keep the legacy booting support around. People
      using this board can boot it with appended DTB with existing bootloader.
      
      By removing the 3517 legacy booting support we can get a bit closer to
      making all of omap3 boot in device tree only mode.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      4d62dbda
  2. 20 12月, 2014 1 次提交
  3. 29 11月, 2014 1 次提交
  4. 08 11月, 2014 1 次提交
  5. 04 11月, 2014 2 次提交
  6. 17 9月, 2014 1 次提交
  7. 09 9月, 2014 2 次提交
  8. 23 7月, 2014 1 次提交
  9. 19 6月, 2014 1 次提交
    • R
      ARM: l2c: fix dependencies on PL310 errata symbols · a641f3a6
      Russell King 提交于
      A number of configurations spit out warnings similar to:
      
      warning: (SOC_IMX6 && SOC_VF610 && ARCH_OMAP4) selects PL310_ERRATA_588369 which has unmet direct dependencies (CACHE_L2X0)
      warning: (SOC_IMX6 && SOC_VF610 && ARCH_OMAP4) selects PL310_ERRATA_727915 which has unmet direct dependencies (CACHE_L2X0)
      
      Clean up the dependencies here:
      * PL310 symbols should only be selected when CACHE_L2X0 is enabled.
      * Since the cache-l2x0 code detects PL310 presence at runtime, and we will
        eventually get rid of CACHE_PL310, surround these errata options with an
        if CACHE_L2X0 conditional rather than repeating the dependency against
        each.
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      a641f3a6
  10. 17 6月, 2014 3 次提交
    • R
      ARM: use menuconfig for sub-arch menus · 21278aea
      Rob Herring 提交于
      The System Type menu is getting quite long with platforms and is
      inconsistent in handling of sub-arch specific options. Tidy up the menu
      by making platform options a menuconfig entry containing any platform
      specific config items.
      
      [arnd: change OMAP part according to suggestion from
       Tony Lindgren <tony@atomide.com>]
      Signed-off-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      21278aea
    • S
      ARM: Remove ARCH_HAS_CPUFREQ config option · 19682f72
      Stephen Boyd 提交于
      This config exists entirely to hide the cpufreq menu from the
      kernel configuration unless a platform has selected it. Nothing
      is actually built if this config is 'Y' and it just leads to more
      patches that add a select under a platform Kconfig so that some
      other CPUfreq option can be chosen. Let's remove the option so
      that we can always enable CPUfreq drivers on ARM platforms.
      Acked-by: NViresh Kumar <viresh.kumar@linaro.org>
      Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      19682f72
    • A
      ARM: omap2: fix am43xx dependency on l2x0 cache · 2ad501cc
      Arnd Bergmann 提交于
      Commit d941f86f ("ARM: l2c: AM43x: add L2 cache support") enabled
      the L2 cache support for the am43xx SoC, but caused a build regression
      when the driver for that cache controller is disabled:
      
      arch/arm/mach-omap2/built-in.o: In function `am43xx_init_early':
      :(.init.text+0xb20): undefined reference to `omap_l2_cache_init'
      
      This did not happen for OMAP4, which has the same call, but enables
      the l2x0 driver unconditionally. We could do the same thing for
      am43xx, but it seems better to allow turning it off and make the
      code work in either case.
      
      This adds an inline wrapper for omap_l2_cache_init for the disabled
      case, and removes the 'select' from OMAP4 so it becomes a user
      visible option.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Cc: linux-omap@vger.kernel.org
      2ad501cc
  11. 30 5月, 2014 1 次提交
  12. 02 4月, 2014 1 次提交
  13. 01 3月, 2014 1 次提交
  14. 20 2月, 2014 2 次提交
  15. 19 2月, 2014 1 次提交
  16. 14 2月, 2014 2 次提交
  17. 05 2月, 2014 1 次提交
  18. 03 2月, 2014 1 次提交
  19. 18 1月, 2014 1 次提交
  20. 26 11月, 2013 2 次提交
  21. 19 10月, 2013 4 次提交
  22. 08 10月, 2013 1 次提交
  23. 26 9月, 2013 1 次提交
  24. 21 8月, 2013 1 次提交
  25. 13 8月, 2013 2 次提交
  26. 25 7月, 2013 1 次提交
  27. 09 7月, 2013 1 次提交
  28. 06 7月, 2013 1 次提交
    • A
      ARM: OMAP: build mach-omap code only if needed · 59d92875
      Arnd Bergmann 提交于
      If we build a kernel with CONFIG_ARCH_OMAP2PLUS enabled but all of the
      individual SoCs disabled, we run into a large number of link errors
      because if incorrect dependencies:
      
      arch/arm/mach-omap2/built-in.o: In function `_add_initiator_dep':
      arch/arm/mach-omap2/omap_hwmod.c:691: undefined reference to `clkdm_add_sleepdep' arch/arm/mach-omap2/built-in.o: In function `_del_initiator_dep':
      arch/arm/mach-omap2/omap_hwmod.c:720: undefined reference to `clkdm_del_sleepdep' arch/arm/mach-omap2/built-in.o: In function `_enable':
      arch/arm/mach-omap2/omap_hwmod.c:2145: undefined reference to `clkdm_in_hwsup'
      arch/arm/mach-omap2/omap_hwmod.c:2147: undefined reference to `clkdm_hwmod_enable'
      arch/arm/mach-omap2/omap_hwmod.c:2191: undefined reference to `clkdm_hwmod_disable'
      arch/arm/mach-omap2/omap_hwmod.c:2146: undefined reference to `clkdm_missing_idle_reporting' arch/arm/mach-omap2/built-in.o: In function `_idle':
      arch/arm/mach-omap2/omap_hwmod.c:2235: undefined reference to `clkdm_hwmod_disable' arch/arm/mach-omap2/built-in.o: In function `_shutdown':
      arch/arm/mach-omap2/omap_hwmod.c:2338: undefined reference to `clkdm_hwmod_disable' arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_get_context_loss_count':
      arch/arm/mach-omap2/omap_hwmod.c:4071: undefined reference to `pwrdm_get_context_loss_count' arch/arm/mach-omap2/built-in.o: In function `omap_pm_clkdms_setup':
      arch/arm/mach-omap2/pm.c:114: undefined reference to `clkdm_allow_idle'
      arch/arm/mach-omap2/pm.c:117: undefined reference to `clkdm_sleep' arch/arm/mach-omap2/built-in.o: In function `omap2_common_pm_late_init':
      arch/arm/mach-omap2/pm.c:294: undefined reference to `omap_voltage_late_init' arch/arm/mach-omap2/built-in.o: In function `omap2_gpio_dev_init':
      arch/arm/mach-omap2/gpio.c:133: undefined reference to `pwrdm_can_ever_lose_context'
      
      We can avoid this if we make CONFIG_ARCH_OMAP2PLUS a silent option that
      gets enabled any time that one of the SoC versions is enabled.
      
      Cc: Tony Lindgren <tony@atomide.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      59d92875