All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: "Raja, Govindraj" <govindraj.raja@ti.com>
Cc: Joe Woodward <jw@terrafix.co.uk>, Kevin Hilman <khilman@ti.com>,
	linux-omap@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
	neilb@suse.de
Subject: Re: Suspend broken on 3.3?
Date: Wed, 4 Apr 2012 08:56:19 -0600 (MDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1204040852460.8000@utopia.booyaka.com> (raw)
In-Reply-To: <CAMrsUd+K_EwXfypgYWNyAhR7b47avTpWDemS87OTkpH81cJ6Aw@mail.gmail.com>

Hello Govindraj

On Mon, 2 Apr 2012, Raja, Govindraj wrote:

> As of now what I can think of is to update qos reqest to prevent MPU
> from transitioning in case of port activity if wakeup capability for port
> is disabled.

Haven't been following this thread closely, but this doesn't seem right.  
Why would changing the UART driver's ability to wake from suspend via the 
sysfs file prevent the driver from using hardware wakeups to wake from 
dynamic idle?


- Paul

  parent reply	other threads:[~2012-04-04 14:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 11:09 Suspend broken on 3.3? Joe Woodward
2012-03-22 17:33 ` Kevin Hilman
2012-03-26 13:41   ` Joe Woodward
2012-03-27  0:34     ` Kevin Hilman
2012-03-27 13:53       ` Raja, Govindraj
2012-03-27 21:37         ` Kevin Hilman
2012-03-28 10:59           ` Raja, Govindraj
2012-03-28 15:38             ` Joe Woodward
2012-03-28 17:46               ` Kevin Hilman
2012-03-29  8:35                 ` Joe Woodward
2012-03-29  9:14                   ` Shubhrajyoti Datta
2012-03-29  9:46                     ` Joe Woodward
2012-03-29 10:26                   ` Paul Walmsley
2012-03-29 11:27                     ` Joe Woodward
2012-03-29 11:40                       ` Joe Woodward
2012-03-29 14:29                         ` Raja, Govindraj
2012-03-30  7:53                           ` Joe Woodward
2012-03-30  8:46                             ` Raja, Govindraj
2012-03-30  9:26                               ` Joe Woodward
2012-03-30 10:15                                 ` Raja, Govindraj
2012-03-30 11:04                                   ` Joe Woodward
2012-03-30 12:24                                     ` Raja, Govindraj
2012-04-02 10:43                                       ` Raja, Govindraj
2012-04-02 12:37                                         ` Joe Woodward
2012-04-03  6:56                                           ` Govindraj
2012-04-04 14:56                                         ` Paul Walmsley [this message]
2012-04-04 16:13                                           ` Raja, Govindraj
2012-04-06  0:29                                             ` Paul Walmsley
2012-04-06 14:21                                               ` Kevin Hilman
2012-04-09 11:27                                                 ` Raja, Govindraj
2012-04-09 14:27                                                   ` Kevin Hilman
2012-04-09 16:01                                                     ` Paul Walmsley
2012-04-09 17:10                                                       ` Kevin Hilman
2012-04-10  9:26                                                         ` Raja, Govindraj
2012-04-10 18:03                                                           ` Kevin Hilman
2012-04-11 13:13                                                             ` Raja, Govindraj
2012-04-11 19:34                                                               ` Paul Walmsley
2012-04-12 11:51                                                                 ` Raja, Govindraj
2012-03-27 14:39       ` Joe Woodward
2012-03-27 21:28         ` 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=alpine.DEB.2.00.1204040852460.8000@utopia.booyaka.com \
    --to=paul@pwsan.com \
    --cc=balbi@ti.com \
    --cc=govindraj.raja@ti.com \
    --cc=jw@terrafix.co.uk \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=neilb@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.