)]}'
{
  "commit": "67e7f18e04cdcf761e28d8ce62503e4815cef72a",
  "tree": "8c139ccb501c5da7c19c9a2e164ce50b82e0c405",
  "parents": [
    "30a586f024deaa74ad563641584db613cbd6a072"
  ],
  "author": {
    "name": "Krishna Konda",
    "email": "kkonda@codeaurora.org",
    "time": "Wed Aug 29 16:29:21 2012 -0700"
  },
  "committer": {
    "name": "Iliyan Malchev",
    "email": "malchev@google.com",
    "time": "Wed Nov 14 16:14:00 2012 -0800"
  },
  "message": "mmc: msm_sdcc: Reset SPS BAM on error recovery\n\nIn the current soft reset sequence performed as part of\nCMD/DATA error recovery we do the following:\n1) Write 1 to DML_SW_RESET\n2) Reset CPSM/DPSM by clearing MCI_CMD and MCI_DATA_CTL\nor by writing to MCI_SW_RST_CONFIG.\n3) Re-init DML\n4) Reconfigure both consumer and producer BAM pipes.\n\nThe BAM pipe reset does not reset the sideband signals, since\nonly SDCC side is reset SDCC - BAM communication will go out\nof sync and cause DML to be stuck without transferring data.\nHence reset BAM core every time SDCC is reset (which is on\nerror recovery).\n\nFix error handling for sps pipe or device reset.\n\nChange-Id: I745e015c862fffa36a814cd007d2e82383668b3a\nSigned-off-by: Venkat Gopalakrishnan \u003cvenkatg@codeaurora.org\u003e\nSigned-off-by: Krishna Konda \u003ckkonda@codeaurora.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dd5948e4754daf2ca24d824966ab7fcb21b392b8",
      "old_mode": 33188,
      "old_path": "drivers/mmc/host/msm_sdcc.c",
      "new_id": "a4248fdd244d77eebeffc77ef17302cbd9b0669e",
      "new_mode": 33188,
      "new_path": "drivers/mmc/host/msm_sdcc.c"
    },
    {
      "type": "modify",
      "old_id": "57794913aa461ff29d0a59ea317bd68b51c91fa0",
      "old_mode": 33188,
      "old_path": "drivers/mmc/host/msm_sdcc.h",
      "new_id": "484c791524e28f48558dbf56af1b6a7defdc2628",
      "new_mode": 33188,
      "new_path": "drivers/mmc/host/msm_sdcc.h"
    }
  ]
}