1. 08 3月, 2011 1 次提交
    • A
      arm: omap4: 4430sdp: drop ehci support · 09173b58
      Anand Gadiyar 提交于
      Most revisions of the OMAP4 Blaze/SDP platform do not have
      the EHCI signals routed by default. The pads are routed
      for the alternate HSI functionality instead, and explicit
      board modifications are needed to route the signals to
      the USB PHY on the board.
      
      Also, turning on the PHY connected to the EHCI port causes
      a board reboot during bootup due to an unintended short
      on the rails - this affects many initial revisions of the
      board, and needs a minor board mod to fix (or as a
      workaround, one should not attempt to power on the
      USB PHY).
      
      Given that these boards need explicit board mods to even
      get EHCI working (separate from the accidental short above),
      we should not attempt to enable EHCI by default.
      
      So drop the EHCI support from the board files for the
      Blaze/SDP platforms.
      Signed-off-by: NAnand Gadiyar <gadiyar@ti.com>
      Cc: Keshava Munegowda <keshava_mgowda@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      09173b58
  2. 01 3月, 2011 2 次提交
  3. 18 2月, 2011 1 次提交
    • H
      usb: otg: OMAP4430: Introducing suspend function for power management · ee896e34
      Hema HK 提交于
      Introduced the suspend/resume function for the OMAP4430 internal PHY.
      This will be used by the twl6030-usb transceiver driver.
      Moved the clock enable/disable function calls and power on/off of the PHY
      code from power on/off functions to suspend/resume function.
      
      Pass the suspend function through board data for OMAP4430sdp and OMAP4panda.
      This will be used by the twl6030-usb transceiver driver.
      Signed-off-by: NHema HK <hemahk@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Paul Walmsley <paul@pwsan.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      ee896e34
  4. 14 1月, 2011 1 次提交
    • T
      omap4: Fix ULPI PHY init for ES1.0 SDP · 7d4ca85a
      Tony Lindgren 提交于
      Commit 6aa85a5a (omap4: 4430sdp:
      enable the ehci port on 4430SDP) added code to enable EHCI
      support on 4430sdp board.
      
      Looks like the ULPI pin does not seem to be muxed properly on ES1.0
      SDP and this causes the system to reboot when the ULPI PHY is
      enabled.
      
      Fix this by muxing the pin, this is the same setting for
      both ES1.0 and ES2.0. Also add checking for gpio_request.
      
      Cc: Keshava Munegowda <keshava_mgowda@ti.com
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      7d4ca85a
  5. 22 12月, 2010 1 次提交
    • P
      OMAP2+: io: split omap2_init_common_hw() · 4805734b
      Paul Walmsley 提交于
      Split omap2_init_common_hw() into two functions.  The first,
      omap2_init_common_infrastructure(), initializes the hwmod code and
      data, the OMAP PM code, and the clock code and data.  The second,
      omap2_init_common_devices(), handles any other early device
      initialization that, for whatever reason, has not been or cannot be
      moved to initcalls or early platform devices.
      
      This patch is required for the hwmod postsetup patch, which allows
      board files to change the state that hwmods should be placed into at
      the conclusion of the hwmod _setup() function.  For example, for a
      board whose creators wish to ensure watchdog coverage across the
      entire kernel boot process, code to change the watchdog's postsetup
      state will be added in the board-*.c file between the
      omap2_init_common_infrastructure() and omap2_init_common_devices() function
      calls.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Tony Lindgren <tony@atomide.com>
      4805734b
  6. 21 12月, 2010 2 次提交
  7. 10 12月, 2010 3 次提交
  8. 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
  9. 01 12月, 2010 1 次提交
  10. 17 11月, 2010 2 次提交
  11. 29 10月, 2010 1 次提交
    • K
      mfd: Adding twl6030 mmc card detect support for MMC1 · 72f2e2c7
      kishore kadiyala 提交于
      Adding card detect callback function and card detect configuration
      function for MMC1 Controller on OMAP4.
      
      Card detect configuration function does initial configuration of the
      MMC Control & PullUp-PullDown registers of Phoenix.
      
      For MMC1 Controller, card detect interrupt source is
      twl6030 which is non-gpio. The card detect call back function provides
      card present/absent status by reading MMC Control register present
      on twl6030.
      
      Since OMAP4 doesn't use any GPIO line as used in OMAP3 for card detect,
      the suspend/resume initialization which was done in omap_hsmmc_gpio_init
      previously is moved to the probe thus making it generic for both OMAP3 &
      OMAP4.
      
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
      Cc: Adrian Hunter <adrian.hunter@nokia.com>
      Signed-off-by: NKishore Kadiyala <kishore.kadiyala@ti.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      72f2e2c7
  12. 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
  13. 09 10月, 2010 2 次提交
    • P
      OMAP: control: move plat-omap/control.h to mach-omap2/control.h · 4814ced5
      Paul Walmsley 提交于
      Only OMAP2+ platforms have the System Control Module (SCM) IP block.
      In the past, we've kept the SCM header file in plat-omap.  This has
      led to abuse - device drivers including it; includes being added that
      create implicit dependencies on OMAP2+ builds; etc.
      
      In response, move the SCM headers into mach-omap2/.
      
      As part of this, remove the direct SCM access from the OMAP UDC
      driver.  It was clearly broken.  The UDC code needs an indepth review for
      use on OMAP2+ chips.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Cory Maccarrone <darkstar6262@gmail.com>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      4814ced5
    • M
      OMAP2plus: Fix static function warnings · 04aeae77
      Manjunath Kondaiah G 提交于
      This patch fixes sparse warnings due non declarations of static functions.
      
      arch/arm/mach-omap2/timer-gp.c:115:12: warning: symbol 'omap2_gp_clockevent_set_gptimer' was not declared. Should it be static?
      arch/arm/mach-omap2/powerdomain.c:993:5: warning: symbol 'pwrdm_set_lowpwrstchange' was not declared. Should it be static?
      arch/arm/mach-omap2/board-flash.c:141:8: warning: symbol 'board_nand_init' was not declared. Should it be static?
      arch/arm/mach-omap2/board-n8x0.c:416:6: warning: symbol 'n8x0_mmc_slot1_cover_handler' was not declared. Should it be static?
      arch/arm/mach-omap2/board-n8x0.c:544:13: warning: symbol 'n8x0_mmc_init' was not declared. Should it be static?
      arch/arm/mach-omap2/board-rx51-peripherals.c:902:13: warning: symbol 'rx51_peripherals_init' was not declared. Should it be static?
      arch/arm/mach-omap2/board-rx51-video.c:107:13: warning: symbol 'rx51_video_mem_init' was not declared. Should it be static?
      arch/arm/mach-omap2/board-zoom-debugboard.c:155:12: warning: symbol 'zoom_debugboard_init' was not declared. Should it be static?
      arch/arm/mach-omap2/board-zoom-peripherals.c:280:13: warning: symbol 'zoom_peripherals_init' was not declared. Should it be static?
      arch/arm/mach-omap2/board-igep0020.c:110:13: warning: symbol 'igep2_flash_init' was not declared. Should it be static?
      arch/arm/mach-omap2/board-am3517evm.c:109:6: warning: symbol 'am3517_evm_ethernet_init' was not declared. Should it be static?
      drivers/mtd/onenand/omap2.c:577:5: warning: symbol 'omap2_onenand_rephase' was not declared. Should it be static?
      Signed-off-by: NManjunath Kondaiah G <manjugk@ti.com>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: Nishanth Menon <nm@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      04aeae77
  14. 02 10月, 2010 2 次提交
  15. 28 9月, 2010 1 次提交
  16. 25 9月, 2010 1 次提交
  17. 24 9月, 2010 1 次提交
  18. 02 8月, 2010 3 次提交
  19. 16 7月, 2010 1 次提交
  20. 21 5月, 2010 5 次提交
  21. 12 3月, 2010 1 次提交
  22. 24 2月, 2010 2 次提交
    • S
      omap4: multi-omap: Allow build to work · ae46ec77
      Santosh Shilimkar 提交于
      The musb support is enabled in omap3 platforms. For omap4 only board
      support is available and the driver still isn't supported.
      Because of this build with omap3_defconfig used for multi-omap
      doesn't work on omap4430 sdp.
      
      This patch avoids usb_musb_init() by adding a cpu check
      in the board file.
      
      Thanks to Anand Gadiyar and Mankad Maulik for the suggestion
      of patching board file instead of musb driver.
      Signed-off-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      ae46ec77
    • M
      omap: musb: Add USB support to 4430 SDP board file · bce06683
      Maulik Mankad 提交于
      This patch adds support for Mentor USB to 4430 SDP board
      file.
      
      It also defines the base address for HS USB OTG controller
      in OMAP4.
      
      Also updates platform specfic structure with base address
      and IRQ details.
      Signed-off-by: NMaulik Mankad <x0082077@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Felipe Balbi <felipe.balbi@nokia.com>
      Cc: David Brownell <david-b@pacbell.net>
      Cc: Greg Kroah-Hartman <gregkh@suse.de>
      Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>
      Cc: Olof Johansson <olof@lixom.net>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      bce06683
  23. 16 2月, 2010 3 次提交
  24. 23 10月, 2009 1 次提交