Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp589309imm; Wed, 25 Jul 2018 02:39:05 -0700 (PDT) X-Google-Smtp-Source: AAOMgpc3bLjkKwmx3PlElbFmNYTXK16zjY4MUzQB3AQxXOiebm+NluYMKk2Z0G97c0zrRTfBrmrI X-Received: by 2002:a17:902:694a:: with SMTP id k10-v6mr20560830plt.166.1532511545218; Wed, 25 Jul 2018 02:39:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532511545; cv=none; d=google.com; s=arc-20160816; b=WbfztZGCUz4DbZt/8h3ry0uYGcYjGnpRiGvLdLwKhz7/actSANpkSQgmY3bYqj4Owy v9WyTOqlie52H17Hbb4N7fda+uZ695N8oXyWAQmMi/KELkPTiGu981R1hnC838SB2tfg vARYbNOmU/X1BB6PHBVuzaSkj8bCo13ZUgOuTtsm8QdzPZsSxYF6KScyStVVrwFMW6Dl k3qj1RsMTOqxWDPMZLqaj7GN8agu1rxzKVsObMQRd3ifaY6hZvFHv2o895onxAffoLk0 kYi94riCwYlbCqpB4vns4FibpmmyotKBeQVZ8PsdEYjulj1LshsbeOItQ0RdgKLRD9Cm ObWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature:arc-authentication-results; bh=zw790fIsPJb4zF8WntNv/1o2cuZq1bliXkE2Dn8ZPGs=; b=JPdf32Fnt38X1/h0QuTlO+a8aGo8o0cNY0E6bmtVBhAZimeR4kPAHaf278LM0Rhtbn fWujqSlF5jEShDQO5TJlfqitMBB5mUn0+SNZayHbgh60oLwhxj2ju43mMlTynpQFXNd6 R/+5ldF17nyV/HbUt47Q/gm+az2MXkrla0kRsLJMDi503NwuZcFD/BoTrJxDQXtBxsUu Re8+DcyIAtnXtpv4HKho2lttoWO7EJMHbNmgbWv071v0gOA7Qd8RTWWXa+xgaWWiQpus AHN+DK986ELMM326NZ1qA7zdzDMi5pSLfwzzWu4s3UUahuOHtfC5mBPrzrGhRjV3epGs eO+Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=pmDkVcUH; 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 f12-v6si13059157pgg.653.2018.07.25.02.38.50; Wed, 25 Jul 2018 02:39:05 -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; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=pmDkVcUH; 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 S1728903AbeGYKsI (ORCPT + 99 others); Wed, 25 Jul 2018 06:48:08 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:43182 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728768AbeGYKsG (ORCPT ); Wed, 25 Jul 2018 06:48:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=References:In-Reply-To:Message-Id: Date:Subject:Cc:To:From:Sender:Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=zw790fIsPJb4zF8WntNv/1o2cuZq1bliXkE2Dn8ZPGs=; b=pmDkVcUHyN/cvT8kZYE8+oel9 ZZuoKobFEvq6MfMO9999RxoR+gbhrlnIkOQRsNjVTxm/No9b1QclLLOlAo9kfP70HEhM0LftM1PvX qwhlUwAY4icW9avGjVqSdIeuRk8rnoyN/Hr6SQhrvfQrtwwOyZ+hHpgMlbksYxXNRK6At8WiimJ2X oP29p2kjDyX398Ih+vs969C+Afj3ED2u0YIEOoQNmHpP5CeKvoVCilaBYm2QSg8USeeg+pv39Qzpx RviaNO1GBpdljEdavLKib8i9ohKn3r0FXZnAfe6hNSkHGsBRVe1TpgGv3qsuubXpRZIi0NPEiGHHT 6fMXj+kQw==; Received: from [91.112.108.175] (helo=localhost) by bombadil.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1fiGEK-0005MZ-2f; Wed, 25 Jul 2018 09:37:12 +0000 From: Christoph Hellwig To: tglx@linutronix.de, palmer@sifive.com, jason@lakedaemon.net, marc.zyngier@arm.com, robh+dt@kernel.org, mark.rutland@arm.com Cc: devicetree@vger.kernel.org, aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, shorne@gmail.com, Palmer Dabbelt Subject: [PATCH 6/6] dt-bindings: interrupt-controller: RISC-V PLIC documentation Date: Wed, 25 Jul 2018 11:36:49 +0200 Message-Id: <20180725093649.32332-7-hch@lst.de> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20180725093649.32332-1-hch@lst.de> References: <20180725093649.32332-1-hch@lst.de> X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Palmer Dabbelt This patch adds documentation for the platform-level interrupt controller (PLIC) found in all RISC-V systems. This interrupt controller routes interrupts from all the devices in the system to each hart-local interrupt controller. Note: the DTS bindings for the PLIC aren't set in stone yet, as we might want to change how we're specifying holes in the hart list. Signed-off-by: Palmer Dabbelt --- .../interrupt-controller/riscv,plic0.txt | 55 +++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/riscv,plic0.txt diff --git a/Documentation/devicetree/bindings/interrupt-controller/riscv,plic0.txt b/Documentation/devicetree/bindings/interrupt-controller/riscv,plic0.txt new file mode 100644 index 000000000000..99cd359dbd43 --- /dev/null +++ b/Documentation/devicetree/bindings/interrupt-controller/riscv,plic0.txt @@ -0,0 +1,55 @@ +RISC-V Platform-Level Interrupt Controller (PLIC) +------------------------------------------------- + +The RISC-V supervisor ISA specification allows for the presence of a +platform-level interrupt controller (PLIC). The PLIC connects all external +interrupts in the system to all hart contexts in the system, via the external +interrupt source in each hart's hart-local interrupt controller (HLIC). A hart +context is a privilege mode in a hardware execution thread. For example, in +an 4 core system with 2-way SMT, you have 8 harts and probably at least two +privilege modes per hart; machine mode and supervisor mode. + +Each interrupt can be enabled on per-context basis. Any context can claim +a pending enabled interrupt and then release it once it has been handled. + +Each interrupt has a configurable priority. Higher priority interrupts are +serviced firs. Each context can specify a priority threshold. Interrupts +with priority below this threshold will not cause the PLIC to raise its +interrupt line leading to the context. + +While the PLIC supports both edge-triggered and level-triggered interrupts, +interrupt handlers are oblivious to this distinction and therefor it is not +specific in the PLIC device-tree binding. + +While the RISC-V ISA doesn't specify a memory layout for the PLIC, the +"riscv,plic0" device is a concrete implementation of the PLIC that contains a +specific memory layout. More details about the memory layout of the +"riscv,plic0" device can be found as a comment in the device driver, or as part +of the SiFive U5 Coreplex Series Manual (page 22 of the PDF of version 1.0) + + +Required properties: +- compatible : "riscv,plic0" +- #address-cells : should be <0> +- #interrupt-cells : should be <1> +- interrupt-controller : Identifies the node as an interrupt controller +- reg : Should contain 1 register range (address and length) +- interrupts-extended : Specifies which contexts are connected to the PLIC, + with "-1" specifying that a context is not present. + +Example: + + plic: interrupt-controller@c000000 { + #address-cells = <0>; + #interrupt-cells = <1>; + compatible = "riscv,plic0"; + interrupt-controller; + interrupts-extended = < + &cpu0-intc 11 + &cpu1-intc 11 &cpu1-intc 9 + &cpu2-intc 11 &cpu2-intc 9 + &cpu3-intc 11 &cpu3-intc 9 + &cpu4-intc 11 &cpu4-intc 9>; + reg = <0xc000000 0x4000000>; + riscv,ndev = <10>; + }; -- 2.18.0