1. 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
  2. 01 12月, 2012 1 次提交
    • T
      ARM: OMAP: Move plat-omap/dma-omap.h to include/linux/omap-dma.h · 45c3eb7d
      Tony Lindgren 提交于
      Based on earlier discussions[1] we attempted to find a suitable
      location for the omap DMA header in commit 2b6c4e73 (ARM: OMAP:
      DMA: Move plat/dma.h to plat-omap/dma-omap.h) until the conversion
      to dmaengine is complete.
      
      Unfortunately that was before I was able to try to test compile
      of the ARM multiplatform builds for omap2+, and the end result
      was not very good.
      
      So I'm creating yet another all over the place patch to cut the
      last dependency for building omap2+ for ARM multiplatform. After
      this, we have finally removed the driver dependencies to the
      arch/arm code, except for few drivers that are being worked on.
      
      The other option was to make the <plat-omap/dma-omap.h> path
      to work, but we'd have to add some new header directory to for
      multiplatform builds.
      
      Or we would have to manually include arch/arm/plat-omap/include
      again from arch/arm/Makefile for omap2+.
      
      Neither of these alternatives sound appealing as they will
      likely lead addition of various other headers exposed to the
      drivers, which we want to avoid for the multiplatform kernels.
      
      Since we already have a minimal include/linux/omap-dma.h,
      let's just use that instead and add a note to it to not
      use the custom omap DMA functions any longer where possible.
      
      Note that converting omap DMA to dmaengine depends on
      dmaengine supporting automatically incrementing the FIFO
      address at the device end, and converting all the remaining
      legacy drivers. So it's going to be few more merge windows.
      
      [1] https://patchwork.kernel.org/patch/1519591/#
      
      cc: Russell King <linux@arm.linux.org.uk>
      cc: Kevin Hilman <khilman@ti.com>
      cc: "Benoît Cousson" <b-cousson@ti.com>
      cc: Herbert Xu <herbert@gondor.apana.org.au>
      cc: "David S. Miller" <davem@davemloft.net>
      cc: Vinod Koul <vinod.koul@intel.com>
      cc: Dan Williams <djbw@fb.com>
      cc: Mauro Carvalho Chehab <mchehab@infradead.org>
      cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
      cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
      cc: David Woodhouse <dwmw2@infradead.org>
      cc: Kyungmin Park <kyungmin.park@samsung.com>
      cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      cc: Hans Verkuil <hans.verkuil@cisco.com>
      cc: Vaibhav Hiremath <hvaibhav@ti.com>
      cc: Lokesh Vutla <lokeshvutla@ti.com>
      cc: Rusty Russell <rusty@rustcorp.com.au>
      cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
      cc: Afzal Mohammed <afzal@ti.com>
      cc: linux-crypto@vger.kernel.org
      cc: linux-media@vger.kernel.org
      cc: linux-mtd@lists.infradead.org
      cc: linux-usb@vger.kernel.org
      cc: linux-fbdev@vger.kernel.org
      Acked-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      45c3eb7d
  3. 17 11月, 2012 2 次提交
  4. 13 11月, 2012 1 次提交
  5. 09 11月, 2012 1 次提交
  6. 07 11月, 2012 1 次提交
  7. 03 11月, 2012 1 次提交
  8. 01 11月, 2012 8 次提交
  9. 30 10月, 2012 2 次提交
    • P
      ARM: OMAP2+: WDT: move init; add read_reset_sources pdata function pointer · 37c67d03
      Paul Walmsley 提交于
      The OMAP watchdog timer driver directly calls a function exported by
      code in arch/arm/mach-omap2.  This is not good; it tightly couples
      this driver to the mach-omap2 integration code.  Instead, add a
      temporary platform_data function pointer to abstract this function
      call.  A subsequent patch will convert the watchdog driver to use this
      function pointer.
      
      This patch also moves the device creation code out of
      arch/arm/mach-omap2/devices.c and into arch/arm/mach-omap2/wd_timer.c.
      This is another step towards the removal of
      arch/arm/mach-omap2/devices.c.
      
      Cc: Wim Van Sebroeck <wim@iguana.be>
      Acked-by: NWim Van Sebroeck <wim@iguana.be>
      [paul@pwsan.com: skip wd_timer device creation when DT blob is present]
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      37c67d03
    • P
      ARM: OMAP1: CGRM: fix omap1_get_reset_sources() return type · 508c0d47
      Paul Walmsley 提交于
      An older version of the patch "ARM: OMAP1: create read_reset_sources()
      function (for initial use by watchdog)" was sent upstream, which used
      the wrong return type for the omap1_get_reset_sources() function.
      Fix it to return a u32, which is what the WDTIMER platform_data
      function pointer read_reset_sources() expects.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      508c0d47
  10. 27 10月, 2012 3 次提交
    • P
      ARM: OMAP1: usb: fix sparse warnings · eba36d77
      Paul Walmsley 提交于
      
      Resolve the following sparse warnings:
      
      arch/arm/mach-omap1/usb.c:304:12: warning: symbol 'omap1_usb0_init' was not declared. Should it be static?
      arch/arm/mach-omap1/usb.c:412:12: warning: symbol 'omap1_usb1_init' was not declared. Should it be static?
      arch/arm/mach-omap1/usb.c:478:12: warning: symbol 'omap1_usb2_init' was not declared. Should it be static?
      
      by declaring those functions as static.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Felipe Balbi <balbi@ti.com>
      [tony@atomide.com: this was missed with plat/usb.h removal]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      eba36d77
    • P
      ARM: OMAP1: fix sparse warning added by commit 4c98dc6b · 97af08b6
      Paul Walmsley 提交于
      Commit 4c98dc6b ("ARM: OMAP: Make
      plat/fpga.h local to arch/arm/plat-omap") results in a new warning from
      sparse:
      
      arch/arm/mach-omap1/fpga.c:147:6: warning: symbol 'omap1510_fpga_init_irq' was not declared. Should it be static?
      
      Fix by adding a missing include.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Tony Lindgren <tony@atomide.com>
      97af08b6
    • P
      ARM: OMAP1: fix build breakage introduced by commit 25c7d49e · 47ba7099
      Paul Walmsley 提交于
      Commit 25c7d49e ("ARM: OMAP: Make
      omap_device local to mach-omap2") broke an OMAP5912-only build here:
      
      arch/arm/mach-omap1/pm_bus.c: In function 'omap1_pm_runtime_init':
      arch/arm/mach-omap1/pm_bus.c:69:2: error: implicit declaration of function
      'cpu_class_is_omap1'
      make[1]: *** [arch/arm/mach-omap1/pm_bus.o] Error 1
      
      Fix by adding a missing include.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Tony Lindgren <tony@atomide.com>
      47ba7099
  11. 25 10月, 2012 3 次提交
  12. 21 10月, 2012 1 次提交
    • P
      ARM: OMAP1: create read_reset_sources() function (for initial use by watchdog) · b5c5353d
      Paul Walmsley 提交于
      On OMAP1, the existing OMAP watchdog driver reads a register directly
      from a non-watchdog IP block.  It also does not convert the register's
      contents into the standard WDIOF_* bits expected from the
      GETBOOTSTATUS ioctl().
      
      To move towards fixing these problems, create an function in
      arch/arm/mach-omap1 to return the reset source data.  A subsequent
      patch will provide this function to the watchdog driver via
      platform_data.
      
      In the long term, the best approach would be to move this function
      to a new OMAP1 driver that handles access to the OMAP1 Clock
      Generation and Reset Management IP block.  Then no platform_data would
      be needed.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      b5c5353d
  13. 19 10月, 2012 6 次提交
  14. 18 10月, 2012 7 次提交
  15. 16 10月, 2012 2 次提交