1. 17 Feb, 2011 4 commits
  2. 14 Feb, 2011 1 commit
  3. 10 Jan, 2011 1 commit
  4. 21 Dec, 2010 1 commit
    • Paul Walmsley's avatar
      OMAP2+: io: split omap2_init_common_hw() · 4805734b
      Paul Walmsley authored
      
      
      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: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Tony Lindgren <tony@atomide.com>
      4805734b
  5. 07 Dec, 2010 1 commit
    • Varadarajan, Charulatha's avatar
      OMAP: GPIO: Implement GPIO as a platform device · 77640aab
      Varadarajan, Charulatha authored
      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: default avatarCharulatha V <charu@ti.com>
      Signed-off-by: default avatarRajendra Nayak <rnayak@ti.com>
      Reviewed-by: default avatarBasak, Partha <p-basak2@ti.com>
      Acked-by: default avatarKevin Hilman <khilman@deeprootsystems.com>
      [tony@atomide.com: updated for bank specific revision and updated boards]
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      77640aab
  6. 02 Dec, 2010 1 commit
  7. 19 Oct, 2010 1 commit
    • Nicolas Pitre's avatar
      arm: remove machine_desc.io_pg_offst and .phys_io · 6451d778
      Nicolas Pitre authored
      
      
      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: default avatarNicolas Pitre <nicolas.pitre@linaro.org>
      Acked-by: Eric Miao <eric.miao at canonical.com>
      6451d778
  8. 08 Oct, 2010 2 commits
    • Manjunath Kondaiah G's avatar
      OMAP3: Keypad: Fix incorrect type initializer · bead4375
      Manjunath Kondaiah G authored
      
      
      The keypad matrix variable declaration is not matching
      with structure variable keymap declared in keypad_matrix.h.
      
      Due to this, following sparse warnings are generated with omap3_defconfig.
      
      arch/arm/mach-omap2/board-devkit8000.c:223:14: warning: incorrect type in initializer (different signedness)
      arch/arm/mach-omap2/board-devkit8000.c:223:14:    expected unsigned int const [usertype] *keymap
      arch/arm/mach-omap2/board-devkit8000.c:223:14:    got int static [toplevel] *<noident>
      
      arch/arm/mach-omap2/board-ldp.c:107:14: warning: incorrect type in initializer (different signedness)
      arch/arm/mach-omap2/board-ldp.c:107:14:    expected unsigned int const [usertype] *keymap
      arch/arm/mach-omap2/board-ldp.c:107:14:    got int static [toplevel] *<noident>
      
      arch/arm/mach-omap2/board-omap3evm.c:472:14: warning: incorrect type in initializer (different signedness)
      arch/arm/mach-omap2/board-omap3evm.c:472:14:    expected unsigned int const [usertype] *keymap
      arch/arm/mach-omap2/board-omap3evm.c:472:14:    got int static [toplevel] *<noident>
      
      arch/arm/mach-omap2/board-3430sdp.c:114:14: warning: incorrect type in initializer (different signedness)
      arch/arm/mach-omap2/board-3430sdp.c:114:14:    expected unsigned int const [usertype] *keymap
      arch/arm/mach-omap2/board-3430sdp.c:114:14:    got int static [toplevel] *<noident>
      
      arch/arm/mach-omap2/board-rx51-peripherals.c:248:14: warning: incorrect type in initializer (different signedness)
      arch/arm/mach-omap2/board-rx51-peripherals.c:248:14:    expected unsigned int const [usertype] *keymap
      arch/arm/mach-omap2/board-rx51-peripherals.c:248:14:    got int static [toplevel] *<noident>
      
      arch/arm/mach-omap2/board-zoom-peripherals.c:88:14: warning: incorrect type in initializer (different signedness)
      arch/arm/mach-omap2/board-zoom-peripherals.c:88:14:    expected unsigned int const [usertype] *keymap
      arch/arm/mach-omap2/board-zoom-peripherals.c:88:14:    got int static [toplevel] *<noident>
      
      arch/arm/mach-omap2/board-cm-t35.c:568:14: warning: incorrect type in initializer (different signedness)
      arch/arm/mach-omap2/board-cm-t35.c:568:14:    expected unsigned int const [usertype] *keymap
      arch/arm/mach-omap2/board-cm-t35.c:568:14:    got int static [toplevel] *<noident>
      
      arch/arm/mach-omap2/board-omap3stalker.c:415:13: warning: incorrect type in initializer (different signedness)
      arch/arm/mach-omap2/board-omap3stalker.c:415:13:    expected unsigned int const [usertype] *keymap
      arch/arm/mach-omap2/board-omap3stalker.c:415:13:    got int static [toplevel] *<noident>
      
      This patch modifies the variable keymap declaration as per declaration in matrix_keymap structure.
      Signed-off-by: default avatarManjunath Kondaiah G <manjugk@ti.com>
      Cc: linux-input@vger.kernel.org
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: Nishanth Menon <nm@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      bead4375
    • Manjunath Kondaiah G's avatar
      OMAP: mach-omap2: Fix static declaration warnings · 38815733
      Manjunath Kondaiah G authored
      
      
      This patch fixes sparse warnings due to non declaration of
      static structures and variables.
      
      Sparse warning logs fixed:
      arch/arm/mach-omap2/control.c:88:6: warning: symbol 'omap3_secure_ram_storage' was not declared. Should it be static?
      n
      arch/arm/mach-omap2/timer-gp.c:50:22: warning: symbol 'gptimer_wakeup' was not declared. Should it be static?
      arch/arm/mach-omap2/timer-gp.c:240:18: warning: symbol 'omap_timer' was not declared. Should it be static?
      arch/arm/mach-omap2/prcm.c:121:24: warning: symbol 'prcm_context' was not declared. Should it be static?
      arch/arm/mach-omap2/mux2420.c:510:29: warning: symbol 'omap2420_pop_ball' was not declared. Should it be static?
      arch/arm/mach-omap2/mux2430.c:589:29: warning: symbol 'omap2430_pop_ball' was not declared. Should it be static?
      arch/arm/mach-omap2/mux34xx.c:934:28: warning: symbol 'omap3_cus_subset' was not declared. Should it be static?
      arch/arm/mach-omap2/mux34xx.c:1080:29: warning: symbol 'omap3_cus_ball' was not declared. Should it be static?
      arch/arm/mach-omap2/mux34xx.c:1272:28: warning: symbol 'omap3_cbb_subset' was not declared. Should it be static?
      arch/arm/mach-omap2/mux34xx.c:1393:29: warning: symbol 'omap3_cbb_ball' was not declared. Should it be static?
      arch/arm/mach-omap2/mux34xx.c:1603:28: warning: symbol 'omap36xx_cbp_subset' was not declared. Should it be static?
      arch/arm/mach-omap2/mux34xx.c:1821:29: warning: symbol 'omap36xx_cbp_ball' was not declared. Should it be static?
      arch/arm/mach-omap2/pm-debug.c:165:15: warning: symbol 'pm_dbg_dir' was not declared. Should it be static?
      arch/arm/mach-omap2/board-omap3evm.c:587:30: warning: symbol 'ads7846_config' was not declared. Should it be static?
      arch/arm/mach-omap2/board-omap3evm.c:606:23: warning: symbol 'omap3evm_spi_board_info' was not declared. Should it be static?
      arch/arm/mach-omap2/board-rx51-sdram.c:46:25: warning: symbol 'rx51_sdrc_params' was not declared. Should it be static?
      arch/arm/mach-omap2/board-rx51-sdram.c:211:25: warning: symbol 'rx51_get_sdram_timings' was not declared. Should it be static?
      arch/arm/mach-omap2/board-omap3touchbook.c:64:15: warning: symbol 'touchbook_revision' was not declared. Should it be static?
      arch/arm/mach-omap2/board-am3517evm.c:350:24: warning: symbol 'am3517_evm_dss_device' was not declared. Should it be static?
      arch/arm/mach-omap2/board-omap3stalker.c:567:23: warning: symbol 'omap3stalker_spi_board_info' was not declared. Should it be static?
      Signed-off-by: default avatarManjunath Kondaiah G <manjugk@ti.com>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: Nishanth Menon <nm@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      38815733
  9. 27 Sep, 2010 1 commit
  10. 05 Aug, 2010 1 commit
  11. 04 Aug, 2010 2 commits
  12. 16 Jul, 2010 1 commit
  13. 27 May, 2010 1 commit
  14. 20 May, 2010 1 commit
  15. 12 May, 2010 2 commits
  16. 11 Mar, 2010 1 commit
    • Felipe Balbi's avatar
      omap2/3/4: ehci: avoid compiler error with touchbook · 6f69a181
      Felipe Balbi authored
      
      
      the early_param() call in board-omap3touchbook.c expands to:
      
      static const char __setup_str_early_touchbook_revision[]
      	__section(.init.rodata) _aligned(1) = tbr;
      [...]
      
      and we have a non-const variable being added to the
      same section:
      
      static struct ehci_hcd_omap_platform_data ehci_pdata
      __section(.init.rodata);
      
      because of that, gcc generates a section type conflict
      which can (and actually should) be avoided by marking
      const every variable marked with __initconst.
      
      This patch fixes that for the ehci_hdc_omap_platform_data.
      Signed-off-by: default avatarFelipe Balbi <felipe.balbi@nokia.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      6f69a181
  17. 19 Feb, 2010 2 commits
  18. 17 Feb, 2010 3 commits
  19. 15 Feb, 2010 3 commits
  20. 12 Feb, 2010 1 commit
  21. 16 Dec, 2009 1 commit
  22. 11 Dec, 2009 3 commits
  23. 22 Nov, 2009 5 commits