From: Lin Ming <ming.m.lin@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Zhang Rui <rui.zhang@intel.com>, Jeff Garzik <jgarzik@pobox.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Tejun Heo <tj@kernel.org>,
Aaron Lu <aaron.lu@amd.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org,
SCSI development list <linux-scsi@vger.kernel.org>,
Linux-pm mailing list <linux-pm@vger.kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: [RFC PATCH v2 8/8] [SCSI] sr: check and enable Zero-power ODD support
Date: Fri, 02 Mar 2012 15:02:45 +0800 [thread overview]
Message-ID: <1330671765.3412.7.camel@minggr> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1203011059230.9392-100000@netrider.rowland.org>
On Thu, 2012-03-01 at 11:02 -0500, Alan Stern wrote:
> On Thu, 1 Mar 2012, Lin Ming wrote:
>
> > ZPODD(Zero Power Optical Disk Drive) is a new feature in
> > SATA 3.1 specification. It provides a way to power off unused ODD.
> >
> > ZPODD support is checked in in sr_probe().
> > can_power_off flag is set during suspend if ZPODD is supported.
> >
> > ATA port's runtime suspend callback will actually power off the ODD
> > and its runtime resume callback will actually power on the ODD.
> >
> > When ODD is powered off(D3Cold state), inserting disk will trigger a
> > wakeup event(GPE). GPE AML handler notifies the associated device. Then
> > ODD is resumed in the notify handler.
>
> I have one stylistic comment on this patch...
>
> > diff --git a/drivers/scsi/sr.h b/drivers/scsi/sr.h
> > index 37c8f6b..39b3d8c 100644
> > --- a/drivers/scsi/sr.h
> > +++ b/drivers/scsi/sr.h
> > @@ -42,6 +42,9 @@ typedef struct scsi_cd {
> > unsigned readcd_cdda:1; /* reading audio data using READ_CD */
> > unsigned media_present:1; /* media is present */
> >
> > + unsigned zpodd:1; /* is ZPODD supported */
> > + unsigned zpodd_event:1;
> > +
>
> You should not expect your readers to understand what "ZPODD" means.
> drivers/scsi/sr.h is used by lots of different people, many of whom
> will have no idea what it refers to, especially since it is part of
> the SATA spec and not the SCSI spec. You should provide a brief
> explanation.
I'll add some explanation.
But I'm thinking maybe it's better to move this flag to ata layer, for
example, adding a flag to libata.h
ATA_DFLAG_ZPODD
sr runtime pm is only enabled when ZPODD(or more general, power off) is
supported.
So the problem is how will sr driver know this flag?
>
> Alan Stern
>
next prev parent reply other threads:[~2012-03-02 7:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 9:02 [RFC PATCH v2 0/8] ACPI D3Cold state and SATA ZPODD support Lin Ming
2012-03-01 9:02 ` [RFC PATCH v2 1/8] ACPI: Introduce ACPI D3_COLD state support Lin Ming
2012-03-12 2:00 ` Aaron Lu
2012-03-12 2:00 ` Aaron Lu
2012-03-12 2:43 ` Lin Ming
2012-03-01 9:02 ` [RFC PATCH v2 2/8] ACPI: Add interface to register/unregister device to/from power resources Lin Ming
2012-03-19 1:32 ` Lin Ming
2012-03-01 9:02 ` [RFC PATCH v2 3/8] PCI: Move acpi_dev_run_wake to acpi core Lin Ming
2012-03-01 9:02 ` [RFC PATCH v2 4/8] libata-acpi: set acpi state for SATA port Lin Ming
2012-03-12 2:02 ` Aaron Lu
2012-03-12 2:02 ` Aaron Lu
2012-03-01 9:02 ` [RFC PATCH v2 5/8] libata-acpi: add ata port runtime D3Cold support Lin Ming
2012-03-19 3:36 ` Aaron Lu
2012-03-19 3:36 ` Aaron Lu
2012-03-19 5:27 ` Lin Ming
2012-03-19 6:35 ` Aaron Lu
2012-03-19 6:35 ` Aaron Lu
2012-03-19 7:03 ` Lin Ming
2012-03-21 4:48 ` Aaron Lu
2012-03-21 4:48 ` Aaron Lu
2012-03-01 9:02 ` [RFC PATCH v2 6/8] libata-acpi: register/unregister device to/from power resource Lin Ming
2012-03-01 9:02 ` [RFC PATCH v2 7/8] PM / Runtime: Add can_power_off flag to subsys data Lin Ming
2012-03-19 1:34 ` Lin Ming
2012-03-01 9:02 ` [RFC PATCH v2 8/8] [SCSI] sr: check and enable Zero-power ODD support Lin Ming
2012-03-01 16:02 ` Alan Stern
2012-03-01 16:02 ` Alan Stern
2012-03-02 7:02 ` Lin Ming [this message]
2012-03-02 15:08 ` Aaron Lu
2012-03-03 3:05 ` Lin Ming
2012-03-12 2:49 ` Lin Ming
2012-03-12 4:53 ` Aaron Lu
2012-03-12 4:53 ` 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=1330671765.3412.7.camel@minggr \
--to=ming.m.lin@intel.com \
--cc=aaron.lu@amd.com \
--cc=jgarzik@pobox.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
--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 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.