From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH] ACPI: evaluate _PS3 when entering D3 Cold Date: Mon, 9 Apr 2012 01:47:36 +0200 Message-ID: <201204090147.36529.rjw@sisk.pl> References: <1333217910-29579-1-git-send-email-aaron.lu@amd.com> <201204010923.18330.rjw@sisk.pl> <1333593080.11327.22.camel@minggr> Mime-Version: 1.0 Content-Type: Text/Plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:59181 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752387Ab2DHXnK convert rfc822-to-8bit (ORCPT ); Sun, 8 Apr 2012 19:43:10 -0400 In-Reply-To: <1333593080.11327.22.camel@minggr> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Lin Ming Cc: Aaron Lu , Len Brown , linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Zhang Rui , Andiry Xu , Alex He On Thursday, April 05, 2012, Lin Ming wrote: > On Sun, 2012-04-01 at 09:23 +0200, Rafael J. Wysocki wrote: > > Hi, > >=20 > > Sorry for the delayed response, I've been travelling recently. > >=20 > > On Sunday, April 01, 2012, Lin Ming wrote: > > > On Sun, 2012-04-01 at 13:56 +0800, Aaron Lu wrote: > > > > Hi, > > > >=20 > > > > On Sun, Apr 01, 2012 at 01:27:33PM +0800, Lin Ming wrote: > > > > > > - if (device->power.states[state].flags.explicit_set) { > > > > > > + /* If state is D3 Cold, try to evaluate _PS3 first */ > > > > > > + if (state =3D=3D ACPI_STATE_D3_COLD) { > > > > > > + explicit_set =3D (ps - 1)->flags.explicit_set; > > > > > > + object_name[3] -=3D 1; > > > > > > + } > > > > >=20 > > > > > I'm not sure whether this works or not. > > > > >=20 > > > > > From ACPI spec, > > > > >=20 > > > > > _PS3 "is used to put the specific device into its D3hot or D3= state" > > > > >=20 > > > > > D3 neither means D3hot nor D3cold. It's an old term before D3= hot and > > > > > D3cold were introduced. > > > > I guess D3 has to mean something, right? :-) > >=20 > > Well, not necessarily. > >=20 > > The problem is what state the _PS3 method puts the device into: D3_= hot or > > D3_cold. > >=20 > > Unfortunately, as far as I can say, ACPI 4.0 didn't specify any "of= ficial" > > mapping between the "old" D3 and the "new" D3_{hod|cold} states, so= we need to > > figure out something. In my opinion, the only reasonable approach = is to > > assume that the state _PS3 puts the device into is always D3_cold, = becuase > > _PS3 may remove power completely from the device. It may not do th= at, but > > we _must_ assume it does that in general. > >=20 > > > > Here is the problem, there is no _PR3 in AMD's implementation, = just _PS3. > > > > And since _S0W evaluates 4, I've to put this device into D3 col= d state > > > > with _PS3. > > > >=20 > > > > And the ACPI does have some words like: > > > >=20 > > > > ------ > > > > Platform/drivers must assume that the device will have power co= mpletely > > > > removed when the device is place into =E2=80=9CD3=E2=80=9D via = _PS3 > >=20 > > Exactly. What it means is basically "always reinitialize the devic= e from > > scratch if you have run _PS3 on it". And that's what we should do. > >=20 > > > > ------ > > > >=20 > > > > This is in section 7.2.11: _PR3. > > > >=20 > > > > >=20 > > > > > Another problem: > > > > >=20 > > > > > With your patch, both D3hot and D3cold will evaluate _PS3, ri= ght? > > > > >=20 > > > > Yes. > > > >=20 > > > > > Will it have problem on AMD platform if you try to put ODD in= to D3hot > > > > > state? _PS3 is evaluated, so it actually enters D3Cold state. > > > >=20 > > > > There is no D3 hot support for this device(from the firmware's > > > > perspective), either it is at D0(via _PS0), or it will be at D3= cold(via > > > > _PS3). > > >=20 > > > But this is the generic code. We can't only consider some special > > > device. > > >=20 > > > Maybe we need some flag to tell which D3 state _PS3 is used for. > >=20 > > No, please. As I said above, we need to reinitialize devices that = _PS3 was > > executed on, which is equivalent to saying that those devices were = put into > > D3_cold. > >=20 > > The only situation where a device can be put into ACPI D3_hot (whic= h is not > > the same as PCI D3_hot, mind you) is when: > >=20 > > (1) There is _PR3 listing some of the device's power resources as "= on". > > (2) The power resources listed by the _PR3 as "off" are turned off = and the > > power resources listed by the _PR3 as "on" are left in the "on"= state. >=20 > I don't understand item (2): >=20 > If the power resource is listed as "off", which means it's already > turned off. Then why should it be turned off again? Sorry, there are two lists. One of them is returned by _PR0 (these are needed to put the device into D0) and the second is returned by _PR3 (if that exists) and these need to be "on" for the device to stay in D3_hot (if they are "off", the device will go into D3_cold instead). Actually, section 7.2.11 of ACPI 5.0 is quite clear in that respect. > Let's see an example >=20 > Assume a device "dev0" depends on 5 power resources: >=20 > pr1, pr2, pr3, pr4, pr5 >=20 > _PR3 lists 3 power resources: pr3, pr4, pr5 >=20 > Device(dev0) > { > Name(_PR3, Package (0x03) > { > pr3, > pr4, > pr5 > }) > } >=20 > If dev0 is put into ACPI D3_hot and pr1 and pr2 are not referenced by > other devices, then it requires: >=20 > - pr1 and pr2 are off > - pr3, pr4 and pr5 are on >=20 > right? That's correct. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html