From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935970Ab3DJJNk (ORCPT ); Wed, 10 Apr 2013 05:13:40 -0400 Received: from mga02.intel.com ([134.134.136.20]:13520 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750797Ab3DJJNh (ORCPT ); Wed, 10 Apr 2013 05:13:37 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,444,1363158000"; d="scan'208";a="292821198" Date: Wed, 10 Apr 2013 12:17:47 +0300 From: Mika Westerberg To: Mathias Nyman Cc: "Rafael J. Wysocki" , Linus Walleij , grant.likely@secretlab.ca, ACPI Devel Maling List , LKML Subject: Re: [PATCH] gpio / ACPI: Handle ACPI events in accordance with the spec Message-ID: <20130410091747.GO21818@intel.com> References: <3043137.BtEKcMiXSu@vostro.rjw.lan> <20130410075319.GN21818@intel.com> <51652035.5000802@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51652035.5000802@linux.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 10, 2013 at 11:17:57AM +0300, Mathias Nyman wrote: > On 04/10/2013 10:53 AM, Mika Westerberg wrote: > >On Tue, Apr 09, 2013 at 03:57:25PM +0200, Rafael J. Wysocki wrote: > >>+void acpi_gpiochip_free_interrupts(struct gpio_chip *chip) > >>+{ > >>+ acpi_handle handle; > >>+ acpi_status status; > >>+ struct list_head *evt_pins; > >>+ struct acpi_gpio_evt_pin *evt_pin, *ep; > >>+ > >>+ if (!chip->dev || !chip->to_irq) > >>+ return; > >>+ > >>+ handle = ACPI_HANDLE(chip->dev); > >>+ if (!handle) > >>+ return; > >>+ > >>+ status = acpi_get_data(handle, acpi_gpio_evt_dh, (void **)&evt_pins); > >>+ if (ACPI_FAILURE(status)) > >>+ return; > >>+ > >>+ list_for_each_entry_safe_reverse(evt_pin, ep, evt_pins, node) { > >>+ devm_free_irq(chip->dev, evt_pin->irq, evt_pin); > > > >How about using normal request/free_irq() functions for both _EVT and > >non-_EVT events? Since we now need to call acpi_gpiochip_free_interrupts() > >anyway, I don't see the point using devm_* functions here. > > > > Then we need to create a list of non-_EVT events, or add them to the > evt_pins list. Good point. Maybe we can add them to the evt_pins list and handle the same way as _EVT (except that we need to call _Exx and _Lxx methods instead of _EVT)?