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 12:07:03 +0100	[thread overview]
Message-ID: <20120925110703.GN31374@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120925103652.GN9137@arwen.pp.htv.fi>

On Tue, Sep 25, 2012 at 01:37:03PM +0300, Felipe Balbi wrote:
> On Tue, Sep 25, 2012 at 11:29:58AM +0100, Russell King - ARM Linux wrote:
> > Because you are accusing me of potentially breaking your beagleboard
> > for merely suggesting further investigation and a better commit message.
> 
> Where did I accuse you of anyting ? I just mentioned we experienced a
> regression with beagleboard XM when using pm_runtime_set_active().

I quote:
:> But should we cause a regression to beagleboard XM because of that ?
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I say again: I was _only_ suggesting further investigation, yet you
were mouthing off about causing a regression to beagleboard "because
of that", effectively saying that no, we should not do any further
investigation and this is the only fix.

> To add extra info, here you go:

Finally, something constructive.

> We pinged Paul and asked if he had seen that before, he had no
> pointers... Because Documentation/power/runtime_pm.txt was using a
> mystruct->is_suspended flag, we just decided to follow the same
> "design" since no-one was able to suggest why pm_runtime_set_active()
> was breaking beagleXM nor how it was supposed to actually work.
> 
> Reading the code: pm_runtime_set_active() would tell pm_runtime core
> the device is actually active by setting runtime_status to RPM_ACTIVE,
> thus the following pm_runtime_get_sync() wouldn't actually call
> runtime_resume() callback, but it would increment usage_counter.
> 
> I can't see why this would fail on beagleXM, but it does and we'd like
> to hear in which situations this could fail...

Well, I've just spent five minutes analysing the code paths - which I
hadn't looked at before - and I've pointed out what's probably causing
the problem for Beagle.  I think you owe me an appology over your
aggressive attitude towards my suggestions that there needed to be
some further investigation.

  reply	other threads:[~2012-09-25 11:07 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
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 [this message]
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=20120925110703.GN31374@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).