From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [PATCH 2/2] gpio: sch: Add interrupt support Date: Wed, 24 Apr 2019 12:45:06 +0300 Message-ID: <20190424094506.GA2654@lahna.fi.intel.com> References: <20190424075816.GU2654@lahna.fi.intel.com> <8999d3f8-d169-eb85-bd2f-08c99d184ea2@siemens.com> <20190424081802.GV2654@lahna.fi.intel.com> <5a28f22c-22f7-760a-d076-68ff19800d44@siemens.com> <20190424084259.GW2654@lahna.fi.intel.com> <7e328b7e-f4f0-851a-4152-a9ffd058201c@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <7e328b7e-f4f0-851a-4152-a9ffd058201c@siemens.com> Sender: linux-kernel-owner@vger.kernel.org To: Jan Kiszka Cc: Andy Shevchenko , Linus Walleij , Bartosz Golaszewski , Linux Kernel Mailing List , linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org, "Rafael J. Wysocki" List-Id: linux-acpi@vger.kernel.org On Wed, Apr 24, 2019 at 11:36:58AM +0200, Jan Kiszka wrote: > OK, there is that table, but what is it supposed to tell me about the > event and where to hook into it better? ... > [02Eh 0046 2] SCI Interrupt : 0009 This is the SCI interrupt GSI number. IIRC it maps 1:1 to Linux interrupt number so you should see it in /proc/interrupts. When a GPE event is triggered it should be handled in the ACPI core. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CABE6C10F11 for ; Wed, 24 Apr 2019 09:45:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9E81A2077C for ; Wed, 24 Apr 2019 09:45:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726480AbfDXJpL (ORCPT ); Wed, 24 Apr 2019 05:45:11 -0400 Received: from mga04.intel.com ([192.55.52.120]:60057 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726216AbfDXJpL (ORCPT ); Wed, 24 Apr 2019 05:45:11 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Apr 2019 02:45:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,389,1549958400"; d="scan'208";a="167441332" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.157]) by fmsmga001.fm.intel.com with SMTP; 24 Apr 2019 02:45:07 -0700 Received: by lahna (sSMTP sendmail emulation); Wed, 24 Apr 2019 12:45:06 +0300 Date: Wed, 24 Apr 2019 12:45:06 +0300 From: Mika Westerberg To: Jan Kiszka Cc: Andy Shevchenko , Linus Walleij , Bartosz Golaszewski , Linux Kernel Mailing List , linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org, "Rafael J. Wysocki" Subject: Re: [PATCH 2/2] gpio: sch: Add interrupt support Message-ID: <20190424094506.GA2654@lahna.fi.intel.com> References: <20190424075816.GU2654@lahna.fi.intel.com> <8999d3f8-d169-eb85-bd2f-08c99d184ea2@siemens.com> <20190424081802.GV2654@lahna.fi.intel.com> <5a28f22c-22f7-760a-d076-68ff19800d44@siemens.com> <20190424084259.GW2654@lahna.fi.intel.com> <7e328b7e-f4f0-851a-4152-a9ffd058201c@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline In-Reply-To: <7e328b7e-f4f0-851a-4152-a9ffd058201c@siemens.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org Message-ID: <20190424094506.EdfSANV3kAUPK0szJWERE0a5W9EGI08cXuSM9F0-CYo@z> On Wed, Apr 24, 2019 at 11:36:58AM +0200, Jan Kiszka wrote: > OK, there is that table, but what is it supposed to tell me about the > event and where to hook into it better? ... > [02Eh 0046 2] SCI Interrupt : 0009 This is the SCI interrupt GSI number. IIRC it maps 1:1 to Linux interrupt number so you should see it in /proc/interrupts. When a GPE event is triggered it should be handled in the ACPI core.