1. 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
  2. 30 5月, 2014 1 次提交
  3. 02 4月, 2014 1 次提交
  4. 01 3月, 2014 1 次提交
  5. 20 2月, 2014 2 次提交
  6. 19 2月, 2014 1 次提交
  7. 14 2月, 2014 2 次提交
  8. 05 2月, 2014 1 次提交
  9. 03 2月, 2014 1 次提交
  10. 18 1月, 2014 1 次提交
  11. 26 11月, 2013 2 次提交
  12. 19 10月, 2013 4 次提交
  13. 08 10月, 2013 1 次提交
  14. 26 9月, 2013 1 次提交
  15. 21 8月, 2013 1 次提交
  16. 13 8月, 2013 2 次提交
  17. 25 7月, 2013 1 次提交
  18. 09 7月, 2013 1 次提交
  19. 06 7月, 2013 2 次提交
    • 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
    • A
      ARM: omap5: omap5 has SCU and TWD · 896eba3b
      Arnd Bergmann 提交于
      These are selected by omap4 but used in common omap4/5
      SMP code, so building an omap5-only kernel is actually
      broken without this patch.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Tony Lindgren <tony@atomide.com>
      896eba3b
  20. 04 7月, 2013 1 次提交
    • S
      ARM: OMAP5: Enable Cortex A15 errata 798181 · 62618c17
      Santosh Shilimkar 提交于
      ARM errata 798181 is applicable for OMAP5 based devices. So enable
      the same in the build. Errata extract and workaround information
      is as below.
      
      On Cortex-A15 (r0p0..r3p2) the TLBI*IS/DSB operations are not
      adequately shooting down all use of the old entries. The
      ARM_ERRATA_798181 option enables the Linux kernel workaround
      for this erratum which sends an IPI to the CPUs that are running
      the same ASID as the one being invalidated.
      
      Cc: Tony Lindgren <tony@atomide.com>
      Signed-off-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      62618c17
  21. 25 6月, 2013 2 次提交
  22. 24 6月, 2013 1 次提交
  23. 17 6月, 2013 1 次提交
  24. 12 6月, 2013 2 次提交
  25. 31 5月, 2013 3 次提交
    • T
      ARM: OMAP2+: Remove legacy mux data for omap4 · c99eb41c
      Tony Lindgren 提交于
      We can now boot with devicetree and muxing can be done
      with pinctrl-single.c.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      c99eb41c
    • T
      ARM: OMAP2+: Remove board-omap4panda.c · b42b9181
      Tony Lindgren 提交于
      We can now boot with device tree. If you don't want to update u-boot,
      you can boot with appended DTB with the following instructions:
      
      1. Make sure you have the appended DTB support in .config
      
         CONFIG_ARM_APPENDED_DTB=y
         CONFIG_ARM_ATAG_DTB_COMPAT=y
         CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND=y
      
      2. Build the zImage
      
         $ ARCH=arm CROSS_COMPILE=... make zImage
      
      3. Build the device tree blobs
      
         $ ARCH=arm CROSS_COMPILE=... make dtbs
      
      4. Append the correct panda dtb to zImage
      
         Depending on your hardware it's omap4-panda.dtb, omap4-panda-a4.dtb
         or omap4-panda-es.dtb.
      
         $ cat arch/arm/boot/zImage arch/arm/boot/dts/omap4-panda-es.dtb > /tmp/appended
      
      5. Use mkimage to produce the appended device tree uImage
      
         $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \
           -n "Linux" -d /tmp/appended /tmp/uImage
      
      Signed-off-by: Tony Lindgren <tony@atomide.com
      b42b9181
    • T
      ARM: OMAP2+: Remove board-4430sdp.c · 76787b3b
      Tony Lindgren 提交于
      We can now boot with device tree. If you don't want to update u-boot,
      you can boot with appended DTB with the following instructions:
      
      1. Make sure you have the appended DTB support in .config
      
         CONFIG_ARM_APPENDED_DTB=y
         CONFIG_ARM_ATAG_DTB_COMPAT=y
         CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND=y
      
      2. Build the zImage
      
         $ ARCH=arm CROSS_COMPILE=... make zImage
      
      3. Build the device tree blobs
      
         $ ARCH=arm CROSS_COMPILE=... make dtbs
      
      4. Append the dtb to zImage
      
         $ cat arch/arm/boot/zImage arch/arm/boot/dts/omap4-sdp.dtb > /tmp/appended
      
      5. Use mkimage to produce the appended device tree uImage
      
         $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \
           -n "Linux" -d /tmp/appended /tmp/uImage
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      76787b3b
  26. 04 5月, 2013 1 次提交
    • T
      ARM: OMAP2+: Fix unmet direct dependencies for SERIAL_OMAP · eb16d332
      Tony Lindgren 提交于
      Commit 8a6201b9 (ARM: OMAP2+: Fix unmet direct dependencies for zoom
      for 8250 serial) fixed unmet direct dependencies for 8250, but failed
      to do the same for omap serial. This can cause the following warning:
      
      warning: (ARCH_OMAP2PLUS_TYPICAL) selects SERIAL_OMAP which has
      unmet direct dependencies (TTY && HAS_IOMEM && GENERIC_HARDIRQS &&
      ARCH_OMAP2PLUS).
      
      We should not select drivers, they should be selected by the
      user. Fix the issue by removing the select and adding them to
      omap2plus_defconfig instead.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      eb16d332