1. 10 12月, 2011 1 次提交
  2. 04 10月, 2011 1 次提交
  3. 30 9月, 2011 4 次提交
  4. 27 9月, 2011 1 次提交
  5. 24 8月, 2011 2 次提交
    • T
      ARM: OMAP: Introduce SoC specific early_init · 8f5b5a41
      Tony Lindgren 提交于
      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: NTony Lindgren <tony@atomide.com>
      8f5b5a41
    • T
      ARM: OMAP: Move omap2_init_common_devices out of init_early · a4ca9dbe
      Tony Lindgren 提交于
      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: NTony Lindgren <tony@atomide.com>
      a4ca9dbe
  6. 22 8月, 2011 1 次提交
  7. 05 7月, 2011 5 次提交
  8. 04 7月, 2011 1 次提交
  9. 28 6月, 2011 1 次提交
  10. 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
  11. 14 6月, 2011 1 次提交
  12. 01 6月, 2011 2 次提交
  13. 31 5月, 2011 1 次提交
  14. 12 5月, 2011 1 次提交
  15. 11 5月, 2011 2 次提交
  16. 03 5月, 2011 1 次提交
  17. 23 3月, 2011 1 次提交
  18. 16 3月, 2011 1 次提交
  19. 12 3月, 2011 1 次提交
  20. 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
  21. 02 3月, 2011 1 次提交
  22. 01 3月, 2011 2 次提交
  23. 26 2月, 2011 1 次提交
  24. 23 2月, 2011 1 次提交
    • B
      OMAP4: Fix -EINVAL for vana, vcxio, vdac · 530a5a50
      Balaji T K 提交于
      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: NBalaji T K <balajitk@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      530a5a50
  25. 18 2月, 2011 2 次提交
  26. 17 2月, 2011 1 次提交
    • A
      arm: omap4: 4430sdp: drop ehci support · 1dbea0f5
      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>
      1dbea0f5
  27. 15 2月, 2011 1 次提交
  28. 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