From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Icenowy Zheng <zhengxingda@iscas.ac.cn>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Enable LPC interrupt controller on MIPS LS7A systems
Date: Tue, 26 May 2026 16:42:15 +0200 [thread overview]
Message-ID: <ahWxR7sW7o06IDDX@alpha.franken.de> (raw)
In-Reply-To: <20260411101744.4020216-1-zhengxingda@iscas.ac.cn>
On Sat, Apr 11, 2026 at 06:17:42PM +0800, Icenowy Zheng wrote:
> This patchset tries to enable support for LPC interrupts on MIPS-based
> Loongson systems with Loongson 7A1000 PCH chip.
>
> The corresponding irqchip support (along with the DT binding) is already
> added to the tip tree.
>
> Tested on a Haier Boyue G51 system with legacy i8042 keyboard/mouse as
> integrated ones.
>
> This patchset is splitted from the original patchset that contains both
> driver part and DT part.
>
> Icenowy Zheng (2):
> MIPS: Loongson64: dts: Sort nodes
> MIPS: Loongson64: dts: Add node for LS7A PCH LPC
>
> arch/mips/boot/dts/loongson/ls7a-pch.dtsi | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
series applied to mips-next
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:[~2026-05-26 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 10:17 [PATCH 0/2] Enable LPC interrupt controller on MIPS LS7A systems Icenowy Zheng
2026-04-11 10:17 ` [PATCH 1/2] MIPS: Loongson64: dts: Sort nodes Icenowy Zheng
2026-04-11 10:17 ` [PATCH 2/2] MIPS: Loongson64: dts: Add node for LS7A PCH LPC Icenowy Zheng
2026-04-29 9:35 ` [PATCH 0/2] Enable LPC interrupt controller on MIPS LS7A systems Jiaxun Yang
2026-05-26 14:42 ` 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=ahWxR7sW7o06IDDX@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zhengxingda@iscas.ac.cn \
/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