)]}'
{
  "commit": "03e8cb534e7cc3f71a07528a44da7ce68e5b5708",
  "tree": "989d0a96a03d8838de7617f6eb0062ed2a7065e6",
  "parents": [
    "65d13516b2358c38ac56a5f83e989a6837dcf825"
  ],
  "author": {
    "name": "James Hogan",
    "email": "james.hogan@imgtec.com",
    "time": "Wed Jun 29 09:28:43 2011 +0100"
  },
  "committer": {
    "name": "Chris Ball",
    "email": "cjb@laptop.org",
    "time": "Wed Jul 20 17:21:05 2011 -0400"
  },
  "message": "mmc: dw_mmc: fix stop when fallen back to PIO\n\nThere are several situations when dw_mci_submit_data_dma() decides to\nfall back to PIO mode instead of using DMA, due to a short (to avoid\noverhead) or \"complex\" (e.g. with unaligned buffers) transaction, even\nthough host-\u003euse_dma is set. However dw_mci_stop_dma() decides whether\nto stop DMA or set the EVENT_XFER_COMPLETE event based on host-\u003euse_dma.\nWhen falling back to PIO mode this results in data timeout errors\ngetting missed and the driver locking up.\n\nTherefore add host-\u003eusing_dma to indicate whether the current\ntransaction is using dma or not, and adjust dw_mci_stop_dma() to use\nthat instead.\n\nSigned-off-by: James Hogan \u003cjames.hogan@imgtec.com\u003e\nAcked-by: Will Newton \u003cwill.newton@imgtec.com\u003e\nTested-by: Jaehoon Chung \u003cjh80.chung@samsung.com\u003e\nSigned-off-by: Chris Ball \u003ccjb@laptop.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "10b697986283c9fac7cd6196a3025fa439197d46",
      "old_mode": 33188,
      "old_path": "drivers/mmc/host/dw_mmc.c",
      "new_id": "fcff3c042f69466ea4889912db176dd88c7c1f21",
      "new_mode": 33188,
      "new_path": "drivers/mmc/host/dw_mmc.c"
    },
    {
      "type": "modify",
      "old_id": "f3f68ee08a1e9fd29f50c76a35108b07748210a4",
      "old_mode": 33188,
      "old_path": "include/linux/mmc/dw_mmc.h",
      "new_id": "6b46819705d186e0d6604ed1a23a821a5bd7be2d",
      "new_mode": 33188,
      "new_path": "include/linux/mmc/dw_mmc.h"
    }
  ]
}