From: Marc Zyngier <maz@kernel.org>
To: Huacai Chen <chenhuacai@gmail.com>
Cc: Huacai Chen <chenhuacai@loongson.cn>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Xuefeng Li <lixuefeng@loongson.cn>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] irqchip: Select downstream irqchip drivers for LoongArch CPU
Date: Mon, 08 Aug 2022 12:16:26 +0100 [thread overview]
Message-ID: <87bksvvvcl.wl-maz@kernel.org> (raw)
In-Reply-To: <CAAhV-H43WQhdnn-QjEAu4gPVt9u7b5hfBXHM6jH2Tt08cBY0eg@mail.gmail.com>
On Mon, 08 Aug 2022 12:06:23 +0100,
Huacai Chen <chenhuacai@gmail.com> wrote:
>
> Hi, Marc,
>
> On Mon, Aug 8, 2022 at 6:05 PM Marc Zyngier <maz@kernel.org> wrote:
> >
> > On Mon, 08 Aug 2022 09:53:19 +0100,
> > Huacai Chen <chenhuacai@loongson.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@intel.com>
> > > Signed-off-by: Huacai Chen <chenhuacai@loongson.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.
next prev parent reply other threads:[~2022-08-08 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 8:53 [PATCH] irqchip: Select downstream irqchip drivers for LoongArch CPU Huacai Chen
2022-08-08 10:05 ` Marc Zyngier
2022-08-08 11:06 ` Huacai Chen
2022-08-08 11:16 ` Marc Zyngier [this message]
2022-08-08 11:24 ` Huacai Chen
2022-08-09 1:59 ` kernel test robot
2022-09-13 12:53 ` [irqchip: irq/irqchip-fixes] " irqchip-bot for Huacai Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bksvvvcl.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=chenhuacai@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=lkp@intel.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox