1. 10 5月, 2011 5 次提交
  2. 09 5月, 2011 9 次提交
  3. 05 5月, 2011 2 次提交
  4. 04 5月, 2011 7 次提交
  5. 03 5月, 2011 7 次提交
  6. 02 5月, 2011 7 次提交
    • K
      omap:usb: add regulator support for EHCI · 6e3d4bec
      Keshava Munegowda 提交于
      in case of ehci phy mode; regulator of phy
      should be enabled before initializing the
      usbhs core driver.
      Signed-off-by: NKeshava Munegowda <keshava_mgowda@ti.com>
      Tested-by: NSteve Calfee <stevecalfee@gmail.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      6e3d4bec
    • A
      mfd: Fix usbhs_enable error handling · d11536e4
      Axel Lin 提交于
      In the case of missing platform_data we do not hold a spin_lock,
      thus we should not call spin_unlock_irqrestore in the error path.
      
      Also simplify the error handling by separating the successful path
      from error path. I think this change improves readability.
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Tested-by: NSteve Calfee <stevecalfee@gmail.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      d11536e4
    • J
      usb: musb: gadget: Fix out-of-sync runtime pm calls · cdefce16
      Jarkko Nikula 提交于
      If cable is not connected to peripheral only board when initializing the
      gadget driver, then runtime pm calls are out-of-sync and the musb cannot
      idle with omap2430.c. This was noted on Nokia N900 where musb prevented the
      CPU to be able to enter deeper retention idle state.
      
      This was working in 2.6.38 before runtime pm conversions but there musb
      smart standby/idle modes were configured statically where they are now
      updated runtime depending on use and cable status.
      
      Reason for out-of-sync is that runtime pm is activated in function
      musb_gadget.c: usb_gadget_probe_driver but suspended only in OTG mode if
      cable is not connected when initializing. In peripheral only mode this leads
      to out-of-sync runtime pm since runtime pm remain active and is activated
      another time in omap2430.c: musb_otg_notifications for VBUS Connect event
      and thus cannot suspend for VBUS Disconnect event since the use count remains
      active.
      
      Fix this by moving cable status check and pm_runtime_put call in
      usb_gadget_probe_driver out of is_otg_enabled block.
      Signed-off-by: NJarkko Nikula <jhnikula@gmail.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      cdefce16
    • J
      usb: musb: omap2430: Fix retention idle on musb peripheral only boards · 383cf4e8
      Jarkko Nikula 提交于
      Recent runtime pm and hwmod conversions for 2.6.39 broke the musb peripheral
      mode OMAP retention idle on boards where the board mode in struct
      musb_hdrc_platform_data is set to MUSB_PERIPHERAL.
      
      These conversions changed the way how the OTG_SYSCONFIG register is
      configured and used in runtime. Before 2.6.39 smart standby/idle modes were
      activated statically in OTG_SYSCONFIG. Those modes allow that the musb is
      able to idle when peripheral device is not connected to host.
      
      In 2.6.39 the OTG_SYSCONFIG is updated runtime depending on VBUS status.
      No standby/idle modes are used when device is connected and force
      standby/idle when disconnected.
      
      Unfortunately VBUS disconnect event that handles the disconnect case lets
      the peripheral musb to idle only when board mode is MUSB_OTG. Fix this by
      checking the peripheral mode also.
      Signed-off-by: NJarkko Nikula <jhnikula@gmail.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      383cf4e8
    • J
      i2c-parport: Fix adapter list handling · 56acc7a3
      Jean Delvare 提交于
      Use a standard list with proper locking to handle the list of
      adapters. Thankfully it only matters on systems with more than one
      parallel port, which are very rare.
      
      Thanks to Lukasz Kapiec for reporting the problem to me.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org
      56acc7a3
    • J
      i2c-i801: Move device ID definitions to driver · a6e5e2be
      Jean Delvare 提交于
      Move the SMBus device ID definitions of recent devices from pci_ids.h
      to the i2c-i801.c driver file. They don't have to be shared, as they
      are clearly identified and only used in this driver. In the future,
      such IDs will go to i2c-i801 directly. This will make adding support
      for new devices much faster and easier, as it will avoid cross-
      subsystem patch sets and merge conflicts.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: Seth Heasley <seth.heasley@intel.com>
      Acked-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      a6e5e2be
    • A
      hwmon: (twl4030-madc-hwmon) Return proper error if hwmon_device_register fails · c30aa39c
      Axel Lin 提交于
      The driver did not return an error if the call to hwmon_device_register failed.
      Fix by returning the error reported from hwmon_device_register.
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Signed-off-by: NGuenter Roeck <guenter.roeck@ericsson.com>
      c30aa39c
  7. 30 4月, 2011 3 次提交