From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Varadarajan, Charulatha" <charu@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Basak, Partha" <p-basak2@ti.com>,
Tero Kristo <tero.kristo@nokia.com>
Subject: Re: [PATCH 2/2] OMAP2+: GPIO: move late PM out of interrupts-disabled idle path
Date: Tue, 14 Sep 2010 07:41:03 -0700 [thread overview]
Message-ID: <87fwxcwfpc.fsf@deeprootsystems.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02CD25F71C@dbde02.ent.ti.com> (Charulatha Varadarajan's message of "Tue, 14 Sep 2010 19:44:33 +0530")
"Varadarajan, Charulatha" <charu@ti.com> writes:
[...]
>> -void omap2_gpio_prepare_for_idle(int power_state)
>> +void omap2_gpio_prepare_for_idle(void)
>> {
>> - int i, c = 0;
>> - int min = 0;
>> + int i, c = 0, min = 0;
>> + int per_next_state;
>> +
>> + if (!per_pwrdm)
>> + return;
>
> "per_pwrdm" is not available for OMAP24xx. Hence
> this breaks the omap2_gpio_prepare_for_idle() path for OMAP2.
>
> In OMAP2420, all gpio banks are in wakeup domain and
> in OMAP2430 GPIO banks 1-4 are in wakeup domain & GPIO5 is
> in core domain.
Sure, this patch is just a proof of concept that we can move the GPIO
idle management out of the interrupts disabled path.
When you adapt this approach to your conversion series, since you have
already broken these functions up to be per-bank, you can have a
per-bank powerdomain that can be configured per-SoC.
Kevin
next prev parent reply other threads:[~2010-09-14 14:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 23:02 [PATCH 0/2] idle-path reorg for interrupt-enabled runtime PM Kevin Hilman
2010-09-13 23:02 ` [PATCH 1/2] OMAP3: PM: move device-specific special cases from PM core into CPUidle Kevin Hilman
2010-09-13 23:02 ` [PATCH 2/2] OMAP2+: GPIO: move late PM out of interrupts-disabled idle path Kevin Hilman
2010-09-14 14:14 ` Varadarajan, Charulatha
2010-09-14 14:41 ` Kevin Hilman [this message]
2010-09-14 16:09 ` Basak, Partha
2010-09-14 16:57 ` Kevin Hilman
2010-09-15 8:02 ` Basak, Partha
2010-09-23 12:54 ` Basak, Partha
2010-09-23 15:38 ` Kevin Hilman
2010-09-23 19:57 ` Basak, Partha
2010-09-23 23:18 ` Kevin Hilman
2010-09-23 23:53 ` Kevin Hilman
2010-09-25 3:30 ` Basak, Partha
2010-09-27 14:53 ` Kevin Hilman
2010-09-22 8:22 ` Kalliguddi, Hema
2010-09-22 14:24 ` Kevin Hilman
2010-09-22 15:09 ` Kalliguddi, Hema
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=87fwxcwfpc.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=charu@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=tero.kristo@nokia.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;
as well as URLs for NNTP newsgroup(s).