From: Aaron Lu <aaron.lu@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oneukum@suse.de>,
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: Mon, 21 Jan 2013 16:04:17 +0800 [thread overview]
Message-ID: <20130121080417.GA6904@aaronlu.sh.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1301191312050.13032-100000@netrider.rowland.org>
On Sat, Jan 19, 2013 at 01:46:15PM -0500, Alan Stern wrote:
> On Sat, 19 Jan 2013, Aaron Lu wrote:
>
> > > 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.
> >
> > Tried on my notebook with a normal ODD, using mplayer under console
> > mode, no GUI environment running, works fine.
> >
> > The usage count will be incremented by the app, and get decreased
> > only when it exits. So the ODD will not be in runtime suspended state
> > when the app is running.
>
> You missed my point. What happens when sr_open() gets called? It
> doesn't try to resume the device. Will we run into trouble then?
Oh yes, you mean the cdo->open gets called without going through sr's
block interface.
I just checked the code, it looks to me the cdrom interface code is the
code common to cdrom functionality, to be used by various underlying
block drivers like sr, ide-cd, etc. All the code cdrom.c has provided
requires a cdi parameter, which can only be provided by the underlying
block driver, so I don't think those cdrom_device_ops functions will be
called without going through the block drivers' interface.
But the functions defined in block_device_operations by sr can be called
by other kernel components as long as they have access to the gendisk
structure of the block device, so I'll add get/sync pair to all those
functions(i.e. sr_block_revalidate_disk, sr_block_ioctl in addition to
the open/release/check_events calls).
>
> > > 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
> >
> > Then we indeed have a problem. But I didn't find any such app in
> > Fedora's repo or by searching the internet.
>
> http://rpm.pbone.net/index.php3/stat/4/idpl/2392183/dir/redhat_5.x/com/cdp-0.33-10.i386.rpm.html
>
> > > closed. Do we want to drop support for that kind of behavior?
> >
> > I don't think we should drop such support.
> > And the safest way to avoid such break is we refine the suspend
> > condition for ODD, and using what ZPODD defined condition isn't that
> > bad to me:
> > - for tray type, no media inside and tray close;
> > - for slot type, no media inside.
> > While whether tray is closed or not may not be that important, but at
> > least we should make sure there is no media inside.
> >
> > Thoughts?
>
> That sounds reasonable to me, at least as a first step. If people want
> their CD drive to suspend, they can eject the disc.
I'm gonna add the cd->media_present check in sr's runtime suspend
callback, if sr thinks there is media inside, suspend will not proceed.
Thanks,
Aaron
next prev parent reply other threads:[~2013-01-21 8:04 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
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 [this message]
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=20130121080417.GA6904@aaronlu.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=James.Bottomley@HansenPartnership.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=oneukum@suse.de \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--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 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).