)]}'
{
  "commit": "56faf0f98fd53e4a27cec331a3ff6d4aa55b1213",
  "tree": "f607637a24045396aee23e3ce0690b5f90946285",
  "parents": [
    "093344e1362cbf9525a5da09a565f357d8102f3b"
  ],
  "author": {
    "name": "Jason Wessel",
    "email": "jason.wessel@windriver.com",
    "time": "Thu Aug 20 15:39:51 2009 -0500"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Wed Sep 23 06:46:38 2009 -0700"
  },
  "message": "USB: dbgp: EHCI debug controller initialization delays\n\nWhen using the EHCI host controller as a polled device, a bit more\ntolerance is required in terms of delays.  On some 3+ghz systems the\ncpu loops were faster than the EHCI device mmio and resulted in the\ncontroller failing to initialize.\n\nOn at least one first generation EHCI controller when it was not\noperating in interrupt mode, it would fail to report a port change\nstatus, but executing the port reset allowed the debug controller to\nwork correctly anyway.  This errata causes a one time 300ms delay in\nthe boot time, where as the typical delay is 1-5ms for an EHCI\ncontroller that does not have this errata.\n\nThe debug printk\u0027s were fixed to have the correct state messages, and\nthere was a conversion from using early_printk to printk to avoid\ncalling the dbgp driver while debugging the initialization.\n\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nCc: Yinghai Lu \u003cyinghai@kernel.org\u003e\nCc: \"Eric W. Biederman\" \u003cebiederm@xmission.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7deae97fe50f2b93edf1167956f0ed52b56ca979",
      "old_mode": 33188,
      "old_path": "drivers/usb/early/ehci-dbgp.c",
      "new_id": "6198ebded3a4c70e3f95998ceedcfee77e5ad12a",
      "new_mode": 33188,
      "new_path": "drivers/usb/early/ehci-dbgp.c"
    }
  ]
}