Received: by 2002:a05:6358:e9c4:b0:b2:91dc:71ab with SMTP id hc4csp4639410rwb; Mon, 8 Aug 2022 04:51:25 -0700 (PDT) X-Google-Smtp-Source: AA6agR5cpWsqmHwZzeNR1E/I+DztH3Xo7pAhU4iFrUlfpK7VVspPsCxW0Quj8oUJW5A1SnpA0RkY X-Received: by 2002:a17:90a:a416:b0:1f7:3b5f:1cd1 with SMTP id y22-20020a17090aa41600b001f73b5f1cd1mr8228505pjp.216.1659959485725; Mon, 08 Aug 2022 04:51:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659959485; cv=none; d=google.com; s=arc-20160816; b=IuqPD1MeqWcLaz0Enxtxe8VtGKC8FBGMAUMb8Ig8t/byp1rzSEggOA5MPIXLeelDDO Ucj1AXD//ln3kqQbk86kWpdiN2443AddMOtYfD9TtLqQ1ZyusN/p24Yyr2mcasYTsDKZ YJmWVklNolAxraRpAP4+vQU88s7G3pYWuO0rRSvSOSSe2Ht+TINnkV126iDkNSR+Ag3v 21WAQcmgkahJD1tjbI2HRg5KhgP88MkDzSNzgOzpRJFeKpFOZKUcB5Bs8DCg1vdeqJAP a0XWgYAGToIIFqTH+e0HCjgawjSzsHPYV4G28OOzp9sXjEIxkbtSf+zoXfZ1nwNoWTAA y0Uw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=dysuPV5CQXbSugEYz8f2s3Gi2b71i7Fc2IQ6is/6Qgg=; b=XAU/mZZLY+YuY3DvauDc8PmZmpw3OmGjvVQlxf3vUDgAT5SSLr5cdoDFWc21S3dF0m PdvCEkOchyanAyKF8UR8E3w7UpggxjncQl/OVyPrrSB/2XWYug+/KLjyeNGfnN7CEOKi UOxahdTH4SXFbNAzdAVDalDVygf8qg/eLL1+nW4+AivW2IYJVgQoDRVjr8bUqF59H7fp sWEDVeP3+x9JUvvUssHRnCOxIg0zGY+xoriLtTjGY8shTDIF2P1hSTgZ9e+cLv8XxJDk 1YE0FBEze/ZvXXxN/Q02OUouxpY7LtjcEifLUshWt24f+9Nv0HXQREABtMGOe+pjqztC LUaQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=aQJP2vID; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y6-20020a17090ad0c600b001ea91760f6esi6520042pjw.79.2022.08.08.04.51.11; Mon, 08 Aug 2022 04:51:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=aQJP2vID; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242863AbiHHLYm (ORCPT + 99 others); Mon, 8 Aug 2022 07:24:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241944AbiHHLYk (ORCPT ); Mon, 8 Aug 2022 07:24:40 -0400 Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9579DDF70 for ; Mon, 8 Aug 2022 04:24:39 -0700 (PDT) Received: by mail-vs1-xe33.google.com with SMTP id d126so4173365vsd.13 for ; Mon, 08 Aug 2022 04:24:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=dysuPV5CQXbSugEYz8f2s3Gi2b71i7Fc2IQ6is/6Qgg=; b=aQJP2vIDtiP3KQSy+VjQbxpmSBOSc40evFworfFPveYME9ChOJ0RMr0LntVgRVn3RS anLl8QE34fv/7udH1zMX1+pWJv8Jf4k8EGokCZNcSLcpqFIq3KtdiONSopKs3niA7i7I 7TQIWMK0Ri5HKGL2ICKTbC2iYA+lEJug0R96S7vQS5din8jSxbkL1yQrLNKeCt9U5DL5 XOD1dvKXzQw12njgL5c+43dBjQumC7fF1Xr4godtQOANYv6JpdktRr8yJNnzkp8ctANO Dx8mf65ZA0sSWE16WvHkUJ/WeSFNPulLnDBOHtMFHFCxbR4fWN4HvVGD9h2vfO1gHDp8 QWRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=dysuPV5CQXbSugEYz8f2s3Gi2b71i7Fc2IQ6is/6Qgg=; b=fMSgGAAAeiDNKrJ4GJaXN7dcUt7U0utNO3FqdqSnspPV4XHVjji9LVc4MLszZfsBV0 eSL5WFbz8wVJ4CgGSOcuyqRyKA7lTxHO6UQsIXqqiW+D5SAs5eVufSQ8vUa6TIFjJICV A5QY2LStmlbct2kvT+2tTSm81Q2I0er6EDfcBovZ7i3HdeOvU/IHcJYkZSwUhiK1rrJy aJ1yUj+jsnqQRe0BG0tUJfb4kVwveKleGLtZpaO63TiNYRe+40SaXPqvCRNJ9ejfpie2 G1aon16JDYUoc0iBWscMEXvPCfK7ShrgwiQiPKsSkjbovL6lety4kTmROVpeKSRxBoyy zAeQ== X-Gm-Message-State: ACgBeo1sJNze7bCeuDz904QgOBou+ppHZ6232TR0wPIu5uFfKSBwQydB PPOlIGhTDkmSREa2UMriFwVbU554xR+cRxO08uw= X-Received: by 2002:a67:d595:0:b0:388:4392:e067 with SMTP id m21-20020a67d595000000b003884392e067mr7742420vsj.78.1659957878664; Mon, 08 Aug 2022 04:24:38 -0700 (PDT) MIME-Version: 1.0 References: <20220808085319.3350111-1-chenhuacai@loongson.cn> <87edxrvymh.wl-maz@kernel.org> <87bksvvvcl.wl-maz@kernel.org> In-Reply-To: <87bksvvvcl.wl-maz@kernel.org> From: Huacai Chen Date: Mon, 8 Aug 2022 19:24:27 +0800 Message-ID: Subject: Re: [PATCH] irqchip: Select downstream irqchip drivers for LoongArch CPU To: Marc Zyngier Cc: Huacai Chen , Thomas Gleixner , LKML , Xuefeng Li , Jiaxun Yang , kernel test robot Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Marc, On Mon, Aug 8, 2022 at 7:16 PM Marc Zyngier wrote: > > On Mon, 08 Aug 2022 12:06:23 +0100, > Huacai Chen wrote: > > > > Hi, Marc, > > > > On Mon, Aug 8, 2022 at 6:05 PM Marc Zyngier wrote: > > > > > > On Mon, 08 Aug 2022 09:53:19 +0100, > > > Huacai Chen wrote: > > > > > > > > LoongArch irqchips have a fixed hierarchy which currently can't be > > > > described by ACPI tables, so upstream irqchip drivers call downstream > > > > irqchip drivers' initialization directly. As a result, the top level > > > > (CPU-level) irqchip driver should explicitly select downstream drivers > > > > to avoid build errors. > > > > > > > > Reported-by: kernel test robot > > > > Signed-off-by: Huacai Chen > > > > --- > > > > drivers/irqchip/Kconfig | 5 +++++ > > > > 1 file changed, 5 insertions(+) > > > > > > > > diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig > > > > index 66b9fa408bf2..2549daa859d6 100644 > > > > --- a/drivers/irqchip/Kconfig > > > > +++ b/drivers/irqchip/Kconfig > > > > @@ -561,6 +561,11 @@ config IRQ_LOONGARCH_CPU > > > > select GENERIC_IRQ_CHIP > > > > select IRQ_DOMAIN > > > > select GENERIC_IRQ_EFFECTIVE_AFF_MASK > > > > + select LOONGSON_LIOINTC > > > > + select LOONGSON_EIOINTC > > > > + select LOONGSON_PCH_PIC > > > > + select LOONGSON_PCH_MSI > > > > + select LOONGSON_PCH_LPC > > > > > > This triggers tons of pretty bad compilation and configuration issues, > > > as PCI still isn't selectable, even in Linus' tree (see below). I'm > > > guessing you still have local patches that hide this issue. > > > > > > Please test your patches on an upstream tree in the future. > > I'm very sorry for that. I think this patch should be delayed after > > 5.20-rc1, then PCI code will have been merged. > > Sure, I'm fine with that. However, I have seen the PCI pull request > going in without any mention of the LoongArch support. Is it going via > another tree? PCI drivers have merged, and PCI enablement will go via loongarch tree. Once I wanted to send PR to Linus today, but Steven said that the loongarch-next branch breaks some build so I should fix that first. Huacai > > Thanks, > > M. > > -- > Without deviation from the norm, progress is not possible.