From: Nishanth Menon <nm@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Davis <afd@ti.com>, Arnd Bergmann <arnd@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Martyn Welch <martyn.welch@collabora.com>,
Hari Nagalla <hnagalla@ti.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mailbox, remoteproc: k3-m4+: fix compile testing
Date: Mon, 14 Oct 2024 11:52:38 -0500 [thread overview]
Message-ID: <20241014165238.nbllvtnxrxbwg344@frying> (raw)
In-Reply-To: <e6c84b91-20ce-474a-87f8-9faeb64f3724@app.fastmail.com>
On 15:43-20241014, Arnd Bergmann wrote:
> On Mon, Oct 14, 2024, at 14:56, Andrew Davis wrote:
> > On 10/7/24 8:23 AM, Arnd Bergmann wrote:
> >> 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.
>
> I generally agree, but the TI_SCI_PROTOCOL interface
> definitions that were added in aa276781a64a ("firmware: Add basic
> support for TI System Control Interface (TI-SCI) protocol")
> appear to explicitly support the case of compile-testing.
>
> See also 13678f3feb30 ("reset: ti-sci: honor TI_SCI_PROTOCOL
> setting when not 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
>
> That's certainly fine with me, but if we do this, I would suggest
> also removing the stub functions from
> include/linux/soc/ti/ti_sci_protocol.h, and the dependency in the
> reset driver.
>
> Adding Nishanth Menon to Cc, to see if he has a preference.
>
> Arnd
While I am OK to do the cleanups and make the drivers independent,
I am also looking to make TISCI stuff independent and be a module
itself. So, dropping the stubs will probably get in the way as we move
ahead with those plans.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-10-14 16:52 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 [this message]
2024-10-14 17:26 ` Andrew Davis
2024-10-15 11:47 ` Nishanth Menon
2024-10-16 15:26 ` Mathieu Poirier
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=20241014165238.nbllvtnxrxbwg344@frying \
--to=nm@ti.com \
--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 \
--cc=mathieu.poirier@linaro.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