From: Nishanth Menon <nm@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
linux-kernel@vger.kernel.org, Marc Zyngier <marc.zyngier@arm.com>,
Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] soc: ti: fix irq-ti-sci link error
Date: Mon, 17 Jun 2019 10:43:42 -0500 [thread overview]
Message-ID: <20190617154342.n2tre474cfyvraw3@kahuna> (raw)
In-Reply-To: <20190617130149.1782930-1-arnd@arndb.de>
On 15:01-20190617, Arnd Bergmann wrote:
> The irqchip driver depends on the SoC specific driver, but we want
> to be able to compile-test it elsewhere:
>
> WARNING: unmet direct dependencies detected for TI_SCI_INTA_MSI_DOMAIN
> Depends on [n]: SOC_TI [=n]
> Selected by [y]:
> - TI_SCI_INTA_IRQCHIP [=y] && TI_SCI_PROTOCOL [=y]
>
> drivers/irqchip/irq-ti-sci-inta.o: In function `ti_sci_inta_irq_domain_probe':
> irq-ti-sci-inta.c:(.text+0x204): undefined reference to `ti_sci_inta_msi_create_irq_domain'
>
> Rearrange the Kconfig and Makefile so we build the soc driver whenever
> its users are there, regardless of the SOC_TI option.
>
> Fixes: 49b323157bf1 ("soc: ti: Add MSI domain bus support for Interrupt Aggregator")
> Fixes: f011df6179bd ("irqchip/ti-sci-inta: Add msi domain support")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/soc/Makefile | 2 +-
> drivers/soc/ti/Kconfig | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/soc/Makefile b/drivers/soc/Makefile
> index 524ecdc2a9bb..2ec355003524 100644
> --- a/drivers/soc/Makefile
> +++ b/drivers/soc/Makefile
> @@ -22,7 +22,7 @@ obj-$(CONFIG_ARCH_ROCKCHIP) += rockchip/
> obj-$(CONFIG_SOC_SAMSUNG) += samsung/
> obj-y += sunxi/
> obj-$(CONFIG_ARCH_TEGRA) += tegra/
> -obj-$(CONFIG_SOC_TI) += ti/
> +obj-y += ti/
> obj-$(CONFIG_ARCH_U8500) += ux500/
> obj-$(CONFIG_PLAT_VERSATILE) += versatile/
> obj-y += xilinx/
> diff --git a/drivers/soc/ti/Kconfig b/drivers/soc/ti/Kconfig
> index ea0859f7b185..d7d50d48d05d 100644
> --- a/drivers/soc/ti/Kconfig
> +++ b/drivers/soc/ti/Kconfig
> @@ -75,10 +75,10 @@ config TI_SCI_PM_DOMAINS
> called ti_sci_pm_domains. Note this is needed early in boot before
> rootfs may be available.
>
> +endif # SOC_TI
> +
> config TI_SCI_INTA_MSI_DOMAIN
> bool
> select GENERIC_MSI_IRQ_DOMAIN
> help
> Driver to enable Interrupt Aggregator specific MSI Domain.
> -
> -endif # SOC_TI
> --
> 2.20.0
>
Looks fine to me. Lokesh?
--
Regards,
Nishanth Menon
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-17 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 13:01 [PATCH] soc: ti: fix irq-ti-sci link error Arnd Bergmann
2019-06-17 15:43 ` Nishanth Menon [this message]
2019-07-01 10:46 ` Lokesh Vutla
2019-07-01 17:36 ` santosh.shilimkar
2019-07-01 22:24 ` Olof Johansson
2019-07-02 1:30 ` santosh.shilimkar
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=20190617154342.n2tre474cfyvraw3@kahuna \
--to=nm@ti.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=marc.zyngier@arm.com \
--cc=olof@lixom.net \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).