[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160227072641.GX1770@lahna.fi.intel.com>
Date: Sat, 27 Feb 2016 09:26:41 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Derek Basehore <dbasehore@...omium.org>
Cc: linux-pm@...r.kernel.org, "Rafael J . Wysocki" <rjw@...ysocki.net>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org,
"Martin K . Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org
Subject: Re: [PATCH v2 3/3] scsi: allow scsi devices to use direct complete
On Wed, Feb 24, 2016 at 04:22:28PM -0800, Derek Basehore wrote:
> This allows scsi devices to remain runtime suspended for system
> suspend. Since runtime suspend is stricter than system suspend
> callbacks, this is just returning a positive number for the prepare
> callback.
AFAICT SCSI layer already leaves devices runtime suspended during system
suspend (see scsi_bus_suspend_common()). What's the benefit using
direct_complete over the current implementation?
> Signed-off-by: Derek Basehore <dbasehore@...omium.org>
> Reviewed-by: Eric Caruso <ejcaruso@...omium.org>
> ---
> drivers/scsi/scsi_pm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/scsi_pm.c b/drivers/scsi/scsi_pm.c
> index b44c1bb..7af76ad 100644
> --- a/drivers/scsi/scsi_pm.c
> +++ b/drivers/scsi/scsi_pm.c
> @@ -178,7 +178,7 @@ static int scsi_bus_prepare(struct device *dev)
> /* Wait until async scanning is finished */
> scsi_complete_async_scans();
> }
> - return 0;
> + return 1;
> }
>
> static int scsi_bus_suspend(struct device *dev)
> --
> 2.7.0.rc3.207.g0ac5344
Powered by blists - more mailing lists