All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
To: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] rtc/rtc-opal: Disable rtc-alarms when opal doesn't support tpo
Date: Wed, 03 Jun 2015 11:04:11 +0530	[thread overview]
Message-ID: <556E91D3.8010707@linux.vnet.ibm.com> (raw)
In-Reply-To: <1433307087-11503-1-git-send-email-vaibhav@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]



On 06/03/2015 10:21 AM, Vaibhav Jain wrote:
> rtc-opal driver provides support for rtc alarms via
> times-power-on(tpo). However some 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.
>
> Signed-off-by: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>

Acked-by: Neelesh Gupta <neelegup@linux.vnet.ibm.com>

Thanks,
Neelesh.

> ---
>   drivers/rtc/rtc-opal.c | 9 +++++----
>   1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/rtc/rtc-opal.c b/drivers/rtc/rtc-opal.c
> index 7061dca..1125641 100644
> --- a/drivers/rtc/rtc-opal.c
> +++ b/drivers/rtc/rtc-opal.c
> @@ -190,11 +190,9 @@ exit:
>   	return rc;
>   }
>
> -static const struct rtc_class_ops opal_rtc_ops = {
> +static struct rtc_class_ops opal_rtc_ops = {
>   	.read_time	= opal_get_rtc_time,
>   	.set_time	= opal_set_rtc_time,
> -	.read_alarm	= opal_get_tpo_time,
> -	.set_alarm	= opal_set_tpo_time,
>   };
>
>   static int opal_rtc_probe(struct platform_device *pdev)
> @@ -202,8 +200,11 @@ static int opal_rtc_probe(struct platform_device *pdev)
>   	struct rtc_device *rtc;
>
>   	if (pdev->dev.of_node && of_get_property(pdev->dev.of_node, "has-tpo",
> -						 NULL))
> +						 NULL)) {
>   		device_set_wakeup_capable(&pdev->dev, true);
> +		opal_rtc_ops.read_alarm	= opal_get_tpo_time;
> +		opal_rtc_ops.set_alarm = opal_set_tpo_time;
> +	}
>
>   	rtc = devm_rtc_device_register(&pdev->dev, DRVNAME, &opal_rtc_ops,
>   				       THIS_MODULE);


[-- Attachment #2: Type: text/html, Size: 2682 bytes --]

  reply	other threads:[~2015-06-03  5:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  4:51 [PATCH] rtc/rtc-opal: Disable rtc-alarms when opal doesn't support tpo Vaibhav Jain
2015-06-03  5:34 ` Neelesh Gupta [this message]
2015-07-08  3:25 ` Michael Neuling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=556E91D3.8010707@linux.vnet.ibm.com \
    --to=neelegup@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=vaibhav@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.