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 577D5C25B67 for ; Thu, 26 Oct 2023 16:52:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version: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:References: List-Owner; bh=O6vC9xIk0zquRcOQvbrJBorU89HidYDNe+mwIWFCBNY=; b=EF5VUf9UQ2bYY9 +D7hBvho2NwR0QLmWQqFE9ra/M0L/I9xK87gu4xZNP9j8Rl8ej2hVnU54xPKDWT320fxNhZ+1xMUG RUaESJaIxaTHRTqxyQi0nswky39Wn5epETShxnJZ9y3nsBHFJvMskUpWIxKZf9bngEY2RsVTlv8tX QQhHaXqyLd1ucan9CQ7rAgfFO2eP5DkpUmUOaU8Vw3f+cCHud/N6je0QAbjYj1yllrSEi1129/t4p /INYV52+6geJJb7vOpgfy11UfjhPF4BxP5UUcVELG6pqkGiYteuY/vNaJj4U8G7yyh06LKv6q8Xyd tlxjJtOTGTbCeBukXcmw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qw3aQ-00Et0d-2y; Thu, 26 Oct 2023 16:51:58 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qw3aN-00Et02-12; Thu, 26 Oct 2023 16:51:56 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by ams.source.kernel.org (Postfix) with ESMTP id 169F3B80ED9; Thu, 26 Oct 2023 16:51:53 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 283EDC433C7; Thu, 26 Oct 2023 16:51:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1698339112; bh=V8qM86kYWnahH8L8to5RnmhawuvXMtXfMH61MytOS1c=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=BlavQRLWWVuUARbinIctcKA8CrUyeRJJCzAYRa0Fnlh/gujQqIpQDkbPZLXuTsxB2 anoCTsLnIYAxfr4tz2637av8xqeK14rbMoxBmRXEei5mUPe81JdX75sAvTlkKPRNqV aynexxIOqntWEOLzZPUH5nNkvFYeW0ENy6fgdQP35bLmHR0J1eUHWj6v7oBJfkeF9r QCu85klS6/56jeSeth5ZOSf58mkffvvnAjmJn+9muzJEhOFbbnf3HVpv6YH7BlEevY /nN6PwqU4zJ5iUO6kAuM0XyjWTf/804GKb8OJVf4hoVSFGWdZyt/87Y+yIhWIg3Hfp kQuiBNn/fG3wA== Date: Thu, 26 Oct 2023 11:51:50 -0500 From: Bjorn Helgaas To: Sunil V L Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org, linux-serial@vger.kernel.org, Catalin Marinas , Will Deacon , Paul Walmsley , Palmer Dabbelt , Albert Ou , "Rafael J . Wysocki" , Len Brown , Bjorn Helgaas , Anup Patel , Thomas Gleixner , Greg Kroah-Hartman , Jiri Slaby , Conor Dooley , Andrew Jones , Atish Kumar Patra , Haibo Xu Subject: Re: [RFC PATCH v2 13/21] irqchip: riscv-intc: Add ACPI support for AIA Message-ID: <20231026165150.GA1825130@bhelgaas> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20231025202344.581132-14-sunilvl@ventanamicro.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231026_095155_532739_ED072B65 X-CRM114-Status: GOOD ( 12.05 ) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Oct 26, 2023 at 01:53:36AM +0530, Sunil V L wrote: > The RINTC subtype structure in MADT also has information about other > interrupt controllers like MMIO. So, save those information and provide > interfaces to retrieve them when required by corresponding drivers. > @@ -218,7 +306,19 @@ static int __init riscv_intc_acpi_init(union acpi_subtable_headers *header, > + * MSI controller (IMSIC) in RISC-V is optional. So, unless > + * IMSIC is discovered, set system wide MSI support as > + * unsupported. Once IMSIC is probed, MSI support will be set. > + */ > + pci_no_msi(); It doesn't seem like we should have to tell the PCI core about functionality we *don't* have. I would think IMSIC would be detected before enumerating PCI devices that might use it, and if we *haven't* found an IMSIC by the time we get to pci_register_host_bridge(), would/should we set PCI_BUS_FLAGS_NO_MSI there? I see Thomas is cc'd; he'd have better insight. Bjorn _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel