1. 23 2月, 2011 2 次提交
    • K
      i2c-omap: fix static suspend vs. runtime suspend · adf6e079
      Kevin Hilman 提交于
      When runtime PM is enabled, each OMAP i2c device is suspended after
      each i2c xfer.  However, there are two cases when the static suspend
      methods must be used to ensure the devices are suspended:
      
      1) runtime PM is disabled, either at compile time or dynamically
          via /sys/devices/.../power/control.
      2) an i2c client driver uses i2c during it's suspend callback, thus
         leaving the i2c driver active (NOTE: runtime suspend transitions are
         disabled during system suspend, so i2c activity during system
         suspend will runtime resume the device, but not runtime (re)suspend it.)
      
      Since the actual work to suspend the device is handled by the
      subsytem, call the bus methods to take care of it.
      
      NOTE: This takes care of a known suspend problem on OMAP3 where the
      TWL RTC driver does i2c xfers during its suspend path leaving the i2c
      driver in an active state (since runtime suspend transistions are
      disabled.)
      Signed-off-by: NKevin Hilman <khilman@ti.com>
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      adf6e079
    • W
      i2c-stu300: make sure adapter-name is terminated · f10820e4
      Wolfram Sang 提交于
      Use strlcpy instead of strncpy.
      Signed-off-by: NWolfram Sang <w.sang@pengutronix.de>
      Cc: Linus Walleij <linus.walleij@stericsson.com>
      Cc: Ben Dooks <ben-linux@fluff.org>
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      f10820e4
  2. 15 1月, 2011 3 次提交
  3. 14 1月, 2011 1 次提交
    • A
      i2c: Convert SCx200 driver from using raw PCI to platform device · de8255cc
      Andres Salomon 提交于
      The SCx200 ACB driver supports ISA hardware as well as PCI.  The PCI
      hardware is CS5535/CS5536 based, and the device that it grabs is handled by
      the cs5535-mfd driver. This converts the SCx200 driver to use a
      platform_driver rather than the previous PCI hackery.
      
      The driver used to manually track the iface list (via linked list); now it
      only does this for ISA devices.  PCI ifaces are handled through standard
      driver model lists.
      
      It's unclear what happens in case of errors in the old ISA code; rather than
      pretending the code actually cares, I've dropped the (implicit) ignorance
      of return values and marked it with a comment.
      Signed-off-by: NAndres Salomon <dilinger@queued.net>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      de8255cc
  4. 13 1月, 2011 2 次提交
  5. 11 1月, 2011 6 次提交
  6. 04 1月, 2011 8 次提交
  7. 21 12月, 2010 1 次提交
  8. 15 12月, 2010 1 次提交
  9. 22 11月, 2010 2 次提交
  10. 16 11月, 2010 2 次提交
  11. 10 11月, 2010 1 次提交
  12. 02 11月, 2010 1 次提交
  13. 01 11月, 2010 3 次提交
  14. 30 10月, 2010 1 次提交
    • R
      i2c-intel-mid: Driver depends on PCI · 9cc11dee
      Randy Dunlap 提交于
      i2c-intel-mid driver uses PCI data structs and interfaces,
      so it should depend on PCI.  Fixes these build errors:
      
      drivers/i2c/busses/i2c-intel-mid.c:977: error: implicit declaration of function 'pci_request_region'
      drivers/i2c/busses/i2c-intel-mid.c:1077: error: implicit declaration of function 'pci_release_region'
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Cc: Ba Zheng <zheng.ba@intel.com>
      Cc: Jean Delvare <khali@linux-fr.org>
      Cc: Ben Dooks <ben-linux@fluff.org>
      Cc: linux-i2c@vger.kernel.org
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      9cc11dee
  15. 28 10月, 2010 1 次提交
    • A
      i2c-intel-mid: support for Moorestown and Medfield platform · aa62f85d
      Alan Cox 提交于
      (Updated to address Ben's comments. With regard to the message segment
       restriction it's not something we hit on the actual platform so while
       I will investigate that further I don't think its a blocker to submission.
       At worst its a spot over-restrictive)
      
      From: Wen Wang <wen.w.wang@intel.com>
      
      Initial release of the driver. Updated and verified on hardware.
      
      Cleaned up as follows
      
      Alan Cox:
         Squash down the switches into tables, and use the PCI ident field. We
         could perhaps take this further and put the platform and port number into
         this.
         uint32t -> u32
         bracketing of case statements
         spacing and '!' usage
         Check the speed (which is now 0/1/2) is valid and ignore otherwise.
         Fix remaining problems/suggestions from Jean's review
         Fix items from Ben's review
      
      Arjan van de Ven:
         Initial power management hooks
      
      Yong Wang <youg.y.wang@intel.com>:
         Shared IRQ support
      
      Wen Wang <wen.w.wang@intel.com>:
         D3 support
         Fixes for OCT test runs
         Interrupt optimisations
      
      Hong Liu <hong.liu@intel.com>
         The runtime PM code is working on the wrong device (i2c_adapter->dev).
         The correct one should be pci_dev->dev. This breaks attached i2c
         slave devices with runtime PM enabled. Slave device needs to runtime
         resume parent device before runtime resuming itself, but we always get
         error since we don't have pm_runtime callback for i2c_adapter->dev.
      
      Bin Yang <bin.yang@intel.com>:
         Update speed table
      
      Saadi Maalem <saadi.maalem@intel.com>:
         Clear all interrupts in the hardware init
      
      Celine Chotard <celinex.chotard@intel.com>:
         Correct ordering of clear/disable of IRQs
      Signed-off-by: NWen Wang <wen.w.wang@intel.com>
      Signed-off-by: NYong Wang <yong.y.wang@intel.com>
      Signed-off-by: NHong Liu <hong.liu@intel.com>
      Signed-off-by: NBin Yang <bin.yang@intel.com>
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      aa62f85d
  16. 27 10月, 2010 1 次提交
  17. 25 10月, 2010 4 次提交