All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: balajitk@ti.com
Cc: linux-omap@vger.kernel.org, sameo@linux.intel.com, wim@iguana.be,
	timo.t.kokkonen@nokia.com, ben-linux@fluff.org,
	lrg@slimlogic.co.uk, broonie@opensource.wolfsonmicro.com,
	p_gortmaker@yahoo.com, a.zummo@towertech.it,
	rtc-linux@googlegroups.com,
	Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH v3 02/04] OMAP4: PMIC: Add support for twl6030 RTC
Date: Thu, 01 Oct 2009 11:35:19 -0700	[thread overview]
Message-ID: <87ws3fc68o.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1254399821-3982-1-git-send-email-balajitk@ti.com> (balajitk@ti.com's message of "Thu\,  1 Oct 2009 17\:53\:41 +0530")

balajitk@ti.com writes:

> From: Balaji T K <balajitk@ti.com>
>
> This version of patch series enables RUN TIME selection of TWL4030 or TWL6030.
>
> This patch adds support for RTC in phoenix TWL6030.
> Register offset addresses have changed in TWL6030
> rtc-twl.c will hence forth support all twl RTC (4030, 5030, 6030 ..)
>
> Signed-off-by: Balaji T K <balajitk@ti.com>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Reviewed-by: Tony Lindgren <tony@atomide.com>

[...]

> @@ -352,6 +401,7 @@ static irqreturn_t twl_rtc_interrupt(int irq, void *rtc)
>  	if (res)
>  		goto out;
>  
> +if (twl_class_is_4030()) {

indentation?

>  	/* Clear on Read enabled. RTC_IT bit of TWL4030_INT_PWR_ISR1
>  	 * needs 2 reads to clear the interrupt. One read is done in
>  	 * do_twl_pwrirq(). Doing the second read, to clear
> @@ -367,6 +417,7 @@ static irqreturn_t twl_rtc_interrupt(int irq, void *rtc)
>  			&rd_reg, TWL4030_INT_PWR_ISR1);
>  	if (res)
>  		goto out;
> +}

and here?

after that,

Reviewed-by: Kevin Hilman <khilman@deeprootsystems.com>



      reply	other threads:[~2009-10-01 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 12:23 [PATCH v3 02/04] OMAP4: PMIC: Add support for twl6030 RTC balajitk
2009-10-01 18:35 ` Kevin Hilman [this message]

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=87ws3fc68o.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=a.zummo@towertech.it \
    --cc=balajitk@ti.com \
    --cc=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=p_gortmaker@yahoo.com \
    --cc=rtc-linux@googlegroups.com \
    --cc=sameo@linux.intel.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=timo.t.kokkonen@nokia.com \
    --cc=wim@iguana.be \
    /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.