Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753406AbdCPTOa (ORCPT ); Thu, 16 Mar 2017 15:14:30 -0400 Received: from smtp2-g21.free.fr ([212.27.42.2]:30559 "EHLO smtp2-g21.free.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751954AbdCPTO2 (ORCPT ); Thu, 16 Mar 2017 15:14:28 -0400 Subject: Re: Legacy PCI interrupt support in PCIe host driver To: Thomas Gleixner Cc: LKML , Linux ARM , Marc Zyngier , Jason Cooper , linux-pci , Bjorn Helgaas , Thibaud Cornic , Phuong Nguyen , Robin Murphy , Liviu Dudau , Lorenzo Pieralisi , Uwe Kleine-Konig , Rob Herring References: <5612adb6-af5c-9fbf-e725-813ee7fe1b4b@free.fr> <8443b350-6aa6-75f8-af48-892c722fc2d9@free.fr> From: Mason Message-ID: <4e54c5f9-7cc1-cfab-592d-a87795147020@free.fr> Date: Thu, 16 Mar 2017 20:13:15 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 702 Lines: 21 On 16/03/2017 18:47, Thomas Gleixner wrote: > On Thu, 16 Mar 2017, Mason wrote: >> I guess if two interrupts fire at the same time, we'll just take two >> separate exceptions? > > Wrong guess. That might work with level interrupts, but with other types > nothing will raise another exception. Sharing interrupts on edge types is a > stupid idea, but hardware folks insist on implementing stupid ideas. When you say "That might work with level interrupts", what is "that" ? In my case, interrupt-map = <0 0 0 1 &irq0 54 IRQ_TYPE_LEVEL_HIGH>; interrupts = <54 IRQ_TYPE_LEVEL_HIGH>; Both ISRs expect LEVEL_HIGH. In fact, doesn't request_irq return an error if the triggers are different? Regards.