)]}'
{
  "commit": "48c98b1bb85a09adf4aa27316682d573e1f37ebf",
  "tree": "ca898d31965df3f7c94d7100a7ce81e58f93fe66",
  "parents": [
    "fd0fc21350838d3073647be173242db0c58744c8"
  ],
  "author": {
    "name": "Mark Brown",
    "email": "broonie@opensource.wolfsonmicro.com",
    "time": "Thu Dec 29 09:58:16 2011 -0800"
  },
  "committer": {
    "name": "Dmitry Torokhov",
    "email": "dmitry.torokhov@gmail.com",
    "time": "Fri Dec 30 00:39:19 2011 -0800"
  },
  "message": "Input: samsung-keypad - implement runtime power management support\n\nWhen runtime power management is enabled put the Samsung keypad driver\ninto suspend mode with wakeups disabled whenever the device is open but\na key is not actually been pressed. As well as saving a trivial amount of\npower this will support the use of SoC wide idle modes which put the entire\ndevice into a retention mode and use explicit wakeup sources to exit.\n\nSince not all of the interrupt controllers used with the driver support\nset_irq_wake() (though they all do the right thing) and there\u0027s a nasty\nWARN() when we disable wake after failing to enable it keep track of the\ncurrent wake status from runtime PM and only disable wake if we managed\nto enable it; I\u0027m not entirely sure why this doesn\u0027t affect the existing\nuses of the API in the driver.\n\nSystem suspend is unaffected as the driver core will runtime resume any\nsuspended devices prior to system suspend.\n\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Dmitry Torokhov \u003cdtor@mail.ru\u003e\n\nConflicts:\n\n\tdrivers/input/keyboard/samsung-keypad.c\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a6e010e016f8b990b512f731c7a18e953a32b9bf",
      "old_mode": 33188,
      "old_path": "drivers/input/keyboard/samsung-keypad.c",
      "new_id": "b746fce2d120d77b33921743341cf60f8a727d9d",
      "new_mode": 33188,
      "new_path": "drivers/input/keyboard/samsung-keypad.c"
    }
  ]
}