From: Keerthy <a0393675@ti.com>
To: <a.zummo@towertech.it>
Cc: Keerthy <j-keerthy@ti.com>, <rtc-linux@googlegroups.com>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] rtc: OMAP: Add external 32k clock feature
Date: Tue, 17 Mar 2015 09:45:09 +0530 [thread overview]
Message-ID: <5507AA4D.3060209@ti.com> (raw)
In-Reply-To: <1425375722-13412-1-git-send-email-j-keerthy@ti.com>
On Tuesday 03 March 2015 03:12 PM, Keerthy wrote:
> Add external 32k clock feature. The internal clock will be gated during suspend.
> Hence make use of the external 32k clock so that rtc is functional accross
> suspend/resume.
A gentle ping on this.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
>
> Tested on DRA7-EVM.
>
> drivers/rtc/rtc-omap.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c
> index 8e5851a..4f803ca 100644
> --- a/drivers/rtc/rtc-omap.c
> +++ b/drivers/rtc/rtc-omap.c
> @@ -107,6 +107,8 @@
>
> /* OMAP_RTC_OSC_REG bit fields: */
> #define OMAP_RTC_OSC_32KCLK_EN BIT(6)
> +#define OMAP_RTC_OSC_OSC32K_GZ BIT(4)
> +#define OMAP_RTC_OSC_EXT_32K BIT(3)
>
> /* OMAP_RTC_IRQWAKEEN bit fields: */
> #define OMAP_RTC_IRQWAKEEN_ALARM_WAKEEN BIT(1)
> @@ -120,6 +122,7 @@
>
> struct omap_rtc_device_type {
> bool has_32kclk_en;
> + bool has_osc_ext_32k;
> bool has_kicker;
> bool has_irqwakeen;
> bool has_pmic_mode;
> @@ -446,6 +449,7 @@ static const struct omap_rtc_device_type omap_rtc_default_type = {
>
> static const struct omap_rtc_device_type omap_rtc_am3352_type = {
> .has_32kclk_en = true,
> + .has_osc_ext_32k = true,
> .has_kicker = true,
> .has_irqwakeen = true,
> .has_pmic_mode = true,
> @@ -543,7 +547,16 @@ static int __init omap_rtc_probe(struct platform_device *pdev)
> if (rtc->type->has_32kclk_en) {
> reg = rtc_read(rtc, OMAP_RTC_OSC_REG);
> rtc_writel(rtc, OMAP_RTC_OSC_REG,
> - reg | OMAP_RTC_OSC_32KCLK_EN);
> + reg | OMAP_RTC_OSC_32KCLK_EN);
> + }
> +
> + /* Enable External clock as the source */
> +
> + if (rtc->type->has_osc_ext_32k) {
> + rtc_writel(rtc, OMAP_RTC_OSC_REG,
> + (OMAP_RTC_OSC_EXT_32K |
> + rtc_read(rtc, OMAP_RTC_OSC_REG)) &
> + (~OMAP_RTC_OSC_OSC32K_GZ));
> }
>
> /* clear old status */
>
next prev parent reply other threads:[~2015-03-17 4:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 9:42 Keerthy
2015-03-17 4:15 ` Keerthy [this message]
2015-03-24 22:59 ` [rtc-linux] " Andrew Morton
2015-04-07 3:29 ` Keerthy
2015-04-07 7:06 ` Igor Grinberg
2015-04-10 8:26 ` Keerthy
2015-04-10 20:37 ` Andrew Morton
2015-04-10 22:23 ` Alexandre Belloni
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=5507AA4D.3060209@ti.com \
--to=a0393675@ti.com \
--cc=a.zummo@towertech.it \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome