summaryrefslogtreecommitdiffstats
path: root/drivers/parport
diff options
context:
space:
mode:
authorRafael J. Wysocki <rjw@sisk.pl>2012-12-02 14:48:50 +0100
committerChris Ball <cjb@laptop.org>2012-12-06 13:55:04 -0500
commitb0afd8f68adf6a9b671b0420ab9116a36409ef7f (patch)
treeb73bdeb24d8ae2444480f8c0572f6c17f2f5168b /drivers/parport
parent063f96c2230052356d8653381912e618a8ae951c (diff)
downloadlinux-b0afd8f68adf6a9b671b0420ab9116a36409ef7f.tar.bz2
mmc: sdio: Add empty bus-level suspend/resume callbacks
Suspend methods provided by SDIO drivers are not supposed to be called by the PM core. Instead, when the SDIO core gets to suspend a device's ancestor, it calls the device driver's suspend routine. However, the PM core executes suspend callback routines directly for device drivers whose bus types don't provide suspend callbacks. In consequece, because the SDIO bus type doesn't provide a suspend callback, the SDIO drivers' suspend routines will be executed by the PM core (which shouldn't happen). To prevent this from happening, add empty system suspend/resume callbacks for the SDIO bus type. An analogous change had been made already by commit (e841a7c mmc: sdio: Use empty system suspend/resume callbacks at the bus level), but then it was reverted inadvertently by commit (d8e2ac3 mmc: sdio: Fix PM_SLEEP related build warnings) that attempted to fix build warnings introduced by commit e841a7c. Reported-by: NeilBrown <neilb@suse.de> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'drivers/parport')
0 files changed, 0 insertions, 0 deletions