All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@amd.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <lenb@kernel.org>, Lin Ming <ming.m.lin@intel.com>,
	linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
	Andiry Xu <andiry.xu@amd.com>, Alex He <alex.he@amd.com>
Subject: Re: [PATCH] ACPI: evaluate _PS3 when entering D3 Cold
Date: Mon, 23 Apr 2012 23:13:27 +0800	[thread overview]
Message-ID: <20120423151327.GA4019@fedora> (raw)
In-Reply-To: <201204231343.03382.rjw@sisk.pl>

On Mon, Apr 23, 2012 at 01:43:03PM +0200, Rafael J. Wysocki wrote:
> On Monday, April 23, 2012, Aaron Lu wrote:
> > Hi Rafael and Ming,
> > 
> > Do you have any more comments on this patch?
> > If not, can I have your ack? Thanks.
> > 
> > -Aaron
> > 
> > On Sun, Apr 01, 2012 at 02:18:30AM +0800, Aaron Lu wrote:
> > > When entering D3 Cold from a higher device state, evaluate _PS3 first
> > > and then make the proper power transition.
> > > This is used to solve the ZPODD problem on AMD's platform, _PS3 on such
> > > platforms will power off the ODD device and thus make the device enter
> > > D3 cold state.
> > > 
> > > Signed-off-by: Aaron Lu <aaron.lu@amd.com>
> > > Cc: Andiry Xu <andiry.xu@amd.com>
> > > Cc: Alex He <alex.he@amd.com>
> > > ---
> > >  drivers/acpi/bus.c |   17 ++++++++++++++---
> > >  1 file changed, 14 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
> > > index 3263b68..68e593f 100644
> > > --- a/drivers/acpi/bus.c
> > > +++ b/drivers/acpi/bus.c
> > > @@ -227,6 +227,8 @@ static int __acpi_bus_set_power(struct acpi_device *device, int state)
> > >  	int result = 0;
> > >  	acpi_status status = AE_OK;
> > >  	char object_name[5] = { '_', 'P', 'S', '0' + state, '\0' };
> > > +	struct acpi_device_power_state *ps;
> > > +	u8 explicit_set;
> > >  
> > >  	if (!device || (state < ACPI_STATE_D0) || (state > ACPI_STATE_D3_COLD))
> > >  		return -EINVAL;
> > > @@ -239,7 +241,8 @@ static int __acpi_bus_set_power(struct acpi_device *device, int state)
> > >  		return 0;
> > >  	}
> > >  
> > > -	if (!device->power.states[state].flags.valid) {
> > > +	ps = &device->power.states[state];
> > > +	if (!ps->flags.valid) {
> > >  		printk(KERN_WARNING PREFIX "Device does not support D%d\n", state);
> > >  		return -ENODEV;
> > >  	}
> > > @@ -263,7 +266,7 @@ static int __acpi_bus_set_power(struct acpi_device *device, int state)
> > >  			if (result)
> > >  				goto end;
> > >  		}
> > > -		if (device->power.states[state].flags.explicit_set) {
> > > +		if (ps->flags.explicit_set) {
> > >  			status = acpi_evaluate_object(device->handle,
> > >  						      object_name, NULL, NULL);
> > >  			if (ACPI_FAILURE(status)) {
> > > @@ -272,7 +275,15 @@ static int __acpi_bus_set_power(struct acpi_device *device, int state)
> > >  			}
> > >  		}
> > >  	} else {
> > > -		if (device->power.states[state].flags.explicit_set) {
> > > +		/* If state is D3 Cold, try to evaluate _PS3 first */
> > > +		if (state == ACPI_STATE_D3_COLD) {
> > > +			explicit_set = (ps - 1)->flags.explicit_set;
> > > +			object_name[3] -= 1;
> > > +		}
> > > +		else {
> > > +			explicit_set = ps->flags.explicit_set;
> > > +		}
> 
> I really don't like this.  I think you should modify acpi_bus_get_power_flags(),
> on top of the recent Lin Ming's patch, so that it sets flags.explicit_set for
> D3_COLD if _PS3 is present and _PR3 is not.
> 

Thanks for your comments.

> I'm not sure you'll need the $subject patch any more then.
> 

A little change is still required. I attached the code below.
BTW, I think _PS3 will also need be executed if both _PS3 and _PR3
available when putting a device into D3cold.

diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index 3263b68..187433f 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -273,6 +273,9 @@ static int __acpi_bus_set_power(struct acpi_device *device, int state)
 		}
 	} else {
 		if (device->power.states[state].flags.explicit_set) {
+			/* evaluate _PS3 instead of _PS4 when entering D3Cold */
+			if (state == ACPI_STATE_D3)
+				object_name[3] -= 1;
 			status = acpi_evaluate_object(device->handle,
 						      object_name, NULL, NULL);
 			if (ACPI_FAILURE(status)) {
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index 7417267..de2ae10 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -887,8 +887,12 @@ static int acpi_bus_get_power_flags(struct acpi_device *device)
 		/* Evaluate "_PSx" to see if we can do explicit sets */
 		object_name[2] = 'S';
 		status = acpi_get_handle(device->handle, object_name, &handle);
-		if (ACPI_SUCCESS(status))
+		if (ACPI_SUCCESS(status)) {
 			ps->flags.explicit_set = 1;
+			/* Also set D3Cold's explicit flag when _PS3 exists */
+			if (i == ACPI_STATE_D3_HOT)
+				(ps+1)->flags.explicit_set = 1;
+		}
 
 		/*
 		 * State is valid if there are means to put the device into it.


Do you like this?

Thanks,
Aaron

> > > +		if (explicit_set) {
> > >  			status = acpi_evaluate_object(device->handle,
> > >  						      object_name, NULL, NULL);
> > >  			if (ACPI_FAILURE(status)) {
> 
> Thanks,
> Rafael
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-04-23 15:13 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31 18:18 [PATCH] ACPI: evaluate _PS3 when entering D3 Cold Aaron Lu
2012-03-31 18:18 ` Aaron Lu
2012-04-01  5:27 ` Lin Ming
2012-04-01  5:56   ` Aaron Lu
2012-04-01  5:56     ` Aaron Lu
2012-04-01  6:28     ` Lin Ming
2012-04-01  6:28       ` Lin Ming
2012-04-01  7:23       ` Rafael J. Wysocki
2012-04-01  7:23         ` Rafael J. Wysocki
2012-04-01  7:45         ` Zhang Rui
2012-04-01  7:45           ` Zhang Rui
2012-04-01  8:49           ` Rafael J. Wysocki
2012-04-01  8:49             ` Rafael J. Wysocki
2012-04-05  3:20             ` huang ying
2012-04-05  3:20               ` huang ying
2012-04-08 23:41               ` Rafael J. Wysocki
2012-04-08 23:41                 ` Rafael J. Wysocki
2012-04-09  2:24                 ` Huang Ying
2012-04-09 21:24                   ` Rafael J. Wysocki
2012-04-05  2:31         ` Lin Ming
2012-04-05  2:31           ` Lin Ming
2012-04-05  2:56           ` Aaron Lu
2012-04-05  2:56             ` Aaron Lu
2012-04-05  3:01             ` Lin Ming
2012-04-08 23:54               ` Rafael J. Wysocki
2012-04-09  1:38                 ` Lin Ming
2012-04-09 21:25                   ` Rafael J. Wysocki
2012-04-08 23:53             ` Rafael J. Wysocki
2012-04-08 23:47           ` Rafael J. Wysocki
2012-04-08 23:47             ` Rafael J. Wysocki
2012-04-05  2:38         ` Lin Ming
2012-04-05  2:38           ` Lin Ming
2012-04-09  0:02           ` Rafael J. Wysocki
2012-04-09  0:02             ` Rafael J. Wysocki
2012-04-01 14:41       ` Aaron Lu
2012-04-01 14:41         ` Aaron Lu
2012-04-01  7:03     ` Zhang Rui
2012-04-01  7:03       ` Zhang Rui
2012-04-01  7:29       ` Rafael J. Wysocki
2012-04-01 15:34       ` Aaron Lu
2012-04-01 15:34         ` Aaron Lu
2012-04-01  7:47         ` Rafael J. Wysocki
2012-04-01  7:47           ` Rafael J. Wysocki
2012-04-01  8:01           ` Zhang Rui
2012-04-01  8:55             ` Rafael J. Wysocki
2012-04-01  8:55               ` Rafael J. Wysocki
2012-04-23  1:09 ` Aaron Lu
2012-04-23  1:09   ` Aaron Lu
2012-04-23 11:43   ` Rafael J. Wysocki
2012-04-23 15:13     ` Aaron Lu [this message]
2012-04-23 19:50       ` Rafael J. Wysocki
2012-04-24  2:07         ` Aaron Lu
2012-04-24  2:07           ` Aaron Lu
2012-04-24  2:29           ` Lin Ming
2012-04-24  3:10             ` Aaron Lu
2012-04-24  3:10               ` Aaron Lu
2012-04-24 13:15               ` Lin Ming
2012-04-24 14:24                 ` Aaron Lu
2012-04-24 21:15                   ` Rafael J. Wysocki
2012-04-26  8:55                     ` huang ying
2012-04-26 20:04                       ` Rafael J. Wysocki

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=20120423151327.GA4019@fedora \
    --to=aaron.lu@amd.com \
    --cc=alex.he@amd.com \
    --cc=andiry.xu@amd.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.com \
    /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.