)]}'
{
  "commit": "f5e596cd9f0ec6c03660fe4196d395bc3da919a4",
  "tree": "0683ff7c576ad5bf0dcc5752f6f4d01780b562a0",
  "parents": [
    "52976fa74b9da790686ee116424458c238564cb1"
  ],
  "author": {
    "name": "Jisheng Zhang",
    "email": "jszhang@marvell.com",
    "time": "Fri Jul 25 19:57:46 2014 +0800"
  },
  "committer": {
    "name": "Wolfram Sang",
    "email": "wsa@the-dreams.de",
    "time": "Fri Aug 01 19:54:59 2014 +0200"
  },
  "message": "i2c: pca954x: put the mux to disconnected state after resume\n\npca954x may be power lost during suspend, so after resume we also suffer\nthe issue fixed by commit cd823db8b1161ef0d756514d280715a576d65cc3,\n\n \"pca954x power-on default is channel 0 connected. If multiple pca954x\n muxes are connected to the same physical I2C bus, the parent bus will\n see channel 0 devices behind both muxes by default.\"\n\nWhat\u0027s more, when resume bootloader may also operate the mux, so the\nthe channel connected after that may not be the one driver thought.\n\nWe fix this problem by putting the mux to disconnected state and\nclearing last_chan in the resume hook.\n\nSigned-off-by: Jisheng Zhang \u003cjszhang@marvell.com\u003e\nReviewed-by: Jean Delvare \u003cjdelvare@suse.de\u003e\nAcked-by: Laurent Pinchart \u003claurent.pinchart@ideasonboard.com\u003e\nSigned-off-by: Wolfram Sang \u003cwsa@the-dreams.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9bd4212782ab834bff64a92bee447ae841441966",
      "old_mode": 33188,
      "old_path": "drivers/i2c/muxes/i2c-mux-pca954x.c",
      "new_id": "ec11b404b433737657957ef9dd0e559a955b45aa",
      "new_mode": 33188,
      "new_path": "drivers/i2c/muxes/i2c-mux-pca954x.c"
    }
  ]
}