From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759289AbZBZEYS (ORCPT ); Wed, 25 Feb 2009 23:24:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752576AbZBZEYI (ORCPT ); Wed, 25 Feb 2009 23:24:08 -0500 Received: from yw-out-2324.google.com ([74.125.46.31]:59450 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752399AbZBZEYH convert rfc822-to-8bit (ORCPT ); Wed, 25 Feb 2009 23:24:07 -0500 MIME-Version: 1.0 In-Reply-To: References: <200902221837.49396.rjw@sisk.pl> <20090226030050.GA3361@elte.hu> Date: Wed, 25 Feb 2009 20:24:03 -0800 Message-ID: Subject: Re: [RFC][PATCH 2/2] PM: Rework handling of interrupts during suspend-resume From: =?ISO-8859-1?Q?Arve_Hj=F8nnev=E5g?= To: "Eric W. Biederman" Cc: Linus Torvalds , Ingo Molnar , "Rafael J. Wysocki" , LKML , Benjamin Herrenschmidt , Jeremy Fitzhardinge , pm list , Len Brown , Jesse Barnes , Thomas Gleixner Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 25, 2009 at 8:20 PM, Eric W. Biederman wrote: > Arve Hjønnevåg writes: > >> We only have one gpio input driver, but I don't think is good to loose >> any wakeup interrupts. Any driver that needs an edge triggered wakeup >> interrupt will have problems if the hardware does not regenerate the >> interrupt when the host does not respond. > > We are not loosing interrupts.  The normal implementation of disable > is a software disable and sets IRQ_PENDING to ensure we don't loose > interrupts when the interrupt is disabled. We loose the wakeup, but yes, the interrupt will be delivered if the system wakes up for any other reason. -- Arve Hjønnevåg