From: Daniel Palmer <daniel@0x0f.com>
To: linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, mark-pk.tsai@mediatek.com,
arnd@arndb.de, maz@kernel.org, linux-kernel@vger.kernel.org,
Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH 1/3] ARM: mstar: Select MStar intc
Date: Fri, 18 Sep 2020 19:49:47 +0900 [thread overview]
Message-ID: <20200918104949.3260823-2-daniel@0x0f.com> (raw)
In-Reply-To: <20200918104949.3260823-1-daniel@0x0f.com>
MediaTek recently introduced support for the MStar interrupt
controller that is also present in some of their chips as well
as the MStar/Sigmastar chips.
Almost all of the peripheral interrupts go through an instance of
this controller in MStar/SigmaStar Arm v7 chips so we want to select
it if CONFIG_ARCH_MSTARV7 is selected.
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
arch/arm/mach-mstar/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-mstar/Kconfig b/arch/arm/mach-mstar/Kconfig
index 52744fe32368..576d1ab293c8 100644
--- a/arch/arm/mach-mstar/Kconfig
+++ b/arch/arm/mach-mstar/Kconfig
@@ -3,6 +3,7 @@ menuconfig ARCH_MSTARV7
depends on ARCH_MULTI_V7
select ARM_GIC
select ARM_HEAVY_MB
+ select MST_IRQ
help
Support for newer MStar/Sigmastar SoC families that are
based on Armv7 cores like the Cortex A7 and share the same
--
2.27.0
next prev parent reply other threads:[~2020-09-18 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 10:49 [PATCH 0/3] ARM: mstar: wire up interrupt controllers Daniel Palmer
2020-09-18 10:49 ` Daniel Palmer [this message]
2020-09-18 10:49 ` [PATCH 2/3] ARM: mstar: Add interrupt controller to base dtsi Daniel Palmer
2020-09-18 10:49 ` [PATCH 3/3] ARM: mstar: Add interrupt to pm_uart Daniel Palmer
2020-09-18 11:34 ` [PATCH 0/3] ARM: mstar: wire up interrupt controllers Arnd Bergmann
2020-09-18 11:43 ` Daniel Palmer
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=20200918104949.3260823-2-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=maz@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