Question about e300 core decrementer interrupt

From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 898A3B7087 for ; Tue, 8 Sep 2009 15:48:07 +1000 (EST) Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 1E58FDDD04 for ; Tue, 8 Sep 2009 15:48:06 +1000 (EST) Received: from az33smr01.freescale.net (az33smr01.freescale.net [10.64.34.199]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id n885m2KJ008273 for ; Mon, 7 Sep 2009 22:48:03 -0700 (MST) Received: from zmy16exm21.fsl.freescale.net (zmy16exm21.ap.freescale.net [10.211.3.25]) by az33smr01.freescale.net (8.13.1/8.13.0) with ESMTP id n885nQCJ004146 for ; Tue, 8 Sep 2009 00:49:27 -0500 (CDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA3047.ECE8C01B" Subject: Question about e300 core decrementer interrupt Date: Tue, 8 Sep 2009 13:48:00 +0800 Message-ID: From: "Li Tao-B22598" To: List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01CA3047.ECE8C01B Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: quoted-printable Dear all, I have a problem in MPC5121 sleep mode. As you know MPC5121 use e300c4 core. When I make the e300c4 core into sleep mode, it will return to full power mode when the=A1=B0decrementer interrupt=A1=B1 occurred. But in the e300 core reference manual said that the =A1=B0decrementer interrupt=A1=B1have no effect when e300 core in sleep mode, because the = time base and decrementer are disabled while the core is in sleep mode. Can anybody explain about this procedure ?=20 Another question is how can I disable the=A1=B0decrementer = interrupt=A1=B1without disable int,smi, or mcpinternal signals. Any help or suggestion would be very helpful. Thank you for your time. --=20 Best Regards, =20 Li Tao =20 ------_=_NextPart_001_01CA3047.ECE8C01B Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: quoted-printable Question about e300 core decrementer interrupt

Dear all,

I have a problem in MPC5121 sleep mode. As you know MPC5121 use = e300c4
core. When I make the e300c4 core into sleep mode, it will return to
full power mode when the=A1=B0decrementer interrupt=A1=B1 occurred.

But in the e300 core reference manual said that the = =A1=B0decrementer
interrupt=A1=B1have no effect when e300 core in sleep mode, because the = time
base and decrementer are disabled while the core is in sleep mode.
Can anybody explain about this procedure ?

Another question is how can I disable the=A1=B0decrementer = interrupt=A1=B1without
disable int,smi, or mcpinternal signals.

Any help or suggestion would be very helpful.
Thank you for your time.

--
Best Regards,

Li Tao

------_=_NextPart_001_01CA3047.ECE8C01B-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 014BEB6F1E for ; Wed, 9 Sep 2009 21:16:22 +1000 (EST) Received: from mail.southpole.se (mail.southpole.se [193.12.106.18]) by ozlabs.org (Postfix) with ESMTP id C3910DDD04 for ; Wed, 9 Sep 2009 21:16:18 +1000 (EST) Subject: Re: Question about e300 core decrementer interrupt From: Kenneth Johansson To: Li Tao-B22598 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Wed, 09 Sep 2009 13:16:07 +0200 Message-Id: <1252494967.10293.6.camel@localhost> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2009-09-08 at 13:48 +0800, Li Tao-B22598 wrote: > Dear all, > > I have a problem in MPC5121 sleep mode. As you know MPC5121 use e300c4 > core. When I make the e300c4 core into sleep mode, it will return to > full power mode when the“decrementer interrupt” occurred. > > But in the e300 core reference manual said that the “decrementer > interrupt”have no effect when e300 core in sleep mode, because the > time > base and decrementer are disabled while the core is in sleep mode. > Can anybody explain about this procedure ? Please talk to people internal to freescale. There is errata on this that is known for a long time(more than a year now) that for some reason is never entered into the errata document. I'm a bit irritated that it's not as the "solution" can mean hardware changes an thus it's potentially expensive. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 086E6B6F31 for ; Thu, 10 Sep 2009 04:43:48 +1000 (EST) Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 7EE19DDD01 for ; Thu, 10 Sep 2009 04:43:46 +1000 (EST) Received: from az33smr01.freescale.net (az33smr01.freescale.net [10.64.34.199]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id n89IhhJN024057 for ; Wed, 9 Sep 2009 11:43:43 -0700 (MST) Received: from b07421-ec1.am.freescale.net (b07421-ec1.am.freescale.net [10.82.121.43]) by az33smr01.freescale.net (8.13.1/8.13.0) with ESMTP id n89IjAkd001026 for ; Wed, 9 Sep 2009 13:45:10 -0500 (CDT) Date: Wed, 9 Sep 2009 13:43:43 -0500 From: Scott Wood To: Kenneth Johansson Subject: Re: Question about e300 core decrementer interrupt Message-ID: <20090909184343.GC8215@b07421-ec1.am.freescale.net> References: <1252494967.10293.6.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <1252494967.10293.6.camel@localhost> Cc: linuxppc-dev@ozlabs.org, Li Tao-B22598 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Sep 09, 2009 at 01:16:07PM +0200, Kenneth Johansson wrote: > On Tue, 2009-09-08 at 13:48 +0800, Li Tao-B22598 wrote: > > Dear all, > > > > I have a problem in MPC5121 sleep mode. As you know MPC5121 use e300c4 > > core. When I make the e300c4 core into sleep mode, it will return to > > full power mode when the“decrementer interrupt” occurred. > > > > But in the e300 core reference manual said that the “decrementer > > interrupt”have no effect when e300 core in sleep mode, because the > > time > > base and decrementer are disabled while the core is in sleep mode. > > Can anybody explain about this procedure ? I'm not specifically familiar with MPC5121, but I'll answer from the perspective of MPC83xx which has a similar core: The decrementer stops ticking when the core goes to sleep. However, if a decrementer was already pending (but masked with MSR[EE]) before you enter sleep mode, it will cause a wakeup. To avoid this, the decrementer is set to a very large value prior to and after disabling interrupts. See generic_suspend_disable_irqs() in arch/powerpc/kernel/time.c. Is this not happening for you? Which kernel version are you using, and what mechanism are you using to go to sleep? > I'm a bit irritated that it's not as the "solution" can mean hardware > changes an thus it's potentially expensive. What sort of hardware changes? -Scott From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 7972FB6F20 for ; Thu, 10 Sep 2009 19:09:58 +1000 (EST) Received: from mail.southpole.se (mail.southpole.se [193.12.106.18]) by ozlabs.org (Postfix) with ESMTP id 12CD5DDD04 for ; Thu, 10 Sep 2009 19:09:58 +1000 (EST) Subject: Re: Question about e300 core decrementer interrupt From: Kenneth Johansson To: Scott Wood In-Reply-To: <20090909184343.GC8215@b07421-ec1.am.freescale.net> References: <1252494967.10293.6.camel@localhost> <20090909184343.GC8215@b07421-ec1.am.freescale.net> Content-Type: text/plain; charset="UTF-8" Date: Thu, 10 Sep 2009 11:09:54 +0200 Message-Id: <1252573794.10293.13.camel@localhost> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, Li Tao-B22598 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2009-09-09 at 13:43 -0500, Scott Wood wrote: > On Wed, Sep 09, 2009 at 01:16:07PM +0200, Kenneth Johansson wrote: > > On Tue, 2009-09-08 at 13:48 +0800, Li Tao-B22598 wrote: > > > Dear all, > > > > > > I have a problem in MPC5121 sleep mode. As you know MPC5121 use e300c4 > > > core. When I make the e300c4 core into sleep mode, it will return to > > > full power mode when the“decrementer interrupt” occurred. > > > > > > But in the e300 core reference manual said that the “decrementer > > > interrupt”have no effect when e300 core in sleep mode, because the > > > time > > > base and decrementer are disabled while the core is in sleep mode. > > > Can anybody explain about this procedure ? > > I'm not specifically familiar with MPC5121, but I'll answer from the > perspective of MPC83xx which has a similar core: > > The decrementer stops ticking when the core goes to sleep. However, if a > decrementer was already pending (but masked with MSR[EE]) before you > enter sleep mode, it will cause a wakeup. > > To avoid this, the decrementer is set to a very large value prior to and > after disabling interrupts. See generic_suspend_disable_irqs() in > arch/powerpc/kernel/time.c. Is this not happening for you? Which kernel > version are you using, and what mechanism are you using to go to sleep? > > > I'm a bit irritated that it's not as the "solution" can mean hardware > > changes an thus it's potentially expensive. > > What sort of hardware changes? I don't want to spread missinformation but this procedure has helped on the ads5121 rev3 and two custom boards. the gpio 28,29,30 needs to be low and gpio31 needs to be hi. regardless of what is used as wakeup source when the device enters deep sleep otherwise you end up in some sort of meta state where you might not wake up on anything and you have this 42 second auto wakeup from the decrementer. Other weired states has also been observed. the PMC module is a bit tempremental in this chip. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 788EEB7B60 for ; Thu, 10 Sep 2009 21:50:43 +1000 (EST) Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id EC93FDDD01 for ; Thu, 10 Sep 2009 21:50:42 +1000 (EST) Received: from de01smr02.am.mot.com (de01smr02.freescale.net [10.208.0.151]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id n8ABocrk001270 for ; Thu, 10 Sep 2009 04:50:38 -0700 (MST) Received: from zmy16exm21.fsl.freescale.net (zmy16exm21.ap.freescale.net [10.211.3.25]) by de01smr02.am.mot.com (8.13.1/8.13.0) with ESMTP id n8ABqMuV012010 for ; Thu, 10 Sep 2009 06:52:23 -0500 (CDT) Subject: Re: Question about e300 core decrementer interrupt From: Li Tao To: Kenneth Johansson In-Reply-To: <1252573794.10293.13.camel@localhost> References: <1252494967.10293.6.camel@localhost> <20090909184343.GC8215@b07421-ec1.am.freescale.net> <1252573794.10293.13.camel@localhost> Content-Type: text/plain; charset="UTF-8" Date: Thu, 10 Sep 2009 19:53:17 +0800 Message-Id: <1252583597.26108.17.camel@ubuntu.ubuntu-domain> Mime-Version: 1.0 Cc: Scott Wood , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Johansson, Thanks for your response =E5=9C=A8 2009-09-10=E5=9B=9B=E7=9A=84 11:09 +0200=EF=BC=8CKenneth Johansso= n=E5=86=99=E9=81=93=EF=BC=9A > On Wed, 2009-09-09 at 13:43 -0500, Scott Wood wrote: > > On Wed, Sep 09, 2009 at 01:16:07PM +0200, Kenneth Johansson wrote: > > > On Tue, 2009-09-08 at 13:48 +0800, Li Tao-B22598 wrote: > > > > Dear all, > > > >=20 > > > > I have a problem in MPC5121 sleep mode. As you know MPC5121 use e30= 0c4 > > > > core. When I make the e300c4 core into sleep mode, it will return t= o > > > > full power mode when the=E2=80=9Cdecrementer interrupt=E2=80=9D occ= urred. > > > >=20 > > > > But in the e300 core reference manual said that the =E2=80=9Cdecrem= enter > > > > interrupt=E2=80=9Dhave no effect when e300 core in sleep mode, beca= use the > > > > time > > > > base and decrementer are disabled while the core is in sleep mode. > > > > Can anybody explain about this procedure ? > >=20 > > I'm not specifically familiar with MPC5121, but I'll answer from the > > perspective of MPC83xx which has a similar core: > >=20 > > The decrementer stops ticking when the core goes to sleep. However, if= a > > decrementer was already pending (but masked with MSR[EE]) before you > > enter sleep mode, it will cause a wakeup. > >=20 > > To avoid this, the decrementer is set to a very large value prior to an= d > > after disabling interrupts. See generic_suspend_disable_irqs() in > > arch/powerpc/kernel/time.c. Is this not happening for you? Which kern= el > > version are you using, and what mechanism are you using to go to sleep?= =20 > >=20 > > > I'm a bit irritated that it's not as the "solution" can mean hardware > > > changes an thus it's potentially expensive. > >=20 > > What sort of hardware changes? >=20 > I don't want to spread missinformation but this procedure has helped on > the ads5121 rev3 and two custom boards.=20 >=20 > the gpio 28,29,30 needs to be low and gpio31 needs to be hi. regardless > of what is used as wakeup source when the device enters deep sleep > otherwise you end up in some sort of meta state where you might not wake > up on anything and you have this 42 second auto wakeup from the > decrementer.=20 I use ads5121 rev4.1 board, the gpio 28,29,30 is low and gpio31 is high. I find that the RTC is fail too, when I use hwclock -f /dev/rtc0 cmd, it was always "Wed Dec 31 23:59:59 1969 0.000000 seconds". I measured the the RTC oscillator is 32.768 kHz, and the VBAT_RTC is 4.2v. I have no idea about why RTC is fail.=20 >=20 > Other weired states has also been observed. the PMC module is a bit > tempremental in this chip. >=20 >=20 >=20 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 8677EB7B3E for ; Thu, 10 Sep 2009 21:56:14 +1000 (EST) Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id DF54CDDD04 for ; Thu, 10 Sep 2009 21:56:13 +1000 (EST) Received: from az33smr01.freescale.net (az33smr01.freescale.net [10.64.34.199]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id n8ABu08h002336 for ; Thu, 10 Sep 2009 04:56:10 -0700 (MST) Received: from zmy16exm21.fsl.freescale.net (zmy16exm21.ap.freescale.net [10.211.3.25]) by az33smr01.freescale.net (8.13.1/8.13.0) with ESMTP id n8ABvRZ5013317 for ; Thu, 10 Sep 2009 06:57:28 -0500 (CDT) Subject: Re: Question about e300 core decrementer interrupt From: Li Tao To: Scott Wood In-Reply-To: <20090909184343.GC8215@b07421-ec1.am.freescale.net> References: <1252494967.10293.6.camel@localhost> <20090909184343.GC8215@b07421-ec1.am.freescale.net> Content-Type: text/plain; charset="UTF-8" Date: Thu, 10 Sep 2009 19:58:42 +0800 Message-Id: <1252583922.26108.23.camel@ubuntu.ubuntu-domain> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, Kenneth Johansson List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Scott Wood, Thanks for your response =E5=9C=A8 2009-09-09=E4=B8=89=E7=9A=84 13:43 -0500=EF=BC=8CScott Wood=E5=86= =99=E9=81=93=EF=BC=9A > On Wed, Sep 09, 2009 at 01:16:07PM +0200, Kenneth Johansson wrote: > > On Tue, 2009-09-08 at 13:48 +0800, Li Tao-B22598 wrote: > > > Dear all, > > >=20 > > > I have a problem in MPC5121 sleep mode. As you know MPC5121 use e300c= 4 > > > core. When I make the e300c4 core into sleep mode, it will return to > > > full power mode when the=E2=80=9Cdecrementer interrupt=E2=80=9D occur= red. > > >=20 > > > But in the e300 core reference manual said that the =E2=80=9Cdecremen= ter > > > interrupt=E2=80=9Dhave no effect when e300 core in sleep mode, becaus= e the > > > time > > > base and decrementer are disabled while the core is in sleep mode. > > > Can anybody explain about this procedure ? >=20 > I'm not specifically familiar with MPC5121, but I'll answer from the > perspective of MPC83xx which has a similar core: >=20 > The decrementer stops ticking when the core goes to sleep. However, if a > decrementer was already pending (but masked with MSR[EE]) before you > enter sleep mode, it will cause a wakeup. >=20 > To avoid this, the decrementer is set to a very large value prior to and > after disabling interrupts. See generic_suspend_disable_irqs() in > arch/powerpc/kernel/time.c. Is this not happening for you? Which kernel > version are you using, and what mechanism are you using to go to sleep? I use 2.6.24 kernel. The PM driver code have set decrementer to 0x7fffffff before go to sleep mode. The driver set HID0[10]=3D1, then set MSR POW bit. PMCCR =3D 00111. > =20 >=20 > > I'm a bit irritated that it's not as the "solution" can mean hardware > > changes an thus it's potentially expensive. >=20 > What sort of hardware changes? >=20 > -Scott From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 50079B6F56 for ; Fri, 11 Sep 2009 01:29:59 +1000 (EST) Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 923E8DDD01 for ; Fri, 11 Sep 2009 01:29:51 +1000 (EST) Received: from de01smr02.am.mot.com (de01smr02.freescale.net [10.208.0.151]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id n8AFTmRO018099 for ; Thu, 10 Sep 2009 08:29:48 -0700 (MST) Received: from az33exm25.fsl.freescale.net (az33exm25.am.freescale.net [10.64.32.16]) by de01smr02.am.mot.com (8.13.1/8.13.0) with ESMTP id n8AFVZVt022245 for ; Thu, 10 Sep 2009 10:31:35 -0500 (CDT) Message-ID: <4AA91B86.7090805@freescale.com> Date: Thu, 10 Sep 2009 10:30:14 -0500 From: Scott Wood MIME-Version: 1.0 To: Li Tao Subject: Re: Question about e300 core decrementer interrupt References: <1252494967.10293.6.camel@localhost> <20090909184343.GC8215@b07421-ec1.am.freescale.net> <1252583922.26108.23.camel@ubuntu.ubuntu-domain> In-Reply-To: <1252583922.26108.23.camel@ubuntu.ubuntu-domain> Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org, Kenneth Johansson List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Li Tao wrote: > Hi Scott Wood, > Thanks for your response > > 在 2009-09-09三的 13:43 -0500，Scott Wood写道： >> The decrementer stops ticking when the core goes to sleep. However, if a >> decrementer was already pending (but masked with MSR[EE]) before you >> enter sleep mode, it will cause a wakeup. >> >> To avoid this, the decrementer is set to a very large value prior to and >> after disabling interrupts. See generic_suspend_disable_irqs() in >> arch/powerpc/kernel/time.c. Is this not happening for you? Which kernel >> version are you using, and what mechanism are you using to go to sleep? > I use 2.6.24 kernel. The PM driver code have set decrementer to > 0x7fffffff before go to sleep mode. It looks like 2.6.24 doesn't have commit 7ac5dde99eb9fefdb526973c600075b7c5703a86 (Implement arch disable/enable irq hooks) -- are you disabling the decrementer in a similar manner, or is it possible that the decrementer has already fired by the time you set it to 0x7fffffff? Could you read the value just prior to entering sleep? Why use such an old kernel, BTW? > The driver set HID0[10]=1, then set MSR POW bit. PMCCR = 00111. I was more interested in whether you were using the suspend_ops (maybe pm_ops back then?) infrastructure (which would invoke the irq hooks) or something custom. -Scott