From: "Cousson, Benoit" <b-cousson@ti.com>
To: "kalle.jokiniemi@nokia.com" <kalle.jokiniemi@nokia.com>
Cc: "paul@pwsan.com" <paul@pwsan.com>,
"Hilman, Kevin" <khilman@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"ilkka.koskinen@nokia.com" <ilkka.koskinen@nokia.com>,
"jhnikula@gmail.com" <jhnikula@gmail.com>
Subject: Re: [PATCH 0/2] OMAP3: wdtimer: fix wdtimer blocking CORE idle
Date: Thu, 10 Mar 2011 12:14:24 +0100 [thread overview]
Message-ID: <4D78B290.7070905@ti.com> (raw)
In-Reply-To: <9D0D31AA57AAF5499AFDC63D6472631B065E79@008-AM1MPN1-036.mgdnok.nokia.com>
Paul,
On 3/10/2011 11:28 AM, kalle.jokiniemi@nokia.com wrote:
>
>
>> -----Original Message-----
>> From: ext Paul Walmsley [mailto:paul@pwsan.com]
>> Sent: 10. maaliskuuta 2011 11:50
>> To: Jokiniemi Kalle (Nokia-MS/Tampere)
>> Cc: khilman@ti.com; linux-omap@vger.kernel.org; Koskinen Ilkka (Nokia-
>> MS/Tampere); jhnikula@gmail.com; b-cousson@ti.com
>> Subject: Re: [PATCH 0/2] OMAP3: wdtimer: fix wdtimer blocking CORE idle
>>
>>
>> Thanks Kalle for tracking this down,
>>
>> could you try this patch along with the patch from this message:
>>
>> http://www.spinics.net/lists/linux-omap/msg48115.html
I have some question with that patch.
By using pm_runtime API, you are suppose to idle the whole IP.
In this case, just because you cannot idle a wdt that is running, it
works, but the point is that the pm_runtime state will not reflect the
HW state.
For pm_runtime point of view, the wdt is supposed to be fully idle (both
fclk and iclk). Whereas in that case, only the iclk will be gated.
Did I miss something?
Benoit
>> and see if it also fixes the problem?
>
> It works as well it seems :)
>
> I assume you prefer this fix to be applied, so I'll send patches on this.
>
> - Kalle
>
>
>>
>> This patch should also prevent the hwmod code from putting the WDT2 into
>> smart-idle mode.
>>
>>
>> - Paul
>>
>>
>> ---
>> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
>> b/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
>> index 457df3e..4366b85 100644
>> --- a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
>> +++ b/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
>> @@ -1294,6 +1294,7 @@ static struct omap_hwmod
>> omap3xxx_wd_timer2_hwmod = {
>> .slaves = omap3xxx_wd_timer2_slaves,
>> .slaves_cnt = ARRAY_SIZE(omap3xxx_wd_timer2_slaves),
>> .omap_chip = OMAP_CHIP_INIT(CHIP_IS_OMAP3430),
>> + .flags = HWMOD_SWSUP_SIDLE,
>> };
>>
>> /* UART common */
>> --
>> 1.7.2.3
>
next prev parent reply other threads:[~2011-03-10 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 9:32 [PATCH 0/2] OMAP3: wdtimer: fix wdtimer blocking CORE idle Kalle Jokiniemi
2011-03-10 9:32 ` [PATCH 1/2] OMAP: hw_mod: consider supported idlemodes in enable_sysc Kalle Jokiniemi
2011-03-10 9:32 ` [PATCH 2/2] OMAP3: wdtimer: Disable SMART idle mode Kalle Jokiniemi
2011-03-10 9:50 ` [PATCH 0/2] OMAP3: wdtimer: fix wdtimer blocking CORE idle Paul Walmsley
2011-03-10 10:28 ` kalle.jokiniemi
2011-03-10 10:52 ` Paul Walmsley
2011-03-10 11:14 ` Cousson, Benoit [this message]
2011-03-10 13:08 ` Paul Walmsley
2011-03-10 13:54 ` Cousson, Benoit
2011-03-10 15:25 ` Cousson, Benoit
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=4D78B290.7070905@ti.com \
--to=b-cousson@ti.com \
--cc=ilkka.koskinen@nokia.com \
--cc=jhnikula@gmail.com \
--cc=kalle.jokiniemi@nokia.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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).