From: Andrew Davis <afd@ti.com>
To: Guillaume La Roque <glaroque@baylibre.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <vishalm@ti.com>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Nicolas Frayer <nfrayer@baylibre.com>
Subject: Re: [PATCH v3 2/2] irqchip: Kconfig: Added module build support for the TI interrupt aggregator
Date: Wed, 16 Oct 2024 08:48:02 -0500 [thread overview]
Message-ID: <0c2ae869-d04f-481d-b770-ec54f4d2e658@ti.com> (raw)
In-Reply-To: <20241016-timodules-v3-2-fa71091ade98@baylibre.com>
On 10/16/24 4:41 AM, Guillaume La Roque wrote:
> From: Nicolas Frayer <nfrayer@baylibre.com>
>
> Added module build support in Kconfig for the TI SCI interrupt aggregator
> driver. The driver's default build is built-in and it also depends on
> ARCH_K3 as the driver uses some 64 bit ops and should only be built
> for 64 bit platforms.
>
> Signed-off-by: Nicolas Frayer <nfrayer@baylibre.com>
> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
> ---
> arch/arm64/Kconfig.platforms | 1 -
> drivers/irqchip/Kconfig | 5 +++--
> drivers/irqchip/irq-ti-sci-inta.c | 1 +
> 3 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 393845a3ae5c..9dea47decfbd 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -135,7 +135,6 @@ config ARCH_K3
> select SOC_TI
> select TI_MESSAGE_MANAGER
> select TI_SCI_PROTOCOL
> - select TI_SCI_INTA_IRQCHIP
> select TI_K3_SOCINFO
> help
> This enables support for Texas Instruments' K3 multicore SoC
> diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
> index a958731404e9..9646322345e4 100644
> --- a/drivers/irqchip/Kconfig
> +++ b/drivers/irqchip/Kconfig
> @@ -544,10 +544,11 @@ config TI_SCI_INTR_IRQCHIP
> TI System Controller, say Y here. Otherwise, say N.
>
> config TI_SCI_INTA_IRQCHIP
> - bool
> - depends on TI_SCI_PROTOCOL
> + tristate "TI SCI INTA Interrupt Controller"
> + depends on ARCH_K3 && TI_SCI_PROTOCOL
You can still compile test, just gate it on 64BIT (or ARM64 if those
64bit ops are only available on ARM64).
depends on ARCH_K3 || (COMPILE_TEST && ARM64)
BTW, the last time this was posted the feedback was that if this
was compiled as a module we might have issues with dependent drivers
not having this IRQ ready as it may be loaded later. I think this
would only cause probe defers if the drivers are well behaving, but
something to double check.
Andrew
> select IRQ_DOMAIN_HIERARCHY
> select TI_SCI_INTA_MSI_DOMAIN
> + default ARCH_K3
> help
> This enables the irqchip driver support for K3 Interrupt aggregator
> over TI System Control Interface available on some new TI's SoCs.
> diff --git a/drivers/irqchip/irq-ti-sci-inta.c b/drivers/irqchip/irq-ti-sci-inta.c
> index b83f5cbab123..a887efba262c 100644
> --- a/drivers/irqchip/irq-ti-sci-inta.c
> +++ b/drivers/irqchip/irq-ti-sci-inta.c
> @@ -743,3 +743,4 @@ module_platform_driver(ti_sci_inta_irq_domain_driver);
>
> MODULE_AUTHOR("Lokesh Vutla <lokeshvutla@ti.com>");
> MODULE_DESCRIPTION("K3 Interrupt Aggregator driver over TI SCI protocol");
> +MODULE_LICENSE("GPL");
>
next prev parent reply other threads:[~2024-10-16 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 9:41 [PATCH v3 0/2] irqchip: Kconfig: Add module support for TI inta/intr Guillaume La Roque
2024-10-16 9:41 ` [PATCH v3 1/2] irqchip: Kconfig: module build support for the TI interrupt router driver Guillaume La Roque
2024-10-16 13:37 ` Andrew Davis
2024-10-16 14:18 ` Guillaume LA ROQUE
2024-10-16 14:26 ` Andrew Davis
2024-10-16 16:38 ` Thomas Gleixner
2024-10-16 18:32 ` Guillaume LA ROQUE
2024-10-16 9:41 ` [PATCH v3 2/2] irqchip: Kconfig: Added module build support for the TI interrupt aggregator Guillaume La Roque
2024-10-16 13:48 ` Andrew Davis [this message]
2024-10-18 8:01 ` Guillaume LA ROQUE
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=0c2ae869-d04f-481d-b770-ec54f4d2e658@ti.com \
--to=afd@ti.com \
--cc=catalin.marinas@arm.com \
--cc=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkorpershoek@baylibre.com \
--cc=nfrayer@baylibre.com \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
--cc=tglx@linutronix.de \
--cc=vishalm@ti.com \
--cc=will@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