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 X-Spam-Level: X-Spam-Status: No, score=-14.0 required=3.0 tests=BAYES_00,INCLUDES_CR_TRAILER, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 29CE9C4320A for ; Tue, 31 Aug 2021 21:16:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0A06B6108E for ; Tue, 31 Aug 2021 21:16:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232930AbhHaVRA (ORCPT ); Tue, 31 Aug 2021 17:17:00 -0400 Received: from mail-ot1-f49.google.com ([209.85.210.49]:45581 "EHLO mail-ot1-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232101AbhHaVRA (ORCPT ); Tue, 31 Aug 2021 17:17:00 -0400 Received: by mail-ot1-f49.google.com with SMTP id l7-20020a0568302b0700b0051c0181deebso835076otv.12; Tue, 31 Aug 2021 14:16:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=rZmwEc8NSqQoWoUVVA+56Qi0kmHYwHehZyUiwcO+sqs=; b=S+S+fT55alkGNj8IncFdTS6BxUSlz7Oi4zETbZiR9uF+9017cNbh1K135uwkxqEl1+ h9LUlcST+dw/et2Gxi/QsuJhkhT8jkAuLBOiVNt1J1zsa/pOZL4CYRYrRN14EpCijK7D CEeQQr7QMJ/m4crHJ0x1+JqftJ+pTEX5a98ivwyPIk2eDjo8QSTgWUTOOtXwEl8vMYrq JDPtyIfk8uO/ai+/oXDLBQQZ3Vpza/d3A15RHTlqBJtFATs6iNCN7w6nqW8Xu7IXYZEz c5M9XY5AhXKnLWICjlZDb6K8ri3kIWx9bKuFl80SxPwPkRagCAxn03KbmdlKvRJyrj5A Cbvg== X-Gm-Message-State: AOAM533QaFcPkiuSQQXSvR5w445I/GQnDTw5183Bf1+ZXyaPkysyqkMg tOuxbNbGSws0Ww2aQBj1Mw== X-Google-Smtp-Source: ABdhPJw7RRtPYNtKDaTLRNDD+gWvBYmpgo6Y5q94eazPn7Kx9XK37LCbzcdLvdMzHqsNBXzR9UapMw== X-Received: by 2002:a9d:4b86:: with SMTP id k6mr21942828otf.198.1630444564237; Tue, 31 Aug 2021 14:16:04 -0700 (PDT) Received: from robh.at.kernel.org (66-90-148-213.dyn.grandenetworks.net. [66.90.148.213]) by smtp.gmail.com with ESMTPSA id b9sm4276424otp.46.2021.08.31.14.16.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 31 Aug 2021 14:16:03 -0700 (PDT) Received: (nullmailer pid 659825 invoked by uid 1000); Tue, 31 Aug 2021 21:16:02 -0000 Date: Tue, 31 Aug 2021 16:16:02 -0500 From: Rob Herring To: Mark Kettenis Cc: devicetree@vger.kernel.org, alyssa@rosenzweig.io, Mark Kettenis , Thomas Gleixner , Marc Zyngier , Hector Martin , Bjorn Helgaas , Jim Quinlan , Nicolas Saenz Julienne , Florian Fainelli , bcm-kernel-feedback-list@broadcom.com, Daire McNamara , Saenz Julienne , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org, linux-rpi-kernel@lists.infradead.org Subject: Re: [PATCH v4 2/4] dt-bindings: interrupt-controller: msi: Add msi-ranges property Message-ID: References: <20210827171534.62380-1-mark.kettenis@xs4all.nl> <20210827171534.62380-3-mark.kettenis@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210827171534.62380-3-mark.kettenis@xs4all.nl> Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Fri, Aug 27, 2021 at 07:15:27PM +0200, Mark Kettenis wrote: > From: Mark Kettenis > > Update the MSI controller binding to add an msi-ranges property > that specifies how MSIs map onto regular interrupts on some other > interrupt controller. > > Signed-off-by: Mark Kettenis > --- > .../bindings/interrupt-controller/msi-controller.yaml | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml b/Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml > index 5ed6cd46e2e0..bf8b8a7dba09 100644 > --- a/Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml > +++ b/Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml > @@ -31,4 +31,12 @@ properties: > Identifies the node as an MSI controller. > $ref: /schemas/types.yaml#/definitions/flag > > + msi-ranges: > + description: > + A list of pairs , where "intid" is the specification It's not really 'pairs' and 'interrupt specifier' is the terminology the spec uses. How about: A list of , where "phandle" is parent interrupt controller, "intspec" is the starting/base interrupt specifier, and "span" is the size of that range (typically multiples of 32). The 'multiples of 32' part is what Marc told me. > + of the first interrupt (including the phandle for the interrupt > + controller) that can be used as an MSI, and "span" the size of > + that range. Multiple ranges can be provided. > + $ref: /schemas/types.yaml#/definitions/phandle-array > + > additionalProperties: true > -- > 2.32.0 > >