• Vaibhav Jain's avatar
    rtc: opal: Handle disabled TPO in opal_get_tpo_time() · 6dc1cf6f
    Vaibhav Jain authored
    On PowerNV platform when Timed-Power-On(TPO) is disabled, read of
    stored TPO yields value with all date components set to '0' inside
    opal_get_tpo_time(). The function opal_to_tm() then converts it to an
    offset from year 1900 yielding alarm-time == "1900-00-01
    00:00:00". This causes problems with __rtc_read_alarm() that
    expecting an offset from "1970-00-01 00:00:00" and returned alarm-time
    results in a -ve value for time64_t. Which ultimately results in this
    error reported in kernel logs with a seemingly garbage value:
    "rtc rtc0: invalid alarm value: -2-1--1041528741
    We fix this by explicitly handling the case of all alarm date-time
    components being '0' inside opal_get_tpo_time() and returning -ENOENT
    in such a case. This signals generic rtc that no alarm is set and it
    bails out from the alarm initialization flow without reporting the
    above error.
    Signed-off-by: default avatarVaibhav Jain <vaibhav@linux.vnet.ibm.com>
    Reported-by: default avatarSteve Best <sbest@redhat.com>
    Signed-off-by: default avatarAlexandre Belloni <alexandre.belloni@free-electrons.com>