1. 21 5月, 2015 1 次提交
    • T
      ARM: omap1: Switch to use MULTI_IRQ · b694331c
      Tony Lindgren 提交于
      This allows us to get a bit further with SPARSE_IRQ and
      MULTIARCH support.
      
      Note that we now also rename omap_irq_flags to omap_l2_irq
      as that's the omap_irq_flags naming is confusing. It just
      contains the interrupt number for the l2 irq.
      
      Cc: Aaro Koskinen <aaro.koskinen@iki.fi>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b694331c
  2. 25 12月, 2012 1 次提交
  3. 13 11月, 2012 1 次提交
  4. 01 11月, 2012 1 次提交
  5. 19 10月, 2012 1 次提交
  6. 18 10月, 2012 2 次提交
    • T
      ARM: OMAP1: Move plat/tc.h to mach/tc.h for omap1 · 54b693d4
      Tony Lindgren 提交于
      We cannot keep this in plat as it causes problems
      with the ARM single zImage support.
      
      Cc: Felipe Balbi <balbi@ti.com>
      Cc: linux-pcmcia@lists.infradead.org
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      54b693d4
    • T
      ARM: OMAP: Make plat/fpga.h local to arch/arm/plat-omap · 4c98dc6b
      Tony Lindgren 提交于
      There's no need to have this file in plat/fpga.h. We can
      make it local to plat-omap replacing fpga_read/write
      functions directly with readb/writeb as that's how
      they are already defined in fpga.h.
      
      Note that 2420 based H4 is also using the fpga, so let's
      keep the led support around in plat-omap until we flip
      over mach-omap2 to device tree.
      
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Cc: linux-fbdev@vger.kernel.org
      Cc: Felipe Balbi <balbi@ti.com>
      Cc: linux-usb@vger.kernel.org
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      4c98dc6b
  7. 21 9月, 2012 2 次提交
  8. 19 9月, 2012 1 次提交
    • A
      ARM: omap: move platform_data definitions · 2203747c
      Arnd Bergmann 提交于
      Platform data for device drivers should be defined in
      include/linux/platform_data/*.h, not in the architecture
      and platform specific directories.
      
      This moves such data out of the omap include directories
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Acked-by: NNicolas Pitre <nico@linaro.org>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Cc: Kevin Hilman <khilman@ti.com>
      Cc: "Benoît Cousson" <b-cousson@ti.com>
      Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
      Cc: David Woodhouse <dwmw2@infradead.org>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      Cc: Ohad Ben-Cohen <ohad@wizery.com>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Omar Ramirez Luna <omar.ramirez@ti.com>
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Cc: Jarkko Nikula <jarkko.nikula@bitmer.com>
      Cc: Liam Girdwood <lrg@ti.com>
      Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
      Cc: Jean Pihet <j-pihet@ti.com>
      Cc: J Keerthy <j-keerthy@ti.com>
      Cc: linux-omap@vger.kernel.org
      2203747c
  9. 11 9月, 2012 1 次提交
  10. 14 5月, 2012 1 次提交
  11. 08 5月, 2012 1 次提交
  12. 13 4月, 2012 1 次提交
    • P
      ARM: OMAP1: board files: deduplicate and clean some NAND-related code · 31cde044
      Paul Walmsley 提交于
      The H2, H3, Perseus2, and FSample board files all contain the same
      duplicated code to handle NAND commands.  That code is missing
      some casts around conversions from unsigned long to void __iomem *.
      
      Consolidate the duplicated code into a new file,
      arch/arm/mach-omap1/board-nand.c.  Resolve the sparse warnings by
      adding appropriate casts:
      
      arch/arm/mach-omap1/board-h2.c:193:9: warning: incorrect type in argument 1 (different base types)
      arch/arm/mach-omap1/board-h2.c:193:9:    expected void const volatile [noderef] <asn:2>*<noident>
      arch/arm/mach-omap1/board-h2.c:193:9:    got unsigned long
      arch/arm/mach-omap1/board-perseus2.c:157:9: warning: incorrect type in argument 1 (different base types)
      arch/arm/mach-omap1/board-perseus2.c:157:9:    expected void const volatile [noderef] <asn:2>*<noident>
      arch/arm/mach-omap1/board-perseus2.c:157:9:    got unsigned long
      arch/arm/mach-omap1/board-fsample.c:199:9: warning: incorrect type in argument 1 (different base types)
      arch/arm/mach-omap1/board-fsample.c:199:9:    expected void const volatile [noderef] <asn:2>*<noident>
      arch/arm/mach-omap1/board-fsample.c:199:9:    got unsigned long
      arch/arm/mach-omap1/board-h3.c:195:9: warning: incorrect type in argument 1 (different base types)
      arch/arm/mach-omap1/board-h3.c:195:9:    expected void const volatile [noderef] <asn:2>*<noident>
      arch/arm/mach-omap1/board-h3.c:195:9:    got unsigned long
      
      Thanks to Arnd Bergmann <arnd@arndb.de> for suggesting a cleaner
      implementation of omap1_nand_cmd_ctl(), avoiding some casts.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Brian Swetland <swetland@google.com>
      Cc: Imre Deak <imre.deak@nokia.com>
      Cc: Greg Lonnon <glonnon@ridgerun.com>
      Cc: Kevin Hilman <kjh@hilman.org>
      Cc: Kevin Hilman <khilman@ti.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      31cde044
  13. 25 2月, 2012 1 次提交
  14. 23 2月, 2012 2 次提交
  15. 05 1月, 2012 1 次提交
  16. 18 11月, 2011 1 次提交
  17. 20 10月, 2011 1 次提交
  18. 22 8月, 2011 1 次提交
  19. 08 8月, 2011 1 次提交
  20. 20 6月, 2011 1 次提交
    • T
      omap: Set separate timer init functions to avoid cpu_is_omap tests · e74984e4
      Tony Lindgren 提交于
      This is needed for the following patches so we can initialize the
      rest of the hardware timers later on.
      
      As with the init_irq calls, there's no need to do cpu_is_omap calls
      during the timer init as we only care about the major omap generation.
      This means that we can initialize the sys_timer with the .timer
      entries alone.
      
      Note that for now we just set stubs for the various sys_timer entries
      that will get populated in a later patch. The following patches will
      also remove the omap_dm_timer_init calls and change the init for the
      rest of the hardware timers to happen with an arch_initcall.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Reviewed-by: NKevin Hilman <khilman@ti.com>
      e74984e4
  21. 16 6月, 2011 1 次提交
  22. 10 2月, 2011 1 次提交
  23. 28 1月, 2011 1 次提交
    • F
      arm: omap1: fix a bunch of section mismatches · bdc58fb9
      Felipe Balbi 提交于
      Fix the following section mismatches:
      WARNING: arch/arm/mach-omap1/built-in.o(.data+0x491c): Section mismatch
      in reference from the variable fsample_config to the (unknown reference)
      .init.data:(unknown)
      The variable fsample_config references
      the (unknown reference) __initdata (unknown)
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the
      variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      
      WARNING: arch/arm/mach-omap1/built-in.o(.data+0x8f0c): Section mismatch
      in reference from the variable ams_delta_config to the (unknown
      reference) .init.data:(unknown)
      The variable ams_delta_config references
      the (unknown reference) __initdata (unknown)
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the
      variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      
      WARNING: arch/arm/mach-omap1/built-in.o(.data+0x93ac): Section mismatch
      in reference from the variable ams_delta_camera_device to the (unknown
      reference) .init.data:(unknown)
      The variable ams_delta_camera_device references
      the (unknown reference) __initdata (unknown)
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the
      variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      
      WARNING: vmlinux.o(.data+0x5e94): Section mismatch in reference from the
      variable fsample_config to the (unknown reference) .init.data:(unknown)
      The variable fsample_config references
      the (unknown reference) __initdata (unknown)
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the
      variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      
      WARNING: vmlinux.o(.data+0xa484): Section mismatch in reference from the
      variable ams_delta_config to the (unknown reference)
      .init.data:(unknown)
      The variable ams_delta_config references
      the (unknown reference) __initdata (unknown)
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the
      variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      
      WARNING: vmlinux.o(.data+0xa924): Section mismatch in reference from the
      variable ams_delta_camera_device to the (unknown reference)
      .init.data:(unknown)
      The variable ams_delta_camera_device references
      the (unknown reference) __initdata (unknown)
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the
      variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      bdc58fb9
  24. 23 12月, 2010 1 次提交
  25. 08 12月, 2010 2 次提交
    • V
      OMAP: GPIO: Implement GPIO as a platform device · 77640aab
      Varadarajan, Charulatha 提交于
      Implement GPIO as a platform device.
      
      GPIO APIs are used in machine_init functions. Hence it is
      required to complete GPIO probe before board_init. Therefore
      GPIO device register and driver register are implemented as
      postcore_initcalls.
      
      omap_gpio_init() does nothing now and this function would be
      removed in the next patch as it's usage is spread across most
      of the board files.
      
      Inorder to convert GPIO as platform device, modifications are
      required in clockxxxx_data.c file for OMAP1 so that device names
      can be used to obtain clock instead of getting clocks by
      name/NULL ptr.
      
      Use runtime pm APIs (pm_runtime_put*/pm_runtime_get*) for enabling
      or disabling the clocks, modify sysconfig settings and remove usage
      of clock FW APIs.
      Note 1: Converting GPIO driver to use runtime PM APIs is not done as a
      separate patch because GPIO clock names are different for various OMAPs
      and are different for some of the banks in the same CPU. This would need
      usage of cpu_is checks and bank id checks while using clock FW APIs in
      the gpio driver. Hence while making GPIO a platform driver framework,
      PM runtime APIs are used directly.
      
      Note 2: While implementing GPIO as a platform device, pm runtime APIs
      are used as mentioned above and modification is not done in gpio's
      prepare for idle/ resume after idle functions. This would be done
      in the next patch series and GPIO driver would be made to use dev_pm_ops
      instead of sysdev_class in that series only.
      
      Due to the above, the GPIO driver implicitly relies on
      CM_AUTOIDLE = 1 on its iclk for power management to work, since the
      driver never disables its iclk.
      This would be taken care in the next patch series (see Note 3 below).
      
      Refer to
      http://www.mail-archive.com/linux-omap@vger.kernel.org/msg39112.html
      for more details.
      
      Note 3: only pm_runtime_get_sync is called in gpio's probe() and
      pm_runtime_put* is never called. This is to make the implementation
      similar to the existing GPIO code. Another patch series would be sent
      to correct this.
      
      In OMAP3 and OMAP4 gpio's debounce clocks are optional clocks. They
      are enabled/ disabled whenever required using clock framework APIs
      
      TODO:
      1. Cleanup the GPIO driver. Use function pointers and register
      offest pointers instead of using hardcoded values
      2. Remove all cpu_is_ checks and OMAP specific macros
      3. Remove usage of gpio_bank array so that only
         instance specific information is used in driver code
      4. Rename 'method'/ avoid it's usage
      5. Fix the non-wakeup gpios handling for OMAP2430, OMAP3 & OMAP4
      6. Modify gpio's prepare for idle/ resume after idle functions
         to use runtime pm implentation.
      Signed-off-by: NCharulatha V <charu@ti.com>
      Signed-off-by: NRajendra Nayak <rnayak@ti.com>
      Reviewed-by: NBasak, Partha <p-basak2@ti.com>
      Acked-by: NKevin Hilman <khilman@deeprootsystems.com>
      [tony@atomide.com: updated for bank specific revision and updated boards]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      77640aab
    • T
      omap: Fix gpio_request calls to happen as arch_initcall · c2cdaffe
      Tony Lindgren 提交于
      Looks like some boards are calling gpio_request from init_irq.
      This will make the request_irq fail, as GPIO will be initialized
      as postcore_initcall.
      Reported-by: NPaul Walmsley <paul@pwsan.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      c2cdaffe
  26. 20 10月, 2010 1 次提交
    • N
      arm: remove machine_desc.io_pg_offst and .phys_io · 6451d778
      Nicolas Pitre 提交于
      Since we're now using addruart to establish the debug mapping, we can
      remove the io_pg_offst and phys_io members of struct machine_desc.
      
      The various declarations were removed using the following script:
      
        grep -rl MACHINE_START arch/arm | xargs \
        sed -i '/MACHINE_START/,/MACHINE_END/ { /\.\(phys_io\|io_pg_offst\)/d }'
      
      [ Initial patch was from Jeremy Kerr, example script from Russell King ]
      Signed-off-by: NNicolas Pitre <nicolas.pitre@linaro.org>
      Acked-by: Eric Miao <eric.miao at canonical.com>
      6451d778
  27. 16 7月, 2010 1 次提交
  28. 05 7月, 2010 1 次提交
  29. 16 2月, 2010 1 次提交
  30. 12 12月, 2009 2 次提交
  31. 21 10月, 2009 1 次提交
    • T
      omap: headers: Move remaining headers from include/mach to include/plat · ce491cf8
      Tony Lindgren 提交于
      Move the remaining headers under plat-omap/include/mach
      to plat-omap/include/plat. Also search and replace the
      files using these headers to include using the right path.
      
      This was done with:
      
      #!/bin/bash
      mach_dir_old="arch/arm/plat-omap/include/mach"
      plat_dir_new="arch/arm/plat-omap/include/plat"
      headers=$(cd $mach_dir_old && ls *.h)
      omap_dirs="arch/arm/*omap*/ \
      drivers/video/omap \
      sound/soc/omap"
      other_files="drivers/leds/leds-ams-delta.c \
      drivers/mfd/menelaus.c \
      drivers/mfd/twl4030-core.c \
      drivers/mtd/nand/ams-delta.c"
      
      for header in $headers; do
      	old="#include <mach\/$header"
      	new="#include <plat\/$header"
      	for dir in $omap_dirs; do
      		find $dir -type f -name \*.[chS] | \
      			xargs sed -i "s/$old/$new/"
      	done
      	find drivers/ -type f -name \*omap*.[chS] | \
      		xargs sed -i "s/$old/$new/"
      	for file in $other_files; do
      		sed -i "s/$old/$new/" $file
      	done
      done
      
      for header in $(ls $mach_dir_old/*.h); do
      	git mv $header $plat_dir_new/
      done
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      ce491cf8
  32. 08 10月, 2009 2 次提交
  33. 29 8月, 2009 1 次提交
  34. 24 3月, 2009 1 次提交