)]}'
{
  "commit": "adf6e07922255937c8bfeea777d19502b4c9a2be",
  "tree": "5aeee4e126ee83567e12e437084766602eae942d",
  "parents": [
    "f10820e49585f281706ac07570a9e1652bdb5dd9"
  ],
  "author": {
    "name": "Kevin Hilman",
    "email": "khilman@ti.com",
    "time": "Thu Jan 27 16:18:41 2011 -0800"
  },
  "committer": {
    "name": "Ben Dooks",
    "email": "ben-linux@fluff.org",
    "time": "Tue Feb 22 23:53:44 2011 +0000"
  },
  "message": "i2c-omap: fix static suspend vs. runtime suspend\n\nWhen runtime PM is enabled, each OMAP i2c device is suspended after\neach i2c xfer.  However, there are two cases when the static suspend\nmethods must be used to ensure the devices are suspended:\n\n1) runtime PM is disabled, either at compile time or dynamically\n    via /sys/devices/.../power/control.\n2) an i2c client driver uses i2c during it\u0027s suspend callback, thus\n   leaving the i2c driver active (NOTE: runtime suspend transitions are\n   disabled during system suspend, so i2c activity during system\n   suspend will runtime resume the device, but not runtime (re)suspend it.)\n\nSince the actual work to suspend the device is handled by the\nsubsytem, call the bus methods to take care of it.\n\nNOTE: This takes care of a known suspend problem on OMAP3 where the\nTWL RTC driver does i2c xfers during its suspend path leaving the i2c\ndriver in an active state (since runtime suspend transistions are\ndisabled.)\n\nSigned-off-by: Kevin Hilman \u003ckhilman@ti.com\u003e\nSigned-off-by: Ben Dooks \u003cben-linux@fluff.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b605ff3a1fa05703d8fbbaf12df90aaa1c125813",
      "old_mode": 33188,
      "old_path": "drivers/i2c/busses/i2c-omap.c",
      "new_id": "0541df90b9fb093201863062fc3c6606539cf467",
      "new_mode": 33188,
      "new_path": "drivers/i2c/busses/i2c-omap.c"
    }
  ]
}