2019-05-19 20:07:45 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2014-04-29 07:03:20 +08:00
|
|
|
menuconfig ARCH_SUNXI
|
ARM: use "depends on" for SoC configs instead of "if" after prompt
Many ARM sub-architectures use prompts followed by "if" conditional,
but it is wrong.
Please notice the difference between
config ARCH_FOO
bool "Foo SoCs" if ARCH_MULTI_V7
and
config ARCH_FOO
bool "Foo SoCs"
depends on ARCH_MULTI_V7
These two are *not* equivalent!
In the former statement, it is not ARCH_FOO, but its prompt that
depends on ARCH_MULTI_V7. So, it is completely valid that ARCH_FOO
is selected by another, but ARCH_MULTI_V7 is still disabled. As it is
not unmet dependency, Kconfig never warns. This is probably not what
you want.
The former should be used only when you need to do so, and you really
understand what you are doing. (In most cases, it should be wrong!)
For enabling/disabling sub-architectures, the latter is always correct.
As a good side effect, this commit fixes some entries over 80 columns
(mach-imx, mach-integrator, mach-mbevu).
[Arnd: I note that there is not really a bug here, according to
the discussion that followed, but I can see value in being consistent
and in making the lines shorter]
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Acked-by: Heiko Stuebner <heiko@sntech.de>
Acked-by: Patrice Chotard <patrice.chotard@st.com>
Acked-by: Liviu Dudau <Liviu.Dudau@arm.com>
Acked-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Acked-by: Jun Nie <jun.nie@linaro.org>
Acked-by: Matthias Brugger <matthias.bgg@gmail.com>
Acked-by: Simon Horman <horms+renesas@verge.net.au>
Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Acked-by: Shawn Guo <shawnguo@kernel.org>
Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Acked-by: Thierry Reding <treding@nvidia.com>
Acked-by: Krzysztof Halasa <khc@piap.pl>
Acked-by: Maxime Coquelin <maxime.coquelin@st.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2015-11-16 11:06:10 +08:00
|
|
|
bool "Allwinner SoCs"
|
2018-12-03 04:23:37 +08:00
|
|
|
depends on ARCH_MULTI_V5 || ARCH_MULTI_V7
|
2015-02-09 18:23:20 +08:00
|
|
|
select ARCH_HAS_RESET_CONTROLLER
|
2012-11-08 19:40:16 +08:00
|
|
|
select CLKSRC_MMIO
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
2016-06-02 20:10:16 +08:00
|
|
|
select GPIOLIB
|
irqchip/sun6i-r: Use a stacked irqchip driver
The R_INTC in the A31 and newer sun8i/sun50i SoCs is more similar to the
original sun4i interrupt controller than the sun7i/sun9i NMI controller.
It is used for two distinct purposes:
- To control the trigger, latch, and mask for the NMI input pin
- To provide the interrupt input for the ARISC coprocessor
As this interrupt controller is not documented, information about it
comes from vendor-provided firmware blobs and from experimentation.
Differences from the sun4i interrupt controller appear to be:
- It only has one or two registers of each kind (max 32 or 64 IRQs)
- Multiplexing logic is added to support additional inputs
- There is no FIQ-related logic
- There is no interrupt priority logic
In order to fulfill its two purposes, this hardware block combines four
types of IRQs. First, the NMI pin is routed to the "IRQ 0" input on this
chip, with a trigger type controlled by the NMI_CTRL_REG. The "IRQ 0
pending" output from this chip, if enabled, is then routed to a SPI IRQ
input on the GIC. In other words, bit 0 of IRQ_ENABLE_REG *does* affect
the NMI IRQ seen at the GIC.
The NMI is followed by a contiguous block of 15 "direct" (my name for
them) IRQ inputs that are connected in parallel to both R_INTC and the
GIC. Or in other words, these bits of IRQ_ENABLE_REG *do not* affect the
IRQs seen at the GIC.
Following the direct IRQs are the ARISC's copy of banked IRQs for shared
peripherals. These are not relevant to Linux. The remaining IRQs are
connected to a multiplexer and provide access to the first (up to) 128
SPIs from the ARISC. This range of SPIs overlaps with the direct IRQs.
Because of the 1:1 correspondence between R_INTC and GIC inputs, this is
a perfect scenario for using a stacked irqchip driver. We want to hook
into setting the NMI trigger type, but not actually handle any IRQ here.
To allow access to all multiplexed IRQs, this driver requires a new
binding where the interrupt number matches the GIC interrupt number.
(This moves the NMI from number 0 to 32 or 96, depending on the SoC.)
For simplicity, copy the three-cell GIC binding; this disambiguates
interrupt 0 in the old binding (the NMI) from interrupt 0 in the new
binding (SPI 0) by the number of cells.
Since R_INTC is in the always-on power domain, and its output is visible
to the power management coprocessor, a stacked irqchip driver provides a
simple way to add wakeup support to any of its IRQs. That is the next
patch; for now, just the NMI is moved over.
This commit mostly reverts commit 173bda53b340 ("irqchip/sunxi-nmi:
Support sun6i-a31-r-intc compatible").
Acked-by: Maxime Ripard <mripard@kernel.org>
Signed-off-by: Samuel Holland <samuel@sholland.org>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20210118055040.21910-4-samuel@sholland.org
2021-01-18 13:50:33 +08:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
|
|
|
|
select IRQ_FASTEOI_HIERARCHY_HANDLERS
|
2012-11-08 19:40:16 +08:00
|
|
|
select PINCTRL
|
2017-02-10 00:39:21 +08:00
|
|
|
select PM_OPP
|
2013-03-24 18:49:25 +08:00
|
|
|
select SUN4I_TIMER
|
2015-02-09 18:23:20 +08:00
|
|
|
select RESET_CONTROLLER
|
2018-12-03 04:23:35 +08:00
|
|
|
help
|
|
|
|
|
Support for Allwinner ARM-based family of processors
|
2014-04-29 07:03:20 +08:00
|
|
|
|
|
|
|
|
if ARCH_SUNXI
|
|
|
|
|
|
2018-12-03 04:23:35 +08:00
|
|
|
if ARCH_MULTI_V7
|
|
|
|
|
|
2014-04-29 07:03:20 +08:00
|
|
|
config MACH_SUN4I
|
|
|
|
|
bool "Allwinner A10 (sun4i) SoCs support"
|
|
|
|
|
default ARCH_SUNXI
|
|
|
|
|
|
|
|
|
|
config MACH_SUN5I
|
|
|
|
|
bool "Allwinner A10s / A13 (sun5i) SoCs support"
|
|
|
|
|
default ARCH_SUNXI
|
|
|
|
|
select SUN5I_HSTIMER
|
|
|
|
|
|
|
|
|
|
config MACH_SUN6I
|
|
|
|
|
bool "Allwinner A31 (sun6i) SoCs support"
|
|
|
|
|
default ARCH_SUNXI
|
|
|
|
|
select ARM_GIC
|
2014-05-15 16:55:13 +08:00
|
|
|
select MFD_SUN6I_PRCM
|
2014-04-29 07:03:20 +08:00
|
|
|
select SUN5I_HSTIMER
|
|
|
|
|
|
|
|
|
|
config MACH_SUN7I
|
|
|
|
|
bool "Allwinner A20 (sun7i) SoCs support"
|
|
|
|
|
default ARCH_SUNXI
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select ARM_PSCI
|
2016-08-23 00:42:19 +08:00
|
|
|
select ARCH_SUPPORTS_BIG_ENDIAN
|
2014-04-29 07:03:20 +08:00
|
|
|
select HAVE_ARM_ARCH_TIMER
|
2013-11-07 19:01:48 +08:00
|
|
|
select SUN5I_HSTIMER
|
2014-04-29 07:03:20 +08:00
|
|
|
|
2014-06-20 22:52:50 +08:00
|
|
|
config MACH_SUN8I
|
2015-05-16 00:38:55 +08:00
|
|
|
bool "Allwinner sun8i Family SoCs support"
|
2014-06-20 22:52:50 +08:00
|
|
|
default ARCH_SUNXI
|
|
|
|
|
select ARM_GIC
|
2014-07-03 22:55:47 +08:00
|
|
|
select MFD_SUN6I_PRCM
|
2014-06-20 22:52:50 +08:00
|
|
|
|
2014-10-08 21:02:52 +08:00
|
|
|
config MACH_SUN9I
|
|
|
|
|
bool "Allwinner (sun9i) SoCs support"
|
|
|
|
|
default ARCH_SUNXI
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
|
2018-01-17 16:46:47 +08:00
|
|
|
config ARCH_SUNXI_MC_SMP
|
|
|
|
|
bool
|
|
|
|
|
depends on SMP
|
2018-05-05 03:05:43 +08:00
|
|
|
default MACH_SUN9I || MACH_SUN8I
|
2018-01-17 16:46:47 +08:00
|
|
|
select ARM_CCI400_PORT_CTRL
|
|
|
|
|
select ARM_CPU_SUSPEND
|
|
|
|
|
|
2014-04-29 07:03:20 +08:00
|
|
|
endif
|
2018-12-03 04:23:35 +08:00
|
|
|
|
2018-12-03 04:23:37 +08:00
|
|
|
if ARCH_MULTI_V5
|
|
|
|
|
|
|
|
|
|
config MACH_SUNIV
|
|
|
|
|
bool "Allwinner ARMv5 F-series (suniv) SoCs support"
|
|
|
|
|
default ARCH_SUNXI
|
|
|
|
|
help
|
|
|
|
|
Support for Allwinner suniv ARMv5 SoCs.
|
|
|
|
|
(F1C100A, F1C100s, F1C200s, F1C500, F1C600)
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2018-12-03 04:23:35 +08:00
|
|
|
endif
|