)]}'
{
  "commit": "1b73e6ae45d0353a062d7bea707757a235473cf9",
  "tree": "22f4d14de41371e48bf513e11e3734adb4dd788c",
  "parents": [
    "a16147965ca7a84dc08c4457961782e06ac7cd0d"
  ],
  "author": {
    "name": "Jamie Lenehan",
    "email": "lenehan@twibble.org",
    "time": "Fri Dec 08 15:26:15 2006 +0900"
  },
  "committer": {
    "name": "Paul Mundt",
    "email": "lethal@linux-sh.org",
    "time": "Tue Dec 12 08:42:08 2006 +0900"
  },
  "message": "rtc: rtc-sh: alarm support.\n\nThis adds alarm support for the RTC_ALM_SET, RTC_ALM_READ,\nRTC_WKALM_SET and RTC_WKALM_RD operations to rtc-sh.\n\nThe only unusual part is the handling of the alarm interrupt. If you\nclear the alarm flag (AF) while the time in the RTC still matches the\ntime in the alarm registers than AF is immediately re-set, and if the\nalarm interrupt (AIE) is still enabled then it re-triggers. I was\noriginally getting around 20k+ interrupts generated during the second\nwhen the RTC and alarm registers matches.\n\nThe solution I\u0027ve used is to clear AIE when the alarm goes off and\nthen use the carry interrupt to re-enabled it. The carry interrupt\nwill check AF and re-enabled AIE if it\u0027s clear. If AF is not clear\nit\u0027ll clear it and then the check will be repeated next carry\ninterrupt. This a bit in rtc structure that indicates that it\u0027s\nwaiting to have AIE re-enabled so it doesn\u0027t turn it on when it\nwasn\u0027t enabled anyway.\n\nSigned-off-by: Jamie Lenehan \u003clenehan@twibble.org\u003e\nSigned-off-by: Paul Mundt \u003clethal@linux-sh.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8f22eb1aff5c7032a495f69fc48d1e11af0e151d",
      "old_mode": 33188,
      "old_path": "drivers/rtc/rtc-sh.c",
      "new_id": "72ba1a70f35f6def6e9468c5fd9a5f70cb5216a0",
      "new_mode": 33188,
      "new_path": "drivers/rtc/rtc-sh.c"
    }
  ]
}