From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: soc@kernel.org, Arnd Bergmann <arnd@arndb.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: [GIT PULL] SOC FSL for 6.20
Date: Tue, 14 Apr 2026 16:08:54 +0200 [thread overview]
Message-ID: <69cdadd6-523c-4a79-8cb3-1deff5910699@kernel.org> (raw)
Hi Arnd,
Please pull the following Freescale Soc Drivers changes for 7.1
Changes to fsl-mc bus are reviewed or acked by Ioana Ciornei.
Thanks
Christophe
The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/chleroy/linux
tags/soc_fsl-7.1-1
for you to fetch changes up to 1bc2b368e0338bf1a977502d6c4716c888d1fbdb:
bus: fsl-mc: wait for the MC firmware to complete its boot
(2026-04-14 08:01:09 +0200)
----------------------------------------------------------------
FSL SOC Changes for 7.1
Freescale QUICC Engine:
- Add missing cleanup on device removal and switch to
irq_domain_create_linear()
in interrupt controller for IO Ports
- Panic on ioremap() failure in qe_reset()
Freescale Management Complex:
- Move fsl-mc over to device MSI infrastructure
- Wait for the MC firmware to complete its boot
Freescale Hypervisor:
- Fix header kernel-doc warnings
----------------------------------------------------------------
Christophe Leroy (CS GROUP) (1):
soc: fsl: qe_ports_ic: switch to irq_domain_create_linear()
Felix Gu (1):
soc: fsl: qe_ports_ic: Add missing cleanup on device removal
Ioana Ciornei (1):
bus: fsl-mc: wait for the MC firmware to complete its boot
Marc Zyngier (6):
fsl-mc: Remove MSI domain propagation to sub-devices
fsl-mc: Add minimal infrastructure to use platform MSI
irqchip/gic-v3-its: Add fsl_mc device plumbing to the msi-parent
handling
fsl-mc: Switch over to per-device platform MSI
fsl-mc: Remove legacy MSI implementation
platform-msi: Remove stale comment
Randy Dunlap (1):
virt: fsl_hypervisor: fix header kernel-doc warnings
Wang Jun (1):
soc: fsl: qe: panic on ioremap() failure in qe_reset()
drivers/base/platform-msi.c | 4 -
drivers/bus/fsl-mc/dprc-driver.c | 14 +--
drivers/bus/fsl-mc/fsl-mc-bus.c | 50 ++++++++-
drivers/bus/fsl-mc/fsl-mc-msi.c | 166
+++++----------------------
drivers/bus/fsl-mc/fsl-mc-private.h | 2 +-
drivers/irqchip/Kconfig | 6 -
drivers/irqchip/Makefile | 1 -
drivers/irqchip/irq-gic-its-msi-parent.c | 7 +-
drivers/irqchip/irq-gic-v3-its-fsl-mc-msi.c | 168
----------------------------
drivers/soc/fsl/qe/qe.c | 3 +
drivers/soc/fsl/qe/qe_ports_ic.c | 23 ++--
include/linux/fsl/mc.h | 6 +-
include/linux/irqdomain_defs.h | 1 -
include/uapi/linux/fsl_hypervisor.h | 4 +-
14 files changed, 106 insertions(+), 349 deletions(-)
delete mode 100644 drivers/irqchip/irq-gic-v3-its-fsl-mc-msi.c
next reply other threads:[~2026-04-14 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 14:08 Christophe Leroy (CS GROUP) [this message]
2026-04-14 14:55 ` [GIT PULL] SOC FSL for 6.20 Arnd Bergmann
2026-04-14 15:02 ` Christophe Leroy (CS GROUP)
2026-04-14 15:13 ` Christophe Leroy (CS GROUP)
-- strict thread matches above, loose matches on Subject: below --
2026-01-31 7:38 Christophe Leroy (CS GROUP)
2026-02-04 12:30 ` patchwork-bot+linux-soc
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=69cdadd6-523c-4a79-8cb3-1deff5910699@kernel.org \
--to=chleroy@kernel.org \
--cc=arnd@arndb.de \
--cc=ioana.ciornei@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
/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