1. 25 2月, 2012 1 次提交
  2. 23 2月, 2012 1 次提交
    • T
      OMAP1: pass LCD config with omapfb_set_lcd_config() · ddba6c7f
      Tomi Valkeinen 提交于
      LCD config for old omapfb driver is passed with OMAP_TAG_LCD from board
      files or from the bootloader. In an effort to remove OMAP_TAG_LCD, this
      patch adds omapfb_set_lcd_config() function that the board files can
      call to set the LCD config.
      
      This has the drawback that configuration can no longer come from the
      bootloader. Of the boards supported by the kernel, this should only
      affect N770 which depends on the data from the bootloader. This patch
      adds an LCD config for N770 to its board files, but that is most
      probably broken. Fixing this would need information about the HW setup
      in N770 boards.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      ddba6c7f
  3. 05 1月, 2012 1 次提交
  4. 18 11月, 2011 1 次提交
  5. 10 11月, 2011 1 次提交
  6. 01 11月, 2011 1 次提交
  7. 20 10月, 2011 1 次提交
  8. 22 8月, 2011 1 次提交
  9. 08 8月, 2011 1 次提交
  10. 04 7月, 2011 1 次提交
    • J
      omap: drop __initdata tags from static struct platform_device declarations · 07ad6ab3
      Janusz Krzysztofik 提交于
      Pointers to statically declared platform device structures which are
      registered with platform_device_register() are then used during run time
      to access these structure members, for example from platform_uevent()
      and much more. Therefore, these structures should never be placed inside
      sections which are dropped after boot. Fix platform devices incorrectly
      tagged with __initdata which happen to exist inside OMAP sub-trees.
      
      This bug has exhibited itself on my ARM/OMAP1 based Amstrad Delta
      videophone after commit 6d3163ce, "mm:
      check if any page in a pageblock is reserved before marking it
      MIGRATE_RESERVE", resulting in reading from several
      /sys/device/platform/*/uevent files always ending up with segmentation
      faults.
      Signed-off-by: NJanusz Krzysztofik <jkrzyszt@tis.icnet.pl>
      Acked-by: NFelipe Balbi <balbi@ti.com>
      Cc: Varadarajan, Charulatha <charu@ti.com>
      Cc: Jarkko Nikula <jhnikula@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      07ad6ab3
  11. 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
  12. 16 6月, 2011 1 次提交
  13. 10 2月, 2011 1 次提交
  14. 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
  15. 06 1月, 2011 2 次提交
  16. 23 12月, 2010 1 次提交
  17. 11 12月, 2010 1 次提交
  18. 08 12月, 2010 1 次提交
    • 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
  19. 01 12月, 2010 1 次提交
  20. 25 11月, 2010 1 次提交
  21. 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
  22. 02 10月, 2010 2 次提交
  23. 16 7月, 2010 1 次提交
  24. 05 7月, 2010 1 次提交
  25. 06 5月, 2010 2 次提交
  26. 23 10月, 2009 2 次提交
    • J
      omap1: Fix DSP public peripherals support for ams-delta · b3dba0b8
      Janusz Krzysztofik 提交于
      DSP public peripherals used to work on OMAP1510 based (or all OMAP1 class?)
      machines as long as old dspgateway code were present in the l-o tree. For
      several months it is no longer included, breaking support for McBSP1 based
      audio on Amstrad Delta, for example.
      
      This patch, derived from the old dspgateway code, corrects the problem for the
      board by simply taking the DSP out of reset state, I guess. That way, things
      should not break when a new dsp code is added to the tree, and the change can
      be reverted then.
      
      If there are any reports on McBSP1 or other DSP public peripherals not working
      for other OMAP1 machines (I've not heard of any for now), I can prepare a more
      general patch providing an extra include file with a helper function defined.
      
      Created and tested against linux-2.6.32-rc5
      Signed-off-by: NJanusz Krzysztofik <jkrzyszt@tis.icnet.pl>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b3dba0b8
    • J
      omap1: Fix redundant UARTs pin muxing that can break other hardware support · c33da3a8
      Janusz Krzysztofik 提交于
      Commit 15ac408e removed enabled_uart
      and OMAP_TAG_UART. This works for mach-omap2, but causes issues on
      mach-omap1 for some boards as the mach-omap1 serial.c was muxing
      pins based on the enabled_uart flag for 15xx.
      
      Fix this by muxing pins in board-*.c files for the 15xx boards for
      the uart ports that had enabled_uart flag set before the commit
      above.
      
      Tested on Amsdtrad Delta only.
      
      Note that in the future we should add support for powering down
      the uarts with a timer like mach-omap2/serial.c does. Otherwise
      the enabled uarts will be blocking retention-while-idle.
      Signed-off-by: NJanusz Krzysztofik <jkrzyszt@tis.icnet.pl>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      c33da3a8
  27. 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
  28. 29 8月, 2009 2 次提交
  29. 24 3月, 2009 1 次提交
    • F
      ARM: OMAP: get rid of OMAP_TAG_USB, v2 · b0b5aa3f
      Felipe Balbi 提交于
      OMAP_TAGS should vanish soon since they're not generic arm tags.
      Most of them can be converted to a platform_data or parsed
      from a command line like e.g. serial tag.
      
      For OMAP_TAG_USB we just let boards call omap_usb_init()
      passing a pointer to omap_usb_config.
      
      Patch updated by Tony for mainline, basically make
      n770 and h4 compile. Also folded in a fix for OSK
      by David Brownell <dbrownell@users.sourceforge.net>.
      Signed-off-by: NFelipe Balbi <felipe.balbi@nokia.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b0b5aa3f
  30. 07 8月, 2008 2 次提交
  31. 09 2月, 2008 2 次提交
  32. 21 9月, 2007 2 次提交