From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch V2 2/4] ARM: Davinci: da8xx/omap-l1: Remove hard coding of rtc device wakeup
Date: Fri, 16 Aug 2013 17:32:13 +0530 [thread overview]
Message-ID: <520E14C5.9090308@ti.com> (raw)
In-Reply-To: <1372841225-18813-3-git-send-email-gururaja.hebbar@ti.com>
On Wednesday 03 July 2013 02:17 PM, Hebbar Gururaja wrote:
> Since now rtc-omap driver itself calls deice_init_wakeup(dev, true),
> duplicate call from the rtc device registration can be removed.
>
> This is basically a partial revert of the prev commit
>
> commit 75c99bb0006ee065b4e2995078d779418b0fab54
> Author: Sekhar Nori <nsekhar@ti.com>
>
> davinci: da8xx/omap-l1: mark RTC as a wakeup source
>
> Signed-off-by: Hebbar Gururaja <gururaja.hebbar@ti.com>
> Acked-by: Kevin Hilman <khilman@linaro.org>
> Acked-by: Sekhar Nori <nsekhar@ti.com>
> Cc: Russell King <linux@arm.linux.org.uk>
Queuing for v3.12. In subject line, please use lower case except for
acronyms and for "ARM". Also, we dont use omap-l1 to avoid confusion
with the real omaps. Just da8xx is enough. I have fixed these locally
this time.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-08-16 12:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 8:47 [Patch V2 0/4] rtc: omap: handle rtc wakeup support in driver Hebbar Gururaja
2013-07-03 8:47 ` [Patch V2 1/4] rtc: omap: restore back (hard-code) wakeup support Hebbar Gururaja
2013-07-03 8:47 ` [Patch V2 2/4] ARM: Davinci: da8xx/omap-l1: Remove hard coding of rtc device wakeup Hebbar Gururaja
2013-08-16 12:02 ` Sekhar Nori [this message]
2013-07-03 8:47 ` [Patch V2 3/4] rtc: omap: add rtc wakeup support to alarm events Hebbar Gururaja
2013-07-24 13:14 ` Gururaja Hebbar
2013-07-03 8:47 ` [Patch V2 4/4] ARM: dts: AM33XX: update rtc node compatibility Hebbar Gururaja
2013-07-30 5:05 ` Gururaja Hebbar
2013-07-30 14:55 ` Mark Rutland
2013-07-30 16:21 ` Sekhar Nori
2013-08-01 17:05 ` Mark Rutland
2013-08-02 11:07 ` Gururaja Hebbar
2013-08-02 11:20 ` Mark Rutland
2013-08-02 11:48 ` Gururaja Hebbar
2013-08-02 12:40 ` Mark Rutland
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=520E14C5.9090308@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).