[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bksvvvcl.wl-maz@kernel.org>
Date: Mon, 08 Aug 2022 12:16:26 +0100
From: Marc Zyngier <maz@...nel.org>
To: Huacai Chen <chenhuacai@...il.com>
Cc: Huacai Chen <chenhuacai@...ngson.cn>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Xuefeng Li <lixuefeng@...ngson.cn>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] irqchip: Select downstream irqchip drivers for LoongArch CPU
On Mon, 08 Aug 2022 12:06:23 +0100,
Huacai Chen <chenhuacai@...il.com> wrote:
>
> Hi, Marc,
>
> On Mon, Aug 8, 2022 at 6:05 PM Marc Zyngier <maz@...nel.org> wrote:
> >
> > On Mon, 08 Aug 2022 09:53:19 +0100,
> > Huacai Chen <chenhuacai@...ngson.cn> 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 <lkp@...el.com>
> > > Signed-off-by: Huacai Chen <chenhuacai@...ngson.cn>
> > > ---
> > > 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?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists