linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanmin Zhang <yanmin_zhang@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Zhang, LongX" <longx.zhang@intel.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pm@lists.linux-foundation.org"
	<linux-pm@lists.linux-foundation.org>
Subject: Re: Subject: [PATCH] drivers-core: move device_pm_remove behind bus_remove_device
Date: Thu, 18 Oct 2012 08:21:37 +0800	[thread overview]
Message-ID: <1350519697.2207.9.camel@ymzhang.sh.intel.com> (raw)
In-Reply-To: <2338561.PDRRozbqko@vostro.rjw.lan>

On Mon, 2012-10-15 at 22:59 +0200, Rafael J. Wysocki wrote:
> On Monday 15 of October 2012 15:39:49 Yanmin Zhang wrote:
> > On Fri, 2012-09-21 at 01:58 +0000, Zhang, LongX wrote:
> > > From: LongX Zhang <longx.zhang@intel.com>
> > > 
> > > device_pm_remove will call pm_runtime_remove which would disable
> > > runtime PM of the device. After that pm_runtime_get* or
> > > pm_runtime_put* will be ingored. So if we disable the runtime PM
> > > before device really be removed, drivers' _remove callback may
> > > access HW even pm_runtime_get* fails. That is bad.
> > The background about the patch: We hit an hang issue when removing a mmc
> > device on Medfield Android phone by sysfs interface.
> > 
> > Consider below call sequence when removing a device:
> > device_del => device_pm_remove
> >            => class_intf->remove_dev(dev, class_intf)  => pm_runtime_get_sync/put_sync
> >            => bus_remove_device => device_release_driver => pm_runtime_get_sync/put_sync
> > 
> > remove_dev might call pm_runtime_get_sync/put_sync.
> > Then, generic device_release_driver also calls pm_runtime_get_sync/put_sync.
> > Since device_del => device_pm_remove firstly, later _get_sync wouldn't really
> > wake up the device.
> > 
> > I git log -p to find the patch which moves the calling to device_pm_remove ahead.
> > It's below patch:
> > 
> > commit 775b64d2b6ca37697de925f70799c710aab5849a
> > Author: Rafael J. Wysocki <rjw@sisk.pl>
> > Date:   Sat Jan 12 20:40:46 2008 +0100
> > 
> >     PM: Acquire device locks on suspend
> >     
> >     This patch reorganizes the way suspend and resume notifications are
> >     sent to drivers.  The major changes are that now the PM core acquires
> >     every device semaphore before calling the methods, and calls to
> >     device_add() during suspends will fail, while calls to device_del()
> >     during suspends will block.
> >     
> >     It also provides a way to safely remove a suspended device with the
> >     help of the PM core, by using the device_pm_schedule_removal() callback
> >     introduced specifically for this purpose, and updates two drivers (msr
> >     and cpuid) that need to use it.
> > 
> > 
> > As device_pm_schedule_removal is deleted by another patch, we need also revert
> > other parts of the patch, i.e. move the calling of device_pm_remove after
> > the calling to bus_remove_device.
> > 
> > > 
> > > Signed-off-by: LongX Zhang <longx.zhang@intel.com>
> 
> Can you please resend the patch?  I lost the track of it unfortunately.
Long sent V2 out. See https://lkml.org/lkml/2012/10/16/594.

      reply	other threads:[~2012-10-18  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  1:58 Subject: [PATCH] drivers-core: move device_pm_remove behind bus_remove_device Zhang, LongX
2012-10-15  7:39 ` Yanmin Zhang
2012-10-15 20:59   ` Rafael J. Wysocki
2012-10-18  0:21     ` Yanmin Zhang [this message]

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=1350519697.2207.9.camel@ymzhang.sh.intel.com \
    --to=yanmin_zhang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=longx.zhang@intel.com \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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).