)]}'
{
  "commit": "ea505bc99f77f3f9db02bb965bd59ac5db063f60",
  "tree": "de89dabcfede2797cdecc224aa5224854db5232a",
  "parents": [
    "88a3a255a510ed193bf0cc35424761c3c9247586"
  ],
  "author": {
    "name": "Viresh Kumar",
    "email": "viresh.kumar@st.com",
    "time": "Thu Apr 19 11:48:15 2012 +0530"
  },
  "committer": {
    "name": "Grant Likely",
    "email": "grant.likely@secretlab.ca",
    "time": "Fri Apr 27 12:07:40 2012 -0600"
  },
  "message": "spi/pl022: Allow request for higher frequency than maximum possible\n\nCurrently, if we request for frequency greater than maximum possible, spi driver\nreturns error.\n\nFor example, if the spi block src frequency is 333/4 MHz, i.e. 83.33.. MHz,\nmaximum frequency programmable would be src/2. Which would come around 41.6...\n\nIt is difficult to pass frequency in these figures. We normally try to program\nin round figures, like 42 MHz and it should get programmed to \u003c\u003d\nrequested_frequency, i.e. 41.6...\n\nFor this to happen, we must not return error even if requested freq is higher\nthan max possible. But should program it to max possible.\n\nReported-by: Vinit Kamalaksha Shenoy \u003cvinit.shenoy@st.com\u003e\nSigned-off-by: Viresh Kumar \u003cviresh.kumar@st.com\u003e\nAcked-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\nSigned-off-by: Grant Likely \u003cgrant.likely@secretlab.ca\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8aa44e7adaef3011a8d51eda80ef48d210423c1d",
      "old_mode": 33188,
      "old_path": "drivers/spi/spi-pl022.c",
      "new_id": "400ae2121a2a48cd1c78469f0c727972b180a777",
      "new_mode": 33188,
      "new_path": "drivers/spi/spi-pl022.c"
    }
  ]
}