From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw01.freescale.net (az33egw01.freescale.net [192.88.158.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw01.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id BED3FDDE26 for ; Wed, 12 Sep 2007 07:51:33 +1000 (EST) Message-ID: <46E70DB5.4050500@freescale.com> Date: Tue, 11 Sep 2007 16:50:45 -0500 From: Scott Wood MIME-Version: 1.0 To: Paul Mackerras Subject: Re: [PATCH 2/3] pm: Handle HID0_SLEEP in the TLF_NAPPING hack. References: <20070905220438.GA11283@ld0162-tx32.am.freescale.net> <20070905220638.GA11353@ld0162-tx32.am.freescale.net> <18151.2374.68378.969061@cargo.ozlabs.ibm.com> In-Reply-To: <18151.2374.68378.969061@cargo.ozlabs.ibm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Paul Mackerras wrote: > Scott Wood writes: > >> The e300 core (and probably most other 6xx chips) can only come out of >> sleep mode with an interrupt. However, interrupts are logically disabled >> by the power management layer. >> >> This hack extends the existing doze/nap hack to also suppress the running >> of the interrupt handler when in sleep mode. > > Having thought about this for a bit, I have come to the conclusion > that it would be a lot cleaner to use a new TLF_SLEEPING bit rather > than having to read HID0 to know whether we were napping or sleeping. > There are plenty of bits left in thread_info.local_flags; we've only > used 1 so far. :) OK. -Scott