From: "irqchip-bot for Geert Uytterhoeven" <tip-bot2@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Marc Zyngier <maz@kernel.org>,
tglx@linutronix.de
Subject: [irqchip: irq/irqchip-fixes] irqchip: IMX_MU_MSI should depend on ARCH_MXC
Date: Wed, 12 Oct 2022 07:49:01 -0000 [thread overview]
Message-ID: <166556094146.401.3044335312264028864.tip-bot2@tip-bot2> (raw)
In-Reply-To: =?utf-8?q?=3C7f3bd932614ddbff46a1b750ef45b231130364ad=2E16649?= =?utf-8?q?00434=2Egit=2Egeert+renesas=40glider=2Ebe=3E?=
The following commit has been merged into the irq/irqchip-fixes branch of irqchip:
Commit-ID: 6c9f7434159b96231f5b27ab938f4766e3586b48
Gitweb: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms/6c9f7434159b96231f5b27ab938f4766e3586b48
Author: Geert Uytterhoeven <geert+renesas@glider.be>
AuthorDate: Tue, 04 Oct 2022 18:22:30 +02:00
Committer: Marc Zyngier <maz@kernel.org>
CommitterDate: Wed, 12 Oct 2022 08:43:59 +01:00
irqchip: IMX_MU_MSI should depend on ARCH_MXC
The Freescale/NXP i.MX Messaging Unit is only present on Freescale/NXP
i.MX SoCs. Hence add a dependency on ARCH_MXC, to prevent asking the
user about this driver when configuring a kernel without Freescale/NXP
i.MX SoC family support.
While at it, expand "MU" to "Messaging Unit" in the help text.
Fixes: 70afdab904d2d1e6 ("irqchip: Add IMX MU MSI controller driver")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/7f3bd932614ddbff46a1b750ef45b231130364ad.1664900434.git.geert+renesas@glider.be
---
drivers/irqchip/Kconfig | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
index 4d85a18..93d9901 100644
--- a/drivers/irqchip/Kconfig
+++ b/drivers/irqchip/Kconfig
@@ -484,14 +484,15 @@ config IMX_INTMUX
config IMX_MU_MSI
tristate "i.MX MU used as MSI controller"
depends on OF && HAS_IOMEM
+ depends on ARCH_MXC || COMPILE_TEST
default m if ARCH_MXC
select IRQ_DOMAIN
select IRQ_DOMAIN_HIERARCHY
select GENERIC_MSI_IRQ_DOMAIN
help
- Provide a driver for the MU block used as a CPU-to-CPU MSI
- controller. This requires a specially crafted DT to make use
- of this driver.
+ Provide a driver for the i.MX Messaging Unit block used as a
+ CPU-to-CPU MSI controller. This requires a specially crafted DT
+ to make use of this driver.
If unsure, say N
reply other threads:[~2022-10-12 7:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=166556094146.401.3044335312264028864.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--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
all inboxes | Powered by JetHome®