From: Jon Hunter <jon-hunter@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH][RFC] OMAP3: PM: Prevent hang in prcm_interrupt_handler
Date: Thu, 25 Jun 2009 13:56:31 -0500 [thread overview]
Message-ID: <4A43C85F.50703@ti.com> (raw)
In-Reply-To: <87prcv25ro.fsf@deeprootsystems.com>
Kevin Hilman wrote:
> Jon Hunter <jon-hunter@ti.com> writes:
>
>> From: Jon Hunter <jon-hunter@ti.com>
>>
>> There are two scenarios where a race condition could result in a hang in the
>> prcm_interrupt handler. These are:
>
> IIRC, the RX51 tree has a workaround for some hangs seen in this
> interrupt handler as well, so this has definitely been seen. The fix
> there though was just to no loop, I think your fix is more thorough
> and fixes the root cause. Thanks.
>
> No comments on the funtional changes, but a couple
> cosmetic/documentation changes.
>
> 1) Would it be possible to summarize the requirements in the function
> itself as part of this patch.
Absolutely. I will add some comments.
> 2) With the extra indentation, this function is getting too indented.
> Looking closer, an abstraction of the 'enable clocks, poll PM_WKST,
> disable clocks loop' could be done an called with the various modules
> and offsets. I've attached a hack/patch below to show what I mean.
> You could just fold this into your patch.
Yes that makes a lot of sense. I did not like the fact it was becoming
difficult to read with the extra indentation. I will re-work this and
get you something in the next couple days.
Thanks for the feedback.
Cheers
Jon
next prev parent reply other threads:[~2009-06-25 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 23:08 [PATCH][RFC] OMAP3: PM: Prevent hang in prcm_interrupt_handler Jon Hunter
2009-06-22 23:44 ` Kevin Hilman
2009-06-25 18:56 ` Jon Hunter [this message]
2009-06-27 5:07 ` Jon Hunter
2009-06-29 21:11 ` Kevin Hilman
2009-07-22 17:09 ` Kevin Hilman
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=4A43C85F.50703@ti.com \
--to=jon-hunter@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox