From: Marc Zyngier <maz@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Julius Werner <jwerner@chromium.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Serge Semin <fancer.lancer@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] irqchip updates for 6.4, take #1
Date: Sun, 21 May 2023 11:18:12 +0100 [thread overview]
Message-ID: <20230521101812.2520740-1-maz@kernel.org> (raw)
Thomas,
Here's a handful of irqchip fixes for 6.4. Nothing major, the most
interesting thing being the workaround for a "creative" firmware issue
on some Mediatek-based Chromebooks, resulting in fireworks of the
pseudo-NMI feature is enabled.
Please pull,
M.
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git tags/irqchip-fixes-6.4-1
for you to fetch changes up to cddb536a73ef2c82ce04059dc61c65e85a355561:
irqchip/mbigen: Unify the error handling in mbigen_of_create_domain() (2023-05-16 11:19:29 +0100)
----------------------------------------------------------------
irqchip fixes for 6.4, take #1
- MIPS GIC fixes for issues that could result in either
loss of state in the interrupt controller, or a deadlock
- Workaround for Mediatek Chromebooks that only save/restore
partial state when turning the GIC redistributors off,
resulting if fireworks if Linux uses interrupt priorities
for pseudo-NMIs
- Fix the MBIGEN error handling on init
- Mark meson-gpio OF data structures as __maybe_unused,
avoiding compilation warnings on non-OF setups
----------------------------------------------------------------
Douglas Anderson (2):
dt-bindings: interrupt-controller: arm,gic-v3: Add quirk for Mediatek SoCs w/ broken FW
irqchip/gic-v3: Disable pseudo NMIs on Mediatek devices w/ firmware issues
Jiaxun Yang (2):
irqchip/mips-gic: Don't touch vl_map if a local interrupt is not routable
irqchip/mips-gic: Use raw spinlock for gic_lock
Kefeng Wang (1):
irqchip/mbigen: Unify the error handling in mbigen_of_create_domain()
Krzysztof Kozlowski (1):
irqchip/meson-gpio: Mark OF related data as maybe unused
.../bindings/interrupt-controller/arm,gic-v3.yaml | 6 ++++
drivers/irqchip/irq-gic-common.c | 8 ++++--
drivers/irqchip/irq-gic-common.h | 1 +
drivers/irqchip/irq-gic-v3.c | 20 ++++++++++++++
drivers/irqchip/irq-mbigen.c | 31 ++++++++++++---------
drivers/irqchip/irq-meson-gpio.c | 2 +-
drivers/irqchip/irq-mips-gic.c | 32 ++++++++++++----------
7 files changed, 69 insertions(+), 31 deletions(-)
next reply other threads:[~2023-05-21 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 10:18 Marc Zyngier [this message]
2023-05-22 6:21 ` [tip: irq/urgent] Merge tag 'irqchip-fixes-6.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent tip-bot2 for Thomas Gleixner
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=20230521101812.2520740-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dianders@chromium.org \
--cc=fancer.lancer@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=jwerner@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.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).