[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1204051000450.1361-100000@iolanthe.rowland.org>
Date: Thu, 5 Apr 2012 10:03:05 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Aaron Lu <aaron.lu@....com>
cc: Lin Ming <ming.m.lin@...el.com>, Zhang Rui <rui.zhang@...el.com>,
Jeff Garzik <jgarzik@...ox.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Tejun Heo <tj@...nel.org>,
<linux-kernel@...r.kernel.org>, <linux-ide@...r.kernel.org>,
<linux-scsi@...r.kernel.org>, <linux-pm@...r.kernel.org>,
linux-acpi <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH v3 7/7] [SCSI] sr: adds Zero-power ODD support
On Thu, 5 Apr 2012, Aaron Lu wrote:
> Hi,
>
> On Thu, Apr 05, 2012 at 02:00:57PM +0800, Lin Ming wrote:
> > >
> > > Another thing to consider is, user might want to eject the tray by
> > > software like the
> > > eject /dev/sr0 command or some UI mouse clicks against the cdrom icon. I'm still
> > > thinking how to do this correctly.
> >
> > Assume eject /dev/sr0 is implemented as:
> >
> > int fd = open("/dev/sr0", ...)
> > ioctl(fd, CDROMEJECT)
> >
>
> Indeed, it is implemented as this :-)
>
> > We may need to resume ODD in the ioctl handler(scsi_cmd_ioctl).
> >
>
> I prefer we do this in sr_block_ioctl.
> Suppose the ODD is now runtime suspended and received an ioctl:
> if the ioctl's cmd is CDROMEJECT, resume it.
> For other cases, return an error code like EPERM.
> When done, according to the result of ioctl: if success, leave it resumed;
> if failed, put it back to sleep.
Alternatively, you may want to do the runtime resume in sr_open and
sr_block_open and the suspend in the corresponding release routines.
It's up to you.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists