From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Andrew Davis <afd@ti.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Martyn Welch <martyn.welch@collabora.com>,
Hari Nagalla <hnagalla@ti.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mailbox, remoteproc: k3-m4+: fix compile testing
Date: Wed, 16 Oct 2024 09:26:24 -0600 [thread overview]
Message-ID: <Zw/bIItwk0jeqKoR@p14s> (raw)
In-Reply-To: <4d8a9786-ee4b-43b8-9207-e048c66349fe@ti.com>
On Mon, Oct 14, 2024 at 09:56:11AM -0500, Andrew Davis wrote:
> On 10/7/24 8:23 AM, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > The k3-m4 remoteproc driver was merged with incorrect dependencies.
> > Despite multiple people trying to fix this, the version 6.12-rc2
> > remains broken and causes a build failure with CONFIG_TI_SCI_PROTOCOL=m
> > when the driver is built-in.
> >
> > arm-linux-gnueabi-ld: drivers/remoteproc/ti_k3_m4_remoteproc.o: in function `k3_m4_rproc_probe':
> > ti_k3_m4_remoteproc.c:(.text.k3_m4_rproc_probe+0x76): undefined reference to `devm_ti_sci_get_by_phandle'
> >
> > Fix the dependency again to make it work in all configurations.
> > The 'select OMAP2PLUS_MBOX' no longer matches what the other drivers
> > dependencies. The link failure can be avoided with a simple 'depends
> > do, so turn that into the same 'depends' to ensure we get no circular
> > on TI_SCI_PROTOCOL', but the extra COMPILE_TEST alternative is what
> > we use elsehwere. On the other hand, building for OMAP2PLUS makes
> > no sense since the hardware only exists on K3.
> >
> > Fixes: ebcf9008a895 ("remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem")
> > Fixes: ba0c0cb56f22 ("remoteproc: k3-m4: use the proper dependencies")
> > Fixes: 54595f2807d2 ("mailbox, remoteproc: omap2+: fix compile testing")
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> > drivers/remoteproc/Kconfig | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
> > index 955e4e38477e..62f8548fb46a 100644
> > --- a/drivers/remoteproc/Kconfig
> > +++ b/drivers/remoteproc/Kconfig
> > @@ -341,9 +341,9 @@ config TI_K3_DSP_REMOTEPROC
> > config TI_K3_M4_REMOTEPROC
> > tristate "TI K3 M4 remoteproc support"
> > - depends on ARCH_OMAP2PLUS || ARCH_K3
> > - select MAILBOX
> > - select OMAP2PLUS_MBOX
> > + depends on ARCH_K3 || COMPILE_TEST
> > + depends on TI_SCI_PROTOCOL || (COMPILE_TEST && TI_SCI_PROTOCOL=n)
>
> This line is odd. IMHO "COMPILE_TEST" should only be added to ARCH_*
> dependencies, as often only one ARCH can be selected which prevents
> compile testing drivers with various multiple architecture deps in
> one compile test.
>
> Normal dependencies, on the other hand, can simply be enabled if one
> wants to compile test its dependent drivers. In this case, TI_SCI_PROTOCOL
> cannot be enabled as it has a dependency up the chain that doesn't
> allow selecting when not on a TI platform. We can fix that as I posted
> here[0]. With that fix in, this line can be simply become:
>
> depends on TI_SCI_PROTOCOL
From the above and the follow-on conversation with Nishanth, should I understand
you are working on a patchset to address this issue? If not I will apply Arnd's
patch. People are sending different fix [1] - the issue needs to be addressed
well before the end of the cycle.
[1]. https://lore.kernel.org/linux-arm-kernel/20241016013922.1392290-1-zengheng4@huawei.com/T/
>
> Andrew
>
> [0] https://lore.kernel.org/lkml/20241014144821.15094-1-afd@ti.com/
>
> > + depends on OMAP2PLUS_MBOX
> > help
> > Say m here to support TI's M4 remote processor subsystems
> > on various TI K3 family of SoCs through the remote processor
next prev parent reply other threads:[~2024-10-16 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 13:23 [PATCH] mailbox, remoteproc: k3-m4+: fix compile testing Arnd Bergmann
2024-10-08 14:12 ` Mathieu Poirier
2024-10-09 17:12 ` Mathieu Poirier
2024-10-14 14:56 ` Andrew Davis
2024-10-14 15:43 ` Arnd Bergmann
2024-10-14 16:52 ` Nishanth Menon
2024-10-14 17:26 ` Andrew Davis
2024-10-15 11:47 ` Nishanth Menon
2024-10-16 15:26 ` Mathieu Poirier [this message]
2024-10-16 15:37 ` Andrew Davis
2024-10-16 16:02 ` Mathieu Poirier
2024-10-16 16:43 ` Andrew Davis
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=Zw/bIItwk0jeqKoR@p14s \
--to=mathieu.poirier@linaro.org \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=hnagalla@ti.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=martyn.welch@collabora.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