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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1773BF8A16F for ; Thu, 16 Apr 2026 13:09:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=rvULyBk5VBWIOdDz4YhXh8YXhAaWRpYAltGaDd8RkGc=; b=JngjdwvgD7jQJAs/iWpx8YTL1A YnEnMwUhfaMUedlUwuJOhVLJBbqBQSoy3YsqLDVFmvq2dS/fghvs0lXw7Pq1DObuygLTavkw/xzUu BNjJBOUFcaIsWpLSqp/bTNkQPIo4LDMt0eSVLxzGBMIIyQt3CWBkoTJqmsgqHaWP8gN8rZbhnOpGn SWsZKzMWHuvjUjif3zmgGdUQPjB91GVTbdNpqEyJ0ZSysR1+i5Bdg58o/g3DJ+8ns8Fm9lI9rvX+n Z3ejJaDDWm5kdHR3oHgVBsQ88UbcctB7y2sMS7C+V3ANM95K0R6Q+K21SDLcKw9BkSHhvQGAny8Uy 0HK8xnRQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1wDMTQ-00000002TXk-1aJS; Thu, 16 Apr 2026 13:09:36 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1wDMTP-00000002TXe-0tIk for linux-arm-kernel@lists.infradead.org; Thu, 16 Apr 2026 13:09:35 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id 6508D60128 for ; Thu, 16 Apr 2026 13:09:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A631EC2BCAF; Thu, 16 Apr 2026 13:09:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776344974; bh=x6vLOatvX0u1D3ES70v+tZ0/zOg4L661uMa6B6zNNIc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=rDxBEMI5HVctMffXjyvPkbG3ZasOVS+DrJlXzUxkhz78a18OXopWebUScBIiDPhkx cfUbQTCQHOmb5Zw/NV3B+kf9W6J2fPm+Ct+britbmxx79hxaJ6G0l4ic5Vaw8yS4bG k6F4nCCSSdTE/ika3ZjPUzaYUi4vAhuGApSxvxav2LixAnnjnK4LOjt1EAI/XQv0TI xAHIfIc5cVftOKFkN11HkTSPoGdUbHG+MW4fXFgu1WJQh/mbi6LIy9JAOSo7hztI0z GV9dqh0nHKu4bG7+gPJQsfsufVhn4VCwY/9fCihTwVeEUIVwsUtFzdFzyj1qqVxift wlprlc7JcsJcw== Date: Thu, 16 Apr 2026 14:09:30 +0100 From: Sudeep Holla To: Rob Herring Cc: Krzysztof Kozlowski , Sudeep Holla , Conor Dooley , Marc Zyngier , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 1/5] dt-bindings: interrupt-controller: Add support for secure donated SGIs Message-ID: <20260416-true-prophetic-centipede-3ad8e5@sudeepholla> References: <20260412-b4-ffa_ns_sgi_gicv3-v1-0-af61243eb405@kernel.org> <20260412-b4-ffa_ns_sgi_gicv3-v1-1-af61243eb405@kernel.org> <20260416121146.GA2736962-robh@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260416121146.GA2736962-robh@kernel.org> X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Apr 16, 2026 at 07:11:46AM -0500, Rob Herring wrote: > On Sun, Apr 12, 2026 at 06:04:37PM +0100, Sudeep Holla wrote: > > In GICv3, SGI security is defined by interrupt grouping and configuration > > rather than by SGI number alone. Linux conventionally reserves SGIs 0-7 > > for non-secure internal kernel IPIs, while higher SGIs is assumed to be > > owned/stolen by the Secure world unless explicitly made available. > > > > Document secure donated SGI interrupt specifiers for the GICv3 binding. > > It describes "arm,secure-donated-ns-sgi-ranges" for SGIs donated by the > > secure world to non-secure software. It excludes SGIs 0-7, which are > > already used by the kernel for internal IPI purposes. > > > > Signed-off-by: Sudeep Holla > > --- > > .../bindings/interrupt-controller/arm,gic-v3.yaml | 27 +++++++++++++++++++++- > > include/dt-bindings/interrupt-controller/arm-gic.h | 1 + > > 2 files changed, 27 insertions(+), 1 deletion(-) > > > > diff --git a/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml b/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml > > index bfd30aae682b..664727d071c9 100644 > > --- a/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml > > +++ b/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml > > @@ -45,17 +45,24 @@ description: | > > > > The 1st cell is the interrupt type; 0 for SPI interrupts, 1 for PPI > > interrupts, 2 for interrupts in the Extended SPI range, 3 for the > > - Extended PPI range. Other values are reserved for future use. > > + Extended PPI range, and 4 for SGI interrupts. Other values are > > + reserved for future use. > > > > The 2nd cell contains the interrupt number for the interrupt type. > > SPI interrupts are in the range [0-987]. PPI interrupts are in the > > range [0-15]. Extended SPI interrupts are in the range [0-1023]. > > Extended PPI interrupts are in the range [0-127]. > > > > + SGI interrupts are in the range [8-15] which overlaps with the SGIs > > + assigned to/reserved for the secure world but donated to the non > > + secure world to use. Refer "arm,secure-donated-ns-sgi-ranges" for > > + more details. > > + > > The 3rd cell is the flags, encoded as follows: > > bits[3:0] trigger type and level flags. > > 1 = edge triggered > > 4 = level triggered > > + SGIs are edge triggered and must be described as such. > > > > The 4th cell is a phandle to a node describing a set of CPUs this > > interrupt is affine to. The interrupt must be a PPI, and the node > > @@ -136,6 +143,24 @@ description: | > > - $ref: /schemas/types.yaml#/definitions/uint32 > > - $ref: /schemas/types.yaml#/definitions/uint64 > > > > + arm,secure-donated-ns-sgi-ranges: > > + description: > > + A list of pairs , where "sgi" is the first SGI INTID of a > > + range donated by the secure side to non-secure software, and "span" is > > + the size of that range. Multiple ranges can be provided. > > + > > + SGIs described by interrupt specifiers with type 4 (SGI) must fall > > + within one of these ranges. SGIs(0-7) reserved by non-secure world > > + for internal IPIs must not be listed here. "sgi" must be in the > > + range [8-15], "span" must be in the range [1-8], and the range must > > + not extend past SGI 15. > > + $ref: /schemas/types.yaml#/definitions/uint32-matrix > > + items: > > As a matrix, you need: > > items: > items: > - ... > - ... > > However, given this is at most 8 entries, I would just do an array: > > minItems: 1 > maxItems: 8 > uniqueItems: true > items: > minimum: 8 > maximum: 15 > Makes sense. > Unless we need more flexibility in GICv5? > IIUC, there are not SGIs in GICv5 and we may need to use one software PPI as a replacement for SGIs. LPIs are used for IPIs. I am assuming Marc will soon post his opinion/rejection on this series 😉 based on some offline discussion we had with respect to how it fits with GICv5. > Is there an example we can stick this property into so it gets tested? > Not sure if [1] serves as an example or you are looking for something else. -- Regards, Sudeep [1] https://lore.kernel.org/all/20260412-b4-ffa_ns_sgi_gicv3-v1-5-af61243eb405@kernel.org/