1. 23 8月, 2013 4 次提交
  2. 13 8月, 2013 1 次提交
  3. 04 7月, 2013 1 次提交
  4. 24 6月, 2013 1 次提交
    • M
      ARM: OMAP2+: AM43x: resolve SMP related build error · 22fe3b89
      Mohammed, Afzal 提交于
      If AM43x and SMP is selected, OMAP4 & OMAP5 deselected, build error as
      follows,
      
      arch/arm/mach-omap2/built-in.o: In function `scu_gp_set':
      arch/arm/mach-omap2/sleep44xx.S:131: undefined reference to `omap4_get_scu_base'
      arch/arm/mach-omap2/sleep44xx.S:132: undefined reference to `scu_power_mode'
      arch/arm/mach-omap2/built-in.o: In function `scu_gp_clear':
      arch/arm/mach-omap2/sleep44xx.S:227: undefined reference to `omap4_get_scu_base'
      arch/arm/mach-omap2/sleep44xx.S:229: undefined reference to `scu_power_mode'
      
      Resolve it by building sleep44xx.S only for OMAP4 & OMAP5.
      Signed-off-by: NAfzal Mohammed <afzal@ti.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      22fe3b89
  5. 17 6月, 2013 1 次提交
  6. 12 6月, 2013 3 次提交
    • A
      ARM: OMAP2+: AM43x: kbuild · 33f82f33
      Afzal Mohammed 提交于
      Build pieces that could be reused for AM43x - GIC related, secure
      related and common PRCM.
      Signed-off-by: NAfzal Mohammed <afzal@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      33f82f33
    • A
      ARM: OMAP2+: separate out OMAP4 restart · ab4c2e1b
      Afzal Mohammed 提交于
      Separate out OMAP4 restart and have it similar to other platforms, in
      a different file. Main motive is to reuse omap4-common on platforms
      other than OMAP4, like AM43x, even if OMAP4 is deselected (otherwise
      would have caused build breakage).
      Signed-off-by: NAfzal Mohammed <afzal@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      ab4c2e1b
    • S
      mailbox/omap: move the OMAP mailbox framework to drivers · c869c75c
      Suman Anna 提交于
      The mailbox hardware (in OMAP) uses a queued mailbox interrupt
      mechanism that provides a communication channel between processors
      through a set of registers and their associated interrupt signals
      by sending and receiving messages.
      
      The OMAP mailbox framework/driver code is moved to be under
      drivers/mailbox, in preparation for adapting to a common mailbox
      driver framework. This allows the build for OMAP mailbox to be
      enabled (it was disabled during the multi-platform support).
      
      As part of the migration from plat and mach code:
      - Kconfig symbols have been renamed to build OMAP1 or OMAP2+ drivers.
      - mailbox.h under plat-omap/plat/include has been split into a public
        and private header files. The public header has only the API related
        functions and types.
      - The module name mailbox.ko from plat-omap is changed to
        omap-mailbox.ko
      - The module name mailbox_mach.ko from mach-omapX is changed as
          mailbox_omap1.ko for OMAP1
          mailbox_omap2.ko for OMAP2+
      
      Cc: Tony Lindgren <tony@atomide.com>
      [gregkh@linuxfoundation.org: ack for staging part]
      Acked-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: NOmar Ramirez Luna <omar.ramirez@copitl.com>
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      c869c75c
  7. 09 6月, 2013 1 次提交
  8. 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
  9. 04 5月, 2013 1 次提交
    • A
      ARM: OMAP: build SMP code only for OMAP4/5 · 572b16db
      Arnd Bergmann 提交于
      The OMAP platform code assumes that SMP is only ever enabled when
      CONFIG_ARCH_OMAP4 or CONFIG_SOC_OMAP5 is enabled, which is not
      necessarirly true in a multiplatform configuration.
      
      arch/arm/mach-omap2/built-in.o: In function `omap4_smp_prepare_cpus':
       :(.init.text+0x413c): undefined reference to `omap_get_wakeupgen_base'
       :(.init.text+0x415c): undefined reference to `omap_secure_apis_support'
      arch/arm/mach-omap2/built-in.o: In function `omap4_boot_secondary':
       :(.cpuinit.text+0x28): undefined reference to `omap_get_wakeupgen_base'
       :(.cpuinit.text+0x3c): undefined reference to `omap_secure_apis_support'
      arch/arm/mach-omap2/built-in.o: In function `omap4_cpu_die':
       :(.ref.text+0x8): undefined reference to `omap_get_wakeupgen_base'
       :(.ref.text+0x10): undefined reference to `omap_secure_apis_support'
       :(.ref.text+0x4c): undefined reference to `omap4_hotplug_cpu'
       :(.ref.text+0x50): undefined reference to `omap_secure_apis_support'
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NTony Lindgren <tony@atomide.com>
      572b16db
  10. 09 4月, 2013 2 次提交
  11. 11 2月, 2013 1 次提交
    • P
      ARM: OMAP4+: AESS: enable internal auto-gating during initial setup · c02060d8
      Paul Walmsley 提交于
      Enable the AESS auto-gating control bit during AESS hwmod setup.  This
      fixes the following boot warning on OMAP4:
      
      omap_hwmod: aess: _wait_target_disable failed
      
      Without this patch, the AESS IP block does not indicate to the PRCM
      that it is idle after it is reset.  This prevents some types of SoC
      power management until something sets the auto-gating control bit.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Signed-off-by: NSebastien Guiriec <s-guiriec@ti.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Péter Ujfalusi <peter.ujfalusi@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      c02060d8
  12. 02 2月, 2013 2 次提交
  13. 12 1月, 2013 1 次提交
  14. 18 12月, 2012 1 次提交
    • T
      ARM: OMAP: Split fb.c to remove last remaining cpu_is_omap usage · 16d60bb8
      Tony Lindgren 提交于
      Looks like we missed plat-omap/fb.c for cpu_is_omap usage
      mach-omap2. This is the last user of cpu_is_omap, so let's
      quickly fix it up so we can finally remove plat/cpu.h for
      omap2lus.
      
      We want to limit cpu_is_omap macro usage to mach-omap2 only so
      we can make plat/cpu.h private. After this we can finally drop
      plat/cpu.h for omap2+.
      
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      16d60bb8
  15. 21 11月, 2012 1 次提交
  16. 15 11月, 2012 1 次提交
  17. 13 11月, 2012 1 次提交
  18. 09 11月, 2012 2 次提交
  19. 08 11月, 2012 1 次提交
    • T
      OMAP: panda: move display init from board file to dss-common.c · 0191bf36
      Tomi Valkeinen 提交于
      Device tree support for omapdss is still some way in the future.  In an
      effort to get a minimal DSS support for DT enabled kernel on selected
      OMAP4 boards, we'll go for a temporary solution: We will call the same
      non-DT omapdss setup code for OMAP4 SDP and Pandaboards from
      board-generic.c, thus enabling DSS for those boards.
      
      This patch moves the display setup code from board-omap4panda.c to
      dss-common.c. dss-common.c will be called by the board-omap4panda.c when
      running on non-DT kernel, and by board-generic.c when running on DT
      enabled kernel.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      0191bf36
  20. 01 11月, 2012 2 次提交
  21. 21 10月, 2012 5 次提交
  22. 18 10月, 2012 1 次提交
  23. 24 9月, 2012 1 次提交
    • J
      ARM: OMAP2+: PMU: Convert OMAP2/3 devices to use HWMOD · ee75d95c
      Jon Hunter 提交于
      Convert OMAP2/3 devices to use HWMOD for creating a PMU device. To support PMU
      on OMAP2 devices we only need to use MPU sub-system and so we can simply use
      the MPU HWMOD to create the PMU device. To support PMU on OMAP3 devices, we need
      to use the MPU and DEBUG sub-systems and so use these HWMODs to create the PMU
      device for OMAP3.
      
      The MPU HWMOD for OMAP2/3 devices is currently missing the PMU interrupt and so
      add the PMU interrupt to the MPU HWMOD for these devices.
      
      This change also moves the PMU code out of the mach-omap2/devices.c files into
      its own pmu.c file as suggested by Kevin Hilman to de-clutter devices.c.
      
      Cc: Ming Lei <ming.lei@canonical.com>
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: Benoit Cousson <b-cousson@ti.com>
      Cc: Paul Walmsley <paul@pwsan.com>
      Cc: Kevin Hilman <khilman@ti.com>
      Signed-off-by: NJon Hunter <jon-hunter@ti.com>
      [paul@pwsan.com: fixed checkpatch messages; updated to apply; dropped old-style
       initial filename line in header comments]
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      ee75d95c
  24. 19 9月, 2012 1 次提交
  25. 12 9月, 2012 1 次提交