From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Marc Zyngier <maz@kernel.org>
Cc: Huacai Chen <chenhc@lemote.com>, Rob Herring <robh+dt@kernel.org>,
Jason Cooper <jason@lakedaemon.net>,
Thomas Gleixner <tglx@linutronix.de>,
linux-mips@vger.kernel.org, Huacai Chen <chenhuacai@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Fuxin Zhang <zhangfx@lemote.com>
Subject: Re: [PATCH V2 0/5] MIPS: Loongson64: Fix and improve irqchip drivers
Date: Thu, 30 Jul 2020 14:31:17 +0200 [thread overview]
Message-ID: <20200730123117.GA4509@alpha.franken.de> (raw)
In-Reply-To: <159611041857.27532.12008177304488845888.b4-ty@kernel.org>
On Thu, Jul 30, 2020 at 01:06:03PM +0100, Marc Zyngier wrote:
> On Thu, 30 Jul 2020 16:51:25 +0800, Huacai Chen wrote:
> > Modernized Loongson64 platforms use a hierarchical interrupt controller
> > architecture. For LS7A PCH, the hierarchy (from inside to outside) is
> > CPUINTC --> LIOINTC --> HTVEC --> PCHPIC/PCHMSI. However, the current
> > status is that there are several bugs in the LIOINTC and PCHPIC drivers,
> > and the HTVEC driver should be improved to support 8 groups of vectors.
> > Loonson64C support only 4 groups of HT vectors, and Loongson64G support
> > as many as 8 groups, so the .dts file and dt-bindings description should
> > also be updated.
> >
> > [...]
>
> Applied to irq/irqchip-next, thanks!
>
> [1/5] dt-bindings: interrupt-controller: Update Loongson HTVEC description
> commit: 8fea4b2e804ab8ff93bd0d67a3dadee1d1a3e24f
> [3/5] irqchip/loongson-liointc: Fix misuse of gc->mask_cache
> commit: c9c73a05413ea4a465cae1cb3593b01b190a233f
> [4/5] irqchip/loongson-htvec: Support 8 groups of HT vectors
> commit: c47e388cfc648421bd821f5d9fda9e76eefe29cd
> [5/5] irqchip/loongson-pch-pic: Fix the misused irq flow handler
> commit: ac62460c24126eb2442e3653a266ebbf05b004d8
>
> Please note that I haven't taken patch #2, as it doesn't apply on top
> of irqchip/next. Please route it via the MIPS tree.
I'll take it.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-07-30 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 8:51 [PATCH V2 0/5] MIPS: Loongson64: Fix and improve irqchip drivers Huacai Chen
2020-07-30 8:51 ` [PATCH V2 1/5] dt-bindings: interrupt-controller: Update Loongson HTVEC description Huacai Chen
2020-07-30 8:51 ` [PATCH V2 2/5] MIPS: DTS: Fix number of msi vectors for Loongson64G Huacai Chen
2020-07-30 20:19 ` Thomas Bogendoerfer
2020-07-30 8:51 ` [PATCH V2 3/5] irqchip: loongson-liointc: Fix misuse of gc->mask_cache Huacai Chen
2020-07-30 8:51 ` [PATCH V2 4/5] irqchip: loongson-htvec: Support 8 groups of HT vectors Huacai Chen
2020-07-30 8:51 ` [PATCH V2 5/5] irqchip: loongson-pch-pic: Fix the misused irq flow handler Huacai Chen
2020-07-30 12:06 ` [PATCH V2 0/5] MIPS: Loongson64: Fix and improve irqchip drivers Marc Zyngier
2020-07-30 12:31 ` Thomas Bogendoerfer [this message]
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=20200730123117.GA4509@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhc@lemote.com \
--cc=chenhuacai@gmail.com \
--cc=jason@lakedaemon.net \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhangfx@lemote.com \
/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;
as well as URLs for NNTP newsgroup(s).