summaryrefslogtreecommitdiff
path: root/drivers/rtc/rtc-sirfsoc.c
diff options
context:
space:
mode:
authorVaibhav Jain <vaibhav@linux.vnet.ibm.com>2015-07-14 13:28:28 +0530
committerAlexandre Belloni <alexandre.belloni@free-electrons.com>2015-09-05 13:19:06 +0200
commitf4a2eecb3ff9f51b179b213e7cc3766f920f2dc5 (patch)
tree29894bee75c6f1fb720da5f89a5c530153cba63b /drivers/rtc/rtc-sirfsoc.c
parentc28b42e3aee03fe869a3f73039cf92686ccbc8fb (diff)
rtc: opal: Enable alarms only when opal supports tpo
rtc-opal driver provides support for rtc alarms via timed-power-on(tpo). However some Power platforms like BML use a fake rtc clock and don't support tpo. Such platforms are indicated by the missing 'has-tpo' property in the device tree. Current implementation however enables callback for rtc_class_ops.read/set alarm irrespective of the tpo support from the platform. This results in a failed opal call when kernel tries to read an existing alarms via opal_get_tpo_time during rtc device registration. This patch fixes this issue by setting opal_rtc_ops.read/set_alarm callback pointers only when tpo is supported. Acked-by: Michael Neuling <mikey@neuling.org> Acked-by: Neelesh Gupta <neelegup@linux.vnet.ibm.com> Signed-off-by: Vaibhav Jain <vaibhav@linux.vnet.ibm.com> Acked-by: Stewart Smith <stewart@linux.vnet.ibm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Diffstat (limited to 'drivers/rtc/rtc-sirfsoc.c')
0 files changed, 0 insertions, 0 deletions