Received: by 2002:a05:7412:31a9:b0:e2:908c:2ebd with SMTP id et41csp2851624rdb; Tue, 12 Sep 2023 14:18:47 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHJFVQMmDY/i2cEuw3L5IBin/X9tVl0763NkWjISuMVHywMnaxatVEjfTTFk3xYvjQr0uCa X-Received: by 2002:a05:6a21:6d9e:b0:134:a4e2:4ac8 with SMTP id wl30-20020a056a216d9e00b00134a4e24ac8mr691263pzb.39.1694553527568; Tue, 12 Sep 2023 14:18:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1694553527; cv=none; d=google.com; s=arc-20160816; b=aEf4UtgwxNiZquIWfluduWYLl1+mSFv0s8g5T6pwVeocQTy1n+nmM8cSUMeWOOsK85 0vR6OnzEtm9ZNpvzG4b8/OWFVtOJWikkqzJD0E//gSNaRYNCw7unxIyRh+4xr7zHnoTK VJCYJOeUs16aBB8Cch+cu8C+FsSw9kToK9cbkriOZ58ny5uB5sokbXxezWmcmLOFttaW vzdUuUrtZkcQ3wx6yc8kiQMlTzn7xdLPxqsFsgthyOJvuL9sUzyztHOVW7y5/Ph/Aars f0Z463pBYWa+CdyNFbUgVQ3kT10NRhU9oSP58gPQCwnMIQX8IeNwgi1viHDHtPLR0h7Y nruw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=ZOjDepVi55uZJQ1rIBBnqb1diEnF/zfemFV4q9wl2F4=; fh=cnGyrU6KU0VQNJMKB03edoR8OrOtwtd0XanYVBu+B1Y=; b=hZBIECi69xjEdvO79dyJjGR5zem/c/gl9irV8RNnUj5vSUSt1AVKBFBF6YlzoS/ENG JPl0WH/KZCyuT6wtDjemfuJtTfLMOGRfb05s3fHwMGiemujX61H6EMTosSHmmEIIGFkM 9jjXC9ezgOlsswyEYmBzLcBRaq6jNDtLEAj/exAPJcotYSIlX7WVl1Na0H6eaY7QlWCJ Oe+66YqdbBAg5fRstFvwbJs2mOhU6/UKSSG9XyWjgMpqEmoEuyfuQ8Jtl//C0FRCJxEN h1Y2wzqEN6SVBiPEAp7+yDPYWINJUoaRHuT26JOhckAnjmwhHwaMaxp1SXA1OnI3Z2DS eSUw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ventanamicro.com header.s=google header.b=iLTlvW8m; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from howler.vger.email (howler.vger.email. [2620:137:e000::3:4]) by mx.google.com with ESMTPS id u22-20020a17090a0c5600b00263e299dff6si89456pje.74.2023.09.12.14.18.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Sep 2023 14:18:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4; Authentication-Results: mx.google.com; dkim=pass header.i=@ventanamicro.com header.s=google header.b=iLTlvW8m; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by howler.vger.email (Postfix) with ESMTP id D94BE8725CEF; Tue, 12 Sep 2023 10:51:24 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at howler.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236893AbjILRvX (ORCPT + 99 others); Tue, 12 Sep 2023 13:51:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36686 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237262AbjILRvO (ORCPT ); Tue, 12 Sep 2023 13:51:14 -0400 Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 693C21711 for ; Tue, 12 Sep 2023 10:51:08 -0700 (PDT) Received: by mail-pl1-x629.google.com with SMTP id d9443c01a7336-1bf6ea270b2so40831685ad.0 for ; Tue, 12 Sep 2023 10:51:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ventanamicro.com; s=google; t=1694541068; x=1695145868; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=ZOjDepVi55uZJQ1rIBBnqb1diEnF/zfemFV4q9wl2F4=; b=iLTlvW8m2poUuDTLDw6BWFYVMWFYVcJo21WLpGX/KMXHMVXzrlr2w0+mGjQuwLuhok QQ6a4Xx/0B12HRT2t7OBzRaTJgmDVkmy2NwHPq0y1wmPcswTDb7tpiygaJXlBBWy+35e M4Eomoh2BuEHYtcKIiWf+TqTMNjqpEjt7bAS8k7SR79ltoDw6hndg7t/gLBZEYJ4paRG T+hxMKDH4lNsrhAlrHgFSiZqNSMrAF2S2rq8Wnn+2lPYg99DL/3XkTzMv2aKZymnqIWE YZvGQN+4B8rVaHCjcYFfgbsEjpoau9mAgHnjXnijCVjhzuuBHN+vWT1T5Wwr+c+k3eWf IwTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694541068; x=1695145868; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZOjDepVi55uZJQ1rIBBnqb1diEnF/zfemFV4q9wl2F4=; b=e14bNXMmattXo6o5JYeEhGhX6QeCCDnEmDlpdcbHIyI4tpSzwwohIuxzq+jZ0hjh7L xITQXaXE7ZR7T8N/wMWmmkrYIhx5PKOgG2TQ7S6pylnq1d7HO43aQwHEYPWTaJ2/Qcst 8+VJCRxEHySmbdNL6jhMTysRWw5gjiCjaTMFTR0WH2KODh58JkeoG+Fo24gRzOVZ5ZwP vkrYDeq5oXkcw40zTCAGzNDcYZ1dvhlNDp9mj1Wv3bPAVhrFzacsXujec7OtkBmrBa6K 4rdN7o9H08vwL+u/VYRTQYj0dgfp5nIlEyXPFfkHnlMsC1S0fRb2aTLgYERAHpJQ1Rf7 rZuA== X-Gm-Message-State: AOJu0YxipSqHPljQM0sGesuUQYYPSs8lmNAFyH9zmtUrg7KvWPBTHUoK B6WyNKfX3nZbALzCpDE8J6yuMA== X-Received: by 2002:a17:902:ec89:b0:1c3:9632:f144 with SMTP id x9-20020a170902ec8900b001c39632f144mr579021plg.31.1694541067692; Tue, 12 Sep 2023 10:51:07 -0700 (PDT) Received: from localhost.localdomain ([171.76.81.83]) by smtp.gmail.com with ESMTPSA id p12-20020a170902a40c00b001b891259eddsm8691440plq.197.2023.09.12.10.51.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Sep 2023 10:51:07 -0700 (PDT) From: Anup Patel To: Palmer Dabbelt , Paul Walmsley , Thomas Gleixner , Marc Zyngier , Rob Herring , Krzysztof Kozlowski , Frank Rowand , Conor Dooley Cc: Atish Patra , Andrew Jones , Sunil V L , Saravana Kannan , Anup Patel , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Anup Patel , Conor Dooley , Krzysztof Kozlowski Subject: [PATCH v8 08/16] dt-bindings: interrupt-controller: Add RISC-V incoming MSI controller Date: Tue, 12 Sep 2023 23:19:20 +0530 Message-Id: <20230912174928.528414-9-apatel@ventanamicro.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230912174928.528414-1-apatel@ventanamicro.com> References: <20230912174928.528414-1-apatel@ventanamicro.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (howler.vger.email [0.0.0.0]); Tue, 12 Sep 2023 10:51:25 -0700 (PDT) We add DT bindings document for the RISC-V incoming MSI controller (IMSIC) defined by the RISC-V advanced interrupt architecture (AIA) specification. Signed-off-by: Anup Patel Reviewed-by: Conor Dooley Acked-by: Krzysztof Kozlowski --- .../interrupt-controller/riscv,imsics.yaml | 172 ++++++++++++++++++ 1 file changed, 172 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/riscv,imsics.yaml diff --git a/Documentation/devicetree/bindings/interrupt-controller/riscv,imsics.yaml b/Documentation/devicetree/bindings/interrupt-controller/riscv,imsics.yaml new file mode 100644 index 000000000000..84976f17a4a1 --- /dev/null +++ b/Documentation/devicetree/bindings/interrupt-controller/riscv,imsics.yaml @@ -0,0 +1,172 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/interrupt-controller/riscv,imsics.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: RISC-V Incoming MSI Controller (IMSIC) + +maintainers: + - Anup Patel + +description: | + The RISC-V advanced interrupt architecture (AIA) defines a per-CPU incoming + MSI controller (IMSIC) for handling MSIs in a RISC-V platform. The RISC-V + AIA specification can be found at https://github.com/riscv/riscv-aia. + + The IMSIC is a per-CPU (or per-HART) device with separate interrupt file + for each privilege level (machine or supervisor). The configuration of + a IMSIC interrupt file is done using AIA CSRs and it also has a 4KB MMIO + space to receive MSIs from devices. Each IMSIC interrupt file supports a + fixed number of interrupt identities (to distinguish MSIs from devices) + which is same for given privilege level across CPUs (or HARTs). + + The device tree of a RISC-V platform will have one IMSIC device tree node + for each privilege level (machine or supervisor) which collectively describe + IMSIC interrupt files at that privilege level across CPUs (or HARTs). + + The arrangement of IMSIC interrupt files in MMIO space of a RISC-V platform + follows a particular scheme defined by the RISC-V AIA specification. A IMSIC + group is a set of IMSIC interrupt files co-located in MMIO space and we can + have multiple IMSIC groups (i.e. clusters, sockets, chiplets, etc) in a + RISC-V platform. The MSI target address of a IMSIC interrupt file at given + privilege level (machine or supervisor) encodes group index, HART index, + and guest index (shown below). + + XLEN-1 > (HART Index MSB) 12 0 + | | | | + ------------------------------------------------------------- + |xxxxxx|Group Index|xxxxxxxxxxx|HART Index|Guest Index| 0 | + ------------------------------------------------------------- + +allOf: + - $ref: /schemas/interrupt-controller.yaml# + - $ref: /schemas/interrupt-controller/msi-controller.yaml# + +properties: + compatible: + items: + - enum: + - qemu,imsics + - const: riscv,imsics + + reg: + minItems: 1 + maxItems: 16384 + description: + Base address of each IMSIC group. + + interrupt-controller: true + + "#interrupt-cells": + const: 0 + + msi-controller: true + + "#msi-cells": + const: 0 + + interrupts-extended: + minItems: 1 + maxItems: 16384 + description: + This property represents the set of CPUs (or HARTs) for which given + device tree node describes the IMSIC interrupt files. Each node pointed + to should be a riscv,cpu-intc node, which has a CPU node (i.e. RISC-V + HART) as parent. + + riscv,num-ids: + $ref: /schemas/types.yaml#/definitions/uint32 + minimum: 63 + maximum: 2047 + description: + Number of interrupt identities supported by IMSIC interrupt file. + + riscv,num-guest-ids: + $ref: /schemas/types.yaml#/definitions/uint32 + minimum: 63 + maximum: 2047 + description: + Number of interrupt identities are supported by IMSIC guest interrupt + file. When not specified it is assumed to be same as specified by the + riscv,num-ids property. + + riscv,guest-index-bits: + minimum: 0 + maximum: 7 + default: 0 + description: + Number of guest index bits in the MSI target address. + + riscv,hart-index-bits: + minimum: 0 + maximum: 15 + description: + Number of HART index bits in the MSI target address. When not + specified it is calculated based on the interrupts-extended property. + + riscv,group-index-bits: + minimum: 0 + maximum: 7 + default: 0 + description: + Number of group index bits in the MSI target address. + + riscv,group-index-shift: + $ref: /schemas/types.yaml#/definitions/uint32 + minimum: 0 + maximum: 55 + default: 24 + description: + The least significant bit position of the group index bits in the + MSI target address. + +required: + - compatible + - reg + - interrupt-controller + - msi-controller + - "#msi-cells" + - interrupts-extended + - riscv,num-ids + +unevaluatedProperties: false + +examples: + - | + // Example 1 (Machine-level IMSIC files with just one group): + + interrupt-controller@24000000 { + compatible = "qemu,imsics", "riscv,imsics"; + interrupts-extended = <&cpu1_intc 11>, + <&cpu2_intc 11>, + <&cpu3_intc 11>, + <&cpu4_intc 11>; + reg = <0x28000000 0x4000>; + interrupt-controller; + #interrupt-cells = <0>; + msi-controller; + #msi-cells = <0>; + riscv,num-ids = <127>; + }; + + - | + // Example 2 (Supervisor-level IMSIC files with two groups): + + interrupt-controller@28000000 { + compatible = "qemu,imsics", "riscv,imsics"; + interrupts-extended = <&cpu1_intc 9>, + <&cpu2_intc 9>, + <&cpu3_intc 9>, + <&cpu4_intc 9>; + reg = <0x28000000 0x2000>, /* Group0 IMSICs */ + <0x29000000 0x2000>; /* Group1 IMSICs */ + interrupt-controller; + #interrupt-cells = <0>; + msi-controller; + #msi-cells = <0>; + riscv,num-ids = <127>; + riscv,group-index-bits = <1>; + riscv,group-index-shift = <24>; + }; +... -- 2.34.1