[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150722171119.GJ2853@piout.net>
Date: Wed, 22 Jul 2015 19:11:19 +0200
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: Vaibhav Jain <vaibhav@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
Neelesh Gupta <neelegup@...ux.vnet.ibm.com>,
Michael Neuling <mikey@...ling.org>,
Alessandro Zummo <a.zummo@...ertech.it>,
rtc-linux@...glegroups.com
Subject: Re: [PATCH] rtc/rtc-opal: Enable alarms only when opal supports tpo
On 14/07/2015 at 13:28:28 +0530, Vaibhav Jain wrote :
> 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@...ling.org>
> Acked-by: Neelesh Gupta <neelegup@...ux.vnet.ibm.com>
> Signed-off-by: Vaibhav Jain <vaibhav@...ux.vnet.ibm.com>
> ---
> drivers/rtc/rtc-opal.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
Applied, thanks.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists