1. 20 6月, 2011 4 次提交
  2. 16 6月, 2011 1 次提交
  3. 01 6月, 2011 2 次提交
  4. 31 5月, 2011 1 次提交
    • J
      OMAP: fix compilation error · 046d886d
      Janusz Krzysztofik 提交于
      Forward-declare platform_device structure in
      arch/arm/plat-omap/include/plat/flash.h, otherwise compilation may break
      with:
      
      In file included from arch/arm/mach-omap1/flash.c:15:
      arch/arm/plat-omap/include/plat/flash.h:14: warning: 'struct platform_device' declared inside parameter list
      arch/arm/plat-omap/include/plat/flash.h:14: warning: its scope is only this definition or declaration, which is probably not what you want
      arch/arm/mach-omap1/flash.c:16: warning: 'struct platform_device' declared inside parameter list
      arch/arm/mach-omap1/flash.c:17: error: conflicting types for 'omap1_set_vpp'
      arch/arm/plat-omap/include/plat/flash.h:14: error: previous declaration of 'omap1_set_vpp' was here
      
      Detected and corrected while building for Amstrad Delta, confirmed with
      omap1_defconfig.
      Signed-off-by: NJanusz Krzysztofik <jkrzyszt@tis.icnet.pl>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      046d886d
  5. 27 5月, 2011 1 次提交
  6. 23 5月, 2011 1 次提交
  7. 21 5月, 2011 1 次提交
  8. 18 5月, 2011 1 次提交
  9. 13 5月, 2011 1 次提交
  10. 11 5月, 2011 3 次提交
  11. 07 5月, 2011 1 次提交
  12. 03 5月, 2011 1 次提交
  13. 20 4月, 2011 1 次提交
  14. 04 4月, 2011 1 次提交
  15. 31 3月, 2011 1 次提交
  16. 22 3月, 2011 1 次提交
  17. 19 3月, 2011 1 次提交
    • B
      ARM: OMAP2+: Fix warnings for GPMC interrupt · 77aded2f
      Balaji T K 提交于
      Commit db97eb7d
      (omap: gpmc: enable irq mode in gpmc) enabled interrupts for
      GPMC (General Purpose Memory Controller). However, looks like
      this patch only works on omap3. Fix the issues to avoid warnings
      on omap4 during the boot.
      
      GPMC: number of chip select is 8, CS0 to CS7. One less IRQ
      allocated throws below warning at boot:
      
      [    0.429290] Trying to install type control for IRQ409
      [    0.429290] Trying to set irq flags for IRQ409
      
      Resolve following warning messages in boot when irq chip is not set:
      
      [    0.429229] Trying to install interrupt handler for IRQ402
      [    0.429229] Trying to install interrupt handler for IRQ403
      [    0.429229] Trying to install interrupt handler for IRQ404
      [    0.429260] Trying to install interrupt handler for IRQ405
      [    0.429260] Trying to install interrupt handler for IRQ406
      [    0.429260] Trying to install interrupt handler for IRQ407
      [    0.429290] Trying to install interrupt handler for IRQ408
      
      Resolve following warning in OMAP4:
      [    0.429290] gpmc: irq-20 could not claim: err -22
      Signed-off-by: NBalaji T K <balajitk@ti.com>
      [tony@atomide.com: combined patches into one, updated comments]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      77aded2f
  18. 16 3月, 2011 1 次提交
  19. 15 3月, 2011 1 次提交
    • D
      omap: iovmm: don't check 'da' to set IOVMF_DA_FIXED flag · d038aee2
      David Cohen 提交于
      Currently IOVMM driver sets IOVMF_DA_FIXED/IOVMF_DA_ANON flags according
      to input 'da' address when mapping memory:
      da == 0: IOVMF_DA_ANON
      da != 0: IOVMF_DA_FIXED
      
      It prevents IOMMU to map first page with fixed 'da'. To avoid such
      issue, IOVMM will not automatically set IOVMF_DA_FIXED. It should now
      come from the user throught 'flags' parameter when mapping memory.
      As IOVMF_DA_ANON and IOVMF_DA_FIXED are mutually exclusive, IOVMF_DA_ANON
      can be removed. The driver will now check internally if IOVMF_DA_FIXED
      is set or not.
      Signed-off-by: NDavid Cohen <dacohen@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      d038aee2
  20. 12 3月, 2011 1 次提交
  21. 11 3月, 2011 5 次提交
  22. 10 3月, 2011 5 次提交
  23. 09 3月, 2011 1 次提交
  24. 08 3月, 2011 3 次提交