linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] OMAP3: PM: ensure IO wakeups are properly disabled
Date: Fri, 20 Aug 2010 09:56:50 +0300	[thread overview]
Message-ID: <20100820065649.GH25742@atomide.com> (raw)
In-Reply-To: <4C6D7936.3090201@ru.mvista.com>

* Sergei Shtylyov <sshtylyov@mvista.com> [100819 21:27]:
> Hello.
> 
> Kevin Hilman wrote:
> 
> >>>>>From: Kevin Hilman <khilman@ti.com>
> >>>>>Commit 5a5f561 (convert OMAP3 PRCM macros to the _SHIFT/_MASK suffixes)
> >>>>>mistakenly removed the check for PER when disabling the IO chain.
> >>>>>During idle, if the PER powerdomain transitions and CORE does not (as
> 
> >>>>  Does not what?
> 
> >>>How about ".. and CORE does not transition"?
> 
> >>   Transition to what then? Sentense till won't parse right...
> 
> >>>Kevin, care to clarify that?
> >>   Yeah, looks like a considerable partt of that sentense got omitted...
> 
> >No.  Nothing was omitted.
> 
> >It's like saying "Tony drinks Fernet and Kevin does not."  Adding an
> >additional "drinks Fernet" at the end is redundant.
> 
>    Sorry, the sentence still doesn't parse for me. You don't say
> "Fernet" there BTW, so it's not clear where the PER powerdomain
> transitions to. What goes after the closing parenthesis doesn't
> clear things up either, it just describes what happens if...

I'll update it with the following to preserve the Fernet style,
and to describe the transition:

During idle, if the PER powerdomain transitions into a lower state
and CORE does not, the IO pad wakeups are not being disabled in
the idle path after they are enabled. This can happen with the
lower C-states when using CPUidle for example.

Updated patch attached.

Please reply ASAP if this is not OK, I'd like to get a pull
request for these fixes sent to Linus over the weekend.

Regards,

Tony
-------------- next part --------------
A non-text attachment was scrubbed...
Name: omap3-pm-ensure-io-wakeups-are-properly-disabled.patch
Type: text/x-diff
Size: 1872 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100820/16fe0adb/attachment.bin>

  reply	other threads:[~2010-08-20  6:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13  8:01 [PATCH 0/6] omap fixes for upcoming 2.6.36-rc1 Tony Lindgren
2010-08-13  8:01 ` [PATCH 1/6] omap3: id: fix 3630 rev detection Tony Lindgren
2010-08-13  8:01 ` [PATCH 2/6] OMAP3: Fix a cpu type check problem Tony Lindgren
2010-08-13  8:02 ` [PATCH 3/6] OMAP3: PM: ensure IO wakeups are properly disabled Tony Lindgren
2010-08-13  9:53   ` Sergei Shtylyov
2010-08-13 10:29     ` Tony Lindgren
2010-08-13 10:50       ` Sergei Shtylyov
2010-08-19 18:14         ` Kevin Hilman
2010-08-19 18:34           ` Sergei Shtylyov
2010-08-20  6:56             ` Tony Lindgren [this message]
2010-08-20 16:43               ` Kevin Hilman
2010-08-13  8:02 ` [PATCH 4/6] omap: Fix sev instruction usage for multi-omap Tony Lindgren
2010-08-13  9:04   ` Shilimkar, Santosh
2010-08-13  8:02 ` [PATCH 5/6] omap: Use CONFIG_SMP for test_for_ipi and test_for_ltirq Tony Lindgren
2010-08-13  9:04   ` Shilimkar, Santosh
2010-08-13  8:02 ` [PATCH 6/6] omap: Fix omap_4430sdp_defconfig for make oldconfig Tony Lindgren
2010-08-13  9:04   ` Shilimkar, Santosh

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=20100820065649.GH25742@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).