All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Aaron Lu <aaron.lu@intel.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Tejun Heo <tj@kernel.org>,
	Aaron Lu <aaron.lwe@gmail.com>, Jeff Wu <jeff.wu@amd.com>,
	linux-ide@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v13 1/9] scsi: sr: support runtime pm
Date: Fri, 18 Jan 2013 10:24:28 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1301181017070.1988-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20130118074240.GA6861@aaronlu.sh.intel.com>

On Fri, 18 Jan 2013, Aaron Lu wrote:

> > Aaron, have you checked whether this patch works okay when you play a
> > track on an audio-only CD on the computer?  The block interface looks 
> > okay but I'm not sure about the cdrom_device interface.
> 
> Just verified it works OK with the whole patchset applied using 2 audio
> CDs.
> 
> After the ODD has been put into zero power state, insert an audio cd.
> ODD will be resumed, gvfs will automatically mount the disc, and a
> dialog titled "Audio Disc" asks me what to do. Press OK, the rhythmbox
> application will get started. Press the Play button of rhythmbox, songs
> will start to play, and runtime_usage is 2. Eject the disc, the ODD will
> be put to zero power state some time later.

What happens if you use a non-ZP drive?

What happens if you're not running a desktop graphical environment, so
gvfs doesn't mount the disc?  Basically, I'm worried that the drive may
remain suspended after sr_open() returns.

What happens if you use a program other than rhythmbox?  There are (or
used to be) programs which would issue the PLAY AUDIO command and then
exit.  The drive would continue playing even while the device file was
closed.  Do we want to drop support for that kind of behavior?

Alan Stern


  reply	other threads:[~2013-01-18 15:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15  9:20 [PATCH v13 0/9] ZPODD Patches Aaron Lu
2013-01-15  9:20 ` [PATCH v13 1/9] scsi: sr: support runtime pm Aaron Lu
2013-01-16 15:45   ` James Bottomley
2013-01-16 16:31     ` Alan Stern
2013-01-18  7:42       ` Aaron Lu
2013-01-18 15:24         ` Alan Stern [this message]
2013-01-19  8:55           ` Aaron Lu
2013-01-19 18:46             ` Alan Stern
2013-01-21  3:31               ` Julian Calaby
2013-01-21  8:14                 ` Aaron Lu
2013-01-21  8:55                   ` Julian Calaby
2013-01-21  9:11                     ` Aaron Lu
2013-01-21 14:56                       ` Oliver Neukum
2013-01-22  2:25                         ` Aaron Lu
2013-01-22  9:13                           ` Oliver Neukum
2013-01-22  9:20                             ` Aaron Lu
2013-01-21  8:04               ` Aaron Lu
2013-01-21  9:37               ` [RFC PATCH] " Aaron Lu
2013-01-21 16:59                 ` Alan Stern
2013-01-22  2:27                   ` Aaron Lu
2013-01-21 13:36               ` [PATCH v13 1/9] " Aaron Lu
2013-01-15  9:20 ` [PATCH v13 2/9] libata: identify and init ZPODD devices Aaron Lu
2013-01-21  9:16   ` Jeff Garzik
2013-01-21  9:28     ` Aaron Lu
2013-01-15  9:20 ` [PATCH v13 3/9] libata: move acpi notification code to zpodd Aaron Lu
2013-01-15  9:21 ` [PATCH v13 4/9] libata: check zero power ready status for ZPODD Aaron Lu
2013-01-15  9:21 ` [PATCH v13 5/9] libata: handle power transition of ODD Aaron Lu
2013-01-15  9:21 ` [PATCH v13 6/9] libata: expose pm qos flags for ata device Aaron Lu
2013-01-15  9:21 ` [PATCH v13 7/9] libata: scsi: no poll when ODD is powered off Aaron Lu
2013-01-15  9:21 ` [PATCH v13 8/9] libata: do not suspend port if normal ODD is attached Aaron Lu
2013-01-21 20:42   ` Jeff Garzik
2013-01-22 11:27     ` Aaron Lu
2013-01-15  9:21 ` [PATCH v13 9/9] scsi: remove can_power_off flag from scsi_device Aaron Lu

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=Pine.LNX.4.44L0.1301181017070.1988-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=aaron.lu@intel.com \
    --cc=aaron.lwe@gmail.com \
    --cc=jeff.wu@amd.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.