Skip to content
Snippets Groups Projects
  1. Jan 26, 2012
  2. Jan 05, 2012
  3. Oct 03, 2011
  4. Sep 30, 2011
  5. Sep 27, 2011
  6. Aug 24, 2011
    • Tony Lindgren's avatar
      ARM: OMAP: Introduce SoC specific early_init · 8f5b5a41
      Tony Lindgren authored
      
      Introduce them for each omap variant and just make them all call
      omap2_init_common_infrastructure for now. Do this for each board-*.c
      file except for board-generic and board-omap3beagle as they use
      the same machine ID for multiple SoCs.
      
      No functional changes.
      
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      8f5b5a41
    • Tony Lindgren's avatar
      ARM: OMAP: Move omap2_init_common_devices out of init_early · a4ca9dbe
      Tony Lindgren authored
      
      There's no need to call omap2_init_common_devices from init_early.
      
      It no longer does anything else except reprogram the memory timings
      for some boards, so it's better to do it later so we have a chance
      to get console messages if something goes wrong.
      
      Move it to happen after omap_serial_init gets called. And while
      patching it anyways, rename it to omap_sdrc_init as suggested by
      Benoit Cousson <b-cousson@ti.com>.
      
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      a4ca9dbe
  7. Aug 21, 2011
  8. Jul 05, 2011
  9. Jul 04, 2011
  10. Jun 27, 2011
  11. Jun 20, 2011
    • Tony Lindgren's avatar
      omap: Set separate timer init functions to avoid cpu_is_omap tests · e74984e4
      Tony Lindgren authored
      
      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: default avatarTony Lindgren <tony@atomide.com>
      Reviewed-by: default avatarKevin Hilman <khilman@ti.com>
      e74984e4
  12. Jun 14, 2011
  13. Jun 01, 2011
  14. May 31, 2011
  15. May 12, 2011
  16. May 11, 2011
  17. May 03, 2011
  18. Mar 23, 2011
  19. Mar 16, 2011
  20. Mar 11, 2011
  21. Mar 07, 2011
    • Anand Gadiyar's avatar
      arm: omap4: 4430sdp: drop ehci support · 09173b58
      Anand Gadiyar authored
      
      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: default avatarAnand Gadiyar <gadiyar@ti.com>
      Cc: Keshava Munegowda <keshava_mgowda@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Signed-off-by: default avatarFelipe Balbi <balbi@ti.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      09173b58
  22. Mar 01, 2011
  23. Feb 25, 2011
  24. Feb 22, 2011
    • Balaji T K's avatar
      OMAP4: Fix -EINVAL for vana, vcxio, vdac · 530a5a50
      Balaji T K authored
      
      Fixed regulators in twl6030 do not have set_voltage hook.
      Regulator core returns -22 if set_voltage is NULL and apply_uV is set
      while applying the constraint to set voltage resulting in failure during probe
      of these regulators.
      Do not set apply_uV for fixed regulators which don't have set_voltage.
      
      machine_constraints_voltage: VANA: failed to apply 2100000uV constraint
      twl_reg twl_reg.43: can't register VANA, -22
      twl_reg: probe of twl_reg.43 failed with error -22
      machine_constraints_voltage: VCXIO: failed to apply 1800000uV constraint
      twl_reg twl_reg.44: can't register VCXIO, -22
      twl_reg: probe of twl_reg.44 failed with error -22
      machine_constraints_voltage: VDAC: failed to apply 1800000uV constraint
      twl_reg twl_reg.45: can't register VDAC, -22
      twl_reg: probe of twl_reg.45 failed with error -22
      
      Signed-off-by: default avatarBalaji T K <balajitk@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      530a5a50
  25. Feb 18, 2011
    • Hema HK's avatar
      usb: otg: OMAP4430: Introducing suspend function for power management · ee896e34
      Hema HK authored
      
      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: default avatarHema HK <hemahk@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Paul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarFelipe Balbi <balbi@ti.com>
      ee896e34
  26. Feb 17, 2011
    • Syed Rafiuddin's avatar
      OMAP4: keypad: Add the board support · 59556765
      Syed Rafiuddin authored
      
      -Add the platform changes for the keypad driver
      -Register keyboard device with hwmod framework.
      
      Signed-off-by: default avatarSyed Rafiuddin <rafiuddin.syed@ti.com>
      Signed-off-by: default avatarAbraham Arce <x0066660@ti.com>
      Signed-off-by: default avatarShubhrajyoti D <shubhrajyoti@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      59556765
    • Anand Gadiyar's avatar
      arm: omap4: 4430sdp: drop ehci support · 1dbea0f5
      Anand Gadiyar authored
      
      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: default avatarAnand Gadiyar <gadiyar@ti.com>
      Cc: Keshava Munegowda <keshava_mgowda@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Signed-off-by: default avatarFelipe Balbi <balbi@ti.com>
      1dbea0f5
Loading