linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFT/PATCH] serial: omap: prevent resume if device is not suspended.
Date: Tue, 25 Sep 2012 09:30:29 +0100	[thread overview]
Message-ID: <20120925083029.GG31374@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKdam572krJZcayRdJ_AciCUZH3LuzD9yoHenhxrB6j9xDZ6JQ@mail.gmail.com>

On Tue, Sep 25, 2012 at 01:52:03PM +0530, Poddar, Sourav wrote:
> Hi Greg,
> 
> Ping on this?
> 
> On Tue, Sep 18, 2012 at 6:10 PM, Sourav Poddar <sourav.poddar@ti.com> wrote:
> > Greg's tty-next is not booting on 2420 based N800. The failure is
> > observed at serial init itself. The reason might be that n800 tries to
> > resume even though it is not suspended before.

How is this happening?  I think that needs proper investigation - or if
it's had more investigation, then the results needs to be included in
the commit description so that everyone can understand the issue here.

We should not be resuming a device which hasn't been suspended.  Maybe
the runtime PM enable sequence is wrong, and that's what should be fixed
instead?  

This sequence in the probe() function:

        pm_runtime_irq_safe(&pdev->dev);
        pm_runtime_enable(&pdev->dev);
        pm_runtime_get_sync(&pdev->dev);

would enable runtime PM while the s/w state indicates that it's disabled,
and then that pm_runtime_get_sync() will want to resume the device.  See
the section "5. Runtime PM Initialization, Device Probing and Removal"
in Documentation/power/runtime_pm.txt, specifically the second paragraph
of that section.

  reply	other threads:[~2012-09-25  8:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 12:40 [RFT/PATCH] serial: omap: prevent resume if device is not suspended Sourav Poddar
2012-09-18 14:02 ` Felipe Balbi
2012-09-18 22:57   ` Paul Walmsley
2012-09-19 11:52   ` Grazvydas Ignotas
2012-09-19 11:59     ` Felipe Balbi
2012-09-25 12:29       ` Jassi Brar
2012-09-25  8:22 ` Poddar, Sourav
2012-09-25  8:30   ` Russell King - ARM Linux [this message]
2012-09-25  8:31     ` Felipe Balbi
2012-09-25  9:12       ` Russell King - ARM Linux
2012-09-25  9:11         ` Felipe Balbi
2012-09-25  9:21           ` Russell King - ARM Linux
2012-09-25  9:48             ` Felipe Balbi
2012-09-25 10:29               ` Russell King - ARM Linux
2012-09-25 10:37                 ` Felipe Balbi
2012-09-25 11:07                   ` Russell King - ARM Linux
2012-09-25 11:12                     ` Felipe Balbi
2012-09-25 11:32                       ` Russell King - ARM Linux
2012-09-25  9:56             ` Poddar, Sourav
2012-09-25 10:59               ` Russell King - ARM Linux
2012-10-03  0:33               ` Kevin Hilman
2012-10-11 18:28                 ` Paul Walmsley
2012-10-12 16:24                   ` Sourav
2012-10-12 16:35                     ` Kevin Hilman
2012-10-12 16:42                       ` Russell King - ARM Linux
2012-10-12 17:29                         ` Poddar, Sourav
2012-10-12 18:49                           ` Russell King - ARM Linux
2012-10-12 17:59                         ` Kevin Hilman
2012-10-12 18:54                           ` Russell King - ARM Linux
2012-10-12 20:32                             ` Kevin Hilman
2012-10-12 21:51                               ` Tony Lindgren
2012-10-15 22:37                                 ` Kevin Hilman
2012-09-25 11:15           ` Russell King - ARM Linux
2012-09-26 20:30   ` Greg KH

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=20120925083029.GG31374@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).