Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp7300135ybi; Wed, 5 Jun 2019 15:04:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqwSSjsY6fmTTb7LNO+6x1ttnfFKzXs7uJxdC5blx/1ge2dT6ZwZ35mU0I+hxD/dCwT0pj70 X-Received: by 2002:aa7:919a:: with SMTP id x26mr35532978pfa.134.1559772262655; Wed, 05 Jun 2019 15:04:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559772262; cv=none; d=google.com; s=arc-20160816; b=ArZalgUFejbHLBW+I2uA+LTl/VUtQSc3dnzVukiZ4tfAN7zOpIvXc1T47Y4g4BRZCc f/ZSlTavwzoGoAZ7TFSV4m9imOagU731Vp1LbjXzkzP72eIRcl6vrtyo3e9Wy1lxD/vQ o/v1cgDEyo2A3HsxObcvTevFHZ+Zpi7on4UBmYuXYaZ04S/8DLrgf5fFu85XKhCxUoH4 vX5v+hDLT6xU6sHZX0jwDr86vh9yrVtxIgulPFITRE2BkjngJySIlQ3m+DI/I/89a2WR ocmk6myd+W1Hf3WOV0yCkK3Rs4bCkEneWnFSGgyUiFWZ7DjVx1et8+1i/JyinCE/zOdV WKtg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=Z6nCnZATi6ZCrr5CfHkHRCfbF+CPpycbp9KSbPaP0UE=; b=zQgYFycPZMGWsDFrqVGDoQjT9qONXC6+YndBjD0mhwPgoFCaHT1VivGnnae9ooSuo4 6r5B9tjtCR2EBeSn5XgPGL4pGUt+mdit/FYXlhiZbUnABfU7pZajUV5LcvTd0E6qRWPE EHUccEbJd86Yhyz83VBPjh7aKgjhBv9a+V7siJqFTGWvGH6kfpf/HXSNdm7uriJBoElX 07Wir39OCmEtB38vixAeF4id+nZn9aggeSJxHvXdOK4eSMpztfB7TrhCXZS8kGWUjd6G 3/cRBBRSR4LtNdt/D5eI+slEyrnJsTeKi6hFzol0ZFQmumBHedebZURg4olg6lBF1RFO aedw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w28si98008pgl.218.2019.06.05.15.04.04; Wed, 05 Jun 2019 15:04:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726600AbfFEWCp (ORCPT + 99 others); Wed, 5 Jun 2019 18:02:45 -0400 Received: from gate.crashing.org ([63.228.1.57]:33831 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726305AbfFEWCp (ORCPT ); Wed, 5 Jun 2019 18:02:45 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id x55M2E1m023585; Wed, 5 Jun 2019 17:02:15 -0500 Message-ID: <8930de04d7f40b84068e4478a12fc496d53930c9.camel@kernel.crashing.org> Subject: Re: [PATCH v2 2/2] irqchip: al-fic: Introduce Amazon's Annapurna Labs Fabric Interrupt Controller Driver From: Benjamin Herrenschmidt To: Marc Zyngier , Talel Shenhar , nicolas.ferre@microchip.com, jason@lakedaemon.net, mark.rutland@arm.com, mchehab+samsung@kernel.org, robh+dt@kernel.org, davem@davemloft.net, shawn.lin@rock-chips.com, tglx@linutronix.de, devicetree@vger.kernel.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org Cc: dwmw@amazon.co.uk, jonnyc@amazon.com, hhhawa@amazon.com, ronenk@amazon.com, hanochu@amazon.com, barakw@amazon.com Date: Thu, 06 Jun 2019 08:02:13 +1000 In-Reply-To: References: <1559731921-14023-1-git-send-email-talel@amazon.com> <1559731921-14023-3-git-send-email-talel@amazon.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2019-06-05 at 13:22 +0100, Marc Zyngier wrote: > > > + * This is generally fixed depending on what pieces of HW it's wired up > > + * to. > > + * > > + * We configure it based on the sensitivity of the first source > > + * being setup, and reject any subsequent attempt at configuring it in a > > + * different way. > > Is that a reliable guess? It also strikes me that the DT binding doesn't > allow for the trigger type to be passed, meaning the individual drivers > have to request the trigger as part of their request_irq() call. I'd > rather you have a complete interrupt specifier in DT, and document the > various limitations of the HW. Actually the DT does, but Talel forgot to update the "example" part of the binding patch. The description does say 2 cells. This is the best approach imho (translation: I asked Talel to do it this way :-) The other option which I don't like is to stick to #interrupt-cells = 1, and have a separate property in the interrupt controller node to indicate whether it needs to be configured as level or edge. These FICs are used for what is generally fixed wires inside the SoC, so it doesn't matter much either way, but I prefer having it self configured based on source just in case a future implementation doesn't have the limitation of all inputs having the same trigger type. Cheers, Ben.