From: Kevin Hilman <khilman@ti.com>
To: "Govindraj.R" <govindraj.raja@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Tero Kristo <t-kristo@ti.com>, Tony Lindgren <tony@atomide.com>,
Paul Walmsley <paul@pwsan.com>, Benoit Cousson <b-cousson@ti.com>,
Rajendra Nayak <rnayak@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH 1/2 v4] ARM: OMAP2+: omap_hwmod: Add api to enable/disable module level wakeup events
Date: Mon, 07 May 2012 11:12:23 -0700 [thread overview]
Message-ID: <874nrr508o.fsf@ti.com> (raw)
In-Reply-To: <1335338237-4095-1-git-send-email-govindraj.raja@ti.com> (Govindraj R.'s message of "Wed, 25 Apr 2012 12:47:17 +0530")
"Govindraj.R" <govindraj.raja@ti.com> writes:
> From: "Govindraj.R" <govindraj.raja@ti.com>
>
> On 24xx/34xx/36xx Module level wakeup events are enabled/disabled using
> PM_WKEN1_CORE/PM_WKEN_PER regs.
>
> Add api to control the module level wakeup mechanism from info provided from
> hwmod data.
Can you rework this slightly on top of the new SoC detection support
recently added to hwmod[1]. That series adds support for init-time, SoC
specific function pointers for this kind of SoC specific feature.
Kevin
[1] git://git.pwsan.com/linux-2.6 hwmod_soc_conditional_cleanup_3.5
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v4] ARM: OMAP2+: omap_hwmod: Add api to enable/disable module level wakeup events
Date: Mon, 07 May 2012 11:12:23 -0700 [thread overview]
Message-ID: <874nrr508o.fsf@ti.com> (raw)
In-Reply-To: <1335338237-4095-1-git-send-email-govindraj.raja@ti.com> (Govindraj R.'s message of "Wed, 25 Apr 2012 12:47:17 +0530")
"Govindraj.R" <govindraj.raja@ti.com> writes:
> From: "Govindraj.R" <govindraj.raja@ti.com>
>
> On 24xx/34xx/36xx Module level wakeup events are enabled/disabled using
> PM_WKEN1_CORE/PM_WKEN_PER regs.
>
> Add api to control the module level wakeup mechanism from info provided from
> hwmod data.
Can you rework this slightly on top of the new SoC detection support
recently added to hwmod[1]. That series adds support for init-time, SoC
specific function pointers for this kind of SoC specific feature.
Kevin
[1] git://git.pwsan.com/linux-2.6 hwmod_soc_conditional_cleanup_3.5
next prev parent reply other threads:[~2012-05-07 18:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 14:09 [PATCH v3 0/2] ARM: omap_hwmod: add api to enable/disable module level wakeup Govindraj.R
2012-04-24 14:09 ` Govindraj.R
2012-04-24 14:09 ` [PATCH v3 1/2] ARM: OMAP2+: omap_hwmod: Add api to enable/disable module level wakeup events Govindraj.R
2012-04-24 14:09 ` Govindraj.R
2012-04-24 16:07 ` Tony Lindgren
2012-04-24 16:07 ` Tony Lindgren
2012-04-24 14:09 ` [PATCH v3 2/2] ARM: omap3: pm: Remove uart module level wakeup configurations Govindraj.R
2012-04-24 14:09 ` Govindraj.R
2012-04-25 7:17 ` [PATCH 1/2 v4] ARM: OMAP2+: omap_hwmod: Add api to enable/disable module level wakeup events Govindraj.R
2012-04-25 7:17 ` Govindraj.R
2012-05-07 18:12 ` Kevin Hilman [this message]
2012-05-07 18:12 ` Kevin Hilman
2012-06-01 9:29 ` Menon, Nishanth
2012-06-01 9:29 ` Menon, Nishanth
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=874nrr508o.fsf@ti.com \
--to=khilman@ti.com \
--cc=b-cousson@ti.com \
--cc=govindraj.raja@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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 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.