From: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
To: devicetree@vger.kernel.org, tglx@linutronix.de,
linuxppc-dev@lists.ozlabs.org, rtc-linux@googlegroups.com,
a.zummo@towertech.it
Cc: benh@au1.ibm.com
Subject: Re: [PATCH v3] rtc/tpo: Driver to support rtc and wakeup on PowerNV platform
Date: Wed, 22 Oct 2014 14:18:11 +0530 [thread overview]
Message-ID: <54476F4B.8050108@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141014083447.7505.89771.stgit@localhost.localdomain>
On 10/14/2014 02:08 PM, Neelesh Gupta wrote:
> The patch implements the OPAL rtc driver that binds with the rtc
> driver subsystem. The driver uses the platform device infrastructure
> to probe the rtc device and register it to rtc class framework. The
> 'wakeup' is supported depending upon the property 'has-tpo' present
> in the OF node. It provides a way to load the generic rtc driver in
> in the absence of an OPAL driver.
>
> The patch also moves the existing OPAL rtc get/set time interfaces to the
> new driver and exposes the necessary OPAL calls using EXPORT_SYMBOL_GPL.
Hi Alessandro,
Awaiting Ack from your side, so that we can take this through the
powerpc tree.
Regards,
Neelesh
>
> Test results:
> -------------
> Host:
> [root@tul169p1 ~]# ls -l /sys/class/rtc/
> total 0
> lrwxrwxrwx 1 root root 0 Oct 14 03:07 rtc0 -> ../../devices/opal-rtc/rtc/rtc0
> [root@tul169p1 ~]# cat /sys/devices/opal-rtc/rtc/rtc0/time
> 08:10:07
> [root@tul169p1 ~]# echo `date '+%s' -d '+ 2 minutes'` > /sys/class/rtc/rtc0/wakealarm
> [root@tul169p1 ~]# cat /sys/class/rtc/rtc0/wakealarm
> 1413274345
> [root@tul169p1 ~]#
>
> FSP:
> $ smgr mfgState
> standby
> $ rtim timeofday
>
> System time is valid: 2014/10/14 08:12:04.225115
>
> $ smgr mfgState
> ipling
> $
>
> Signed-off-by: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
> ---
>
> Changes in v3
> =============
> - Rebased to the latest tree.
>
> Changes in v2
> =============
> - Added Documentation/devicetree/bindings/rtc/rtc-opal.txt
> - Explicitly turn off RTC_UIE mode by setting 'rtc->uie_unsupported'
>
> Documentation/devicetree/bindings/rtc/rtc-opal.txt | 16 +
> arch/powerpc/include/asm/opal.h | 7 -
> arch/powerpc/kernel/time.c | 1
> arch/powerpc/platforms/powernv/opal-async.c | 3
> arch/powerpc/platforms/powernv/opal-rtc.c | 65 +----
> arch/powerpc/platforms/powernv/opal-wrappers.S | 2
> arch/powerpc/platforms/powernv/opal.c | 6
> arch/powerpc/platforms/powernv/setup.c | 2
> drivers/rtc/Kconfig | 11 +
> drivers/rtc/Makefile | 1
> drivers/rtc/rtc-opal.c | 261 ++++++++++++++++++++
> 11 files changed, 325 insertions(+), 50 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/rtc/rtc-opal.txt
> create mode 100644 drivers/rtc/rtc-opal.c
>
next prev parent reply other threads:[~2014-10-22 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 8:38 [PATCH v3] rtc/tpo: Driver to support rtc and wakeup on PowerNV platform Neelesh Gupta
2014-10-22 8:48 ` Neelesh Gupta [this message]
2014-11-17 6:02 ` Neelesh Gupta
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=54476F4B.8050108@linux.vnet.ibm.com \
--to=neelegup@linux.vnet.ibm.com \
--cc=a.zummo@towertech.it \
--cc=benh@au1.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rtc-linux@googlegroups.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).