From: "Cousson, Benoit" <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "kalle.jokiniemi@nokia.com" <kalle.jokiniemi@nokia.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 14:54:11 +0100 [thread overview]
Message-ID: <4D78D803.6080309@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103100604460.15132@utopia.booyaka.com>
On 3/10/2011 2:08 PM, Paul Walmsley wrote:
> Hi Benoît,
>
> On Thu, 10 Mar 2011, Cousson, Benoit wrote:
>
>> On 3/10/2011 11:28 AM, kalle.jokiniemi@nokia.com wrote:
>>>
>>>> From: ext Paul Walmsley [mailto:paul@pwsan.com]
>>>> Sent: 10. maaliskuuta 2011 11:50
>>>>
>>>> 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?
>
> Looking at it, I don't know how the old driver managed to work at all.
> Commit 7ec5ad0f3c1e28b693185c35f768953c5db32291 ("OMAP: WDT: Use PM
> runtime APIs instead of clk FW APIs") removed this from omap_wdt_probe():
>
> - /* autogate OCP interface clock */
> - __raw_writel(0x01, wdev->base + OMAP_WATCHDOG_SYS_CONFIG);
>
> This would put the WDTIMER into force-idle, and nothing ever took it out
> of force-idle. So I don't quite understand why the PRCM wouldn't just
> turn off the functional clock to the WDTIMER at this point. Any thoughts
> on this?
The idle definition of the PRCM is just: idle of the ocp clock (iclk).
The fclk can be active while the module is "idle" for the PRCM point of
view.
That's why we have a mismatch in that case with the pm_runtime idle
definition, where the module should be fully idle.
In that case, since the WDT is in the wakeup domain, we do not even have
to re-enable the iclk since the wakeup domain is always on whenever the
MPU is running.
That fact that we have to explicitly do a force idle, probably means
that the autoidle is broken in the IP.
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-10 13:54 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
2011-03-10 13:08 ` Paul Walmsley
2011-03-10 13:54 ` Cousson, Benoit [this message]
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=4D78D803.6080309@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).