From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] rtc: omap: add rtc wakeup support to alarm events
Date: Fri, 31 May 2013 10:41:22 -0700 [thread overview]
Message-ID: <87a9nb2gjh.fsf@linaro.org> (raw)
In-Reply-To: <1369982005-8572-3-git-send-email-gururaja.hebbar@ti.com> (Hebbar Gururaja's message of "Fri, 31 May 2013 12:03:25 +0530")
Hebbar Gururaja <gururaja.hebbar@ti.com> writes:
> On some platforms (like AM33xx), a special register (RTC_IRQWAKEEN)
> is available to enable Wakeup feature for Alarm Events.
>
> Since new platforms/Boards are now added through DT only, this feature
> is supported via DT property only.
> Platforms using such IP should add the property "ti,has_irq_wake_enb"
> in rtc DT node.
This is a property of the IP, not the board. Can't you detect this
based on the revision of the IP?
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@linaro.org>
To: Hebbar Gururaja <gururaja.hebbar@ti.com>
Cc: akpm@linux-foundation.org, linux@arm.linux.org.uk,
zonque@gmail.com, linux-arm-kernel@lists.infradead.org,
grant.likely@linaro.org, rob.herring@calxeda.com,
rob@landley.net, a.zummo@towertech.it,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
davinci-linux-open-source@linux.davincidsp.com,
vaibhav.bedia@ti.com, sudhakar.raj@ti.com
Subject: Re: [PATCH 2/2] rtc: omap: add rtc wakeup support to alarm events
Date: Fri, 31 May 2013 10:41:22 -0700 [thread overview]
Message-ID: <87a9nb2gjh.fsf@linaro.org> (raw)
In-Reply-To: <1369982005-8572-3-git-send-email-gururaja.hebbar@ti.com> (Hebbar Gururaja's message of "Fri, 31 May 2013 12:03:25 +0530")
Hebbar Gururaja <gururaja.hebbar@ti.com> writes:
> On some platforms (like AM33xx), a special register (RTC_IRQWAKEEN)
> is available to enable Wakeup feature for Alarm Events.
>
> Since new platforms/Boards are now added through DT only, this feature
> is supported via DT property only.
> Platforms using such IP should add the property "ti,has_irq_wake_enb"
> in rtc DT node.
This is a property of the IP, not the board. Can't you detect this
based on the revision of the IP?
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@linaro.org>
To: Hebbar Gururaja <gururaja.hebbar@ti.com>
Cc: <akpm@linux-foundation.org>, <linux@arm.linux.org.uk>,
<zonque@gmail.com>, <linux-arm-kernel@lists.infradead.org>,
<grant.likely@linaro.org>, <rob.herring@calxeda.com>,
<rob@landley.net>, <a.zummo@towertech.it>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<rtc-linux@googlegroups.com>,
<davinci-linux-open-source@linux.davincidsp.com>,
<vaibhav.bedia@ti.com>, <sudhakar.raj@ti.com>
Subject: Re: [PATCH 2/2] rtc: omap: add rtc wakeup support to alarm events
Date: Fri, 31 May 2013 10:41:22 -0700 [thread overview]
Message-ID: <87a9nb2gjh.fsf@linaro.org> (raw)
In-Reply-To: <1369982005-8572-3-git-send-email-gururaja.hebbar@ti.com> (Hebbar Gururaja's message of "Fri, 31 May 2013 12:03:25 +0530")
Hebbar Gururaja <gururaja.hebbar@ti.com> writes:
> On some platforms (like AM33xx), a special register (RTC_IRQWAKEEN)
> is available to enable Wakeup feature for Alarm Events.
>
> Since new platforms/Boards are now added through DT only, this feature
> is supported via DT property only.
> Platforms using such IP should add the property "ti,has_irq_wake_enb"
> in rtc DT node.
This is a property of the IP, not the board. Can't you detect this
based on the revision of the IP?
Kevin
next prev parent reply other threads:[~2013-05-31 17:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 6:33 [PATCH 0/2] rtc: rtc-omap: add support for DT wakeup & alarm events Hebbar Gururaja
2013-05-31 6:33 ` Hebbar Gururaja
2013-05-31 6:33 ` Hebbar Gururaja
2013-05-31 6:33 ` [PATCH 1/2] rtc: omap: add option to indicate wakeup support through DT Hebbar Gururaja
2013-05-31 6:33 ` Hebbar Gururaja
2013-05-31 6:33 ` Hebbar Gururaja
2013-05-31 6:44 ` Prabhakar Lad
2013-05-31 6:44 ` Prabhakar Lad
2013-05-31 6:46 ` Hebbar, Gururaja
2013-05-31 6:46 ` Hebbar, Gururaja
2013-05-31 6:46 ` Hebbar, Gururaja
2013-05-31 17:48 ` Kevin Hilman
2013-05-31 17:48 ` Kevin Hilman
2013-05-31 17:48 ` Kevin Hilman
2013-06-04 9:48 ` Hebbar, Gururaja
2013-06-04 9:48 ` Hebbar, Gururaja
2013-06-04 9:48 ` Hebbar, Gururaja
2013-05-31 6:33 ` [PATCH 2/2] rtc: omap: add rtc wakeup support to alarm events Hebbar Gururaja
2013-05-31 6:33 ` Hebbar Gururaja
2013-05-31 6:33 ` Hebbar Gururaja
2013-05-31 6:50 ` Prabhakar Lad
2013-05-31 6:50 ` Prabhakar Lad
2013-05-31 17:41 ` Kevin Hilman [this message]
2013-05-31 17:41 ` Kevin Hilman
2013-05-31 17:41 ` Kevin Hilman
2013-06-04 9:39 ` Hebbar, Gururaja
2013-06-04 9:39 ` Hebbar, Gururaja
2013-06-04 9:39 ` Hebbar, Gururaja
2013-06-10 11:25 ` Hebbar, Gururaja
2013-06-10 11:25 ` Hebbar, Gururaja
2013-06-10 11:25 ` Hebbar, Gururaja
2013-06-13 9:39 ` Hebbar, Gururaja
2013-06-13 9:39 ` Hebbar, Gururaja
2013-06-13 9:39 ` Hebbar, Gururaja
2013-06-13 22:21 ` Kevin Hilman
2013-06-13 22:21 ` Kevin Hilman
2013-06-13 22:21 ` Kevin Hilman
2013-06-14 11:38 ` Hebbar, Gururaja
2013-06-14 11:38 ` Hebbar, Gururaja
2013-06-14 11:38 ` Hebbar, Gururaja
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=87a9nb2gjh.fsf@linaro.org \
--to=khilman@linaro.org \
--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 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.