From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Vinod Koul <vinod.koul@intel.com>,
Peter Griffin <peter.griffin@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: wcnss-pil: add QCOM_SMD dependency
Date: Fri, 18 Nov 2016 09:05:49 -0800 [thread overview]
Message-ID: <20161118170549.GB2769@tuxbot> (raw)
In-Reply-To: <20161118161528.775709-1-arnd@arndb.de>
On Fri 18 Nov 08:15 PST 2016, Arnd Bergmann wrote:
> When qcom_smd is a loadable module and adsp-pil is built-in,
> we get a link error:
>
> drivers/remoteproc/qcom_wcnss_pil.o: In function `wcnss_smd_remove':
> qcom_wcnss_iris.c:(.text.wcnss_smd_remove+0x10): undefined reference to `qcom_smd_unregister_edge'
> drivers/remoteproc/qcom_wcnss_pil.o: In function `wcnss_smd_probe':
> qcom_wcnss_iris.c:(.text.wcnss_smd_probe+0x12): undefined reference to `qcom_smd_register_edge'
>
> This adds a Kconfig dependency to avoid this. We can still allow
> build-testing with SMD disabled.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied
Thanks,
Bjorn
> ---
> drivers/remoteproc/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
> index 5a0019ce7555..677b3fede83d 100644
> --- a/drivers/remoteproc/Kconfig
> +++ b/drivers/remoteproc/Kconfig
> @@ -106,6 +106,7 @@ config QCOM_Q6V5_PIL
> config QCOM_WCNSS_PIL
> tristate "Qualcomm WCNSS Peripheral Image Loader"
> depends on OF && ARCH_QCOM
> + depends on QCOM_SMD || (COMPILE_TEST && QCOM_SMD = n)
> depends on QCOM_SMEM
> depends on REMOTEPROC
> select QCOM_MDT_LOADER
> --
> 2.9.0
>
prev parent reply other threads:[~2016-11-18 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 16:15 [PATCH] remoteproc: wcnss-pil: add QCOM_SMD dependency Arnd Bergmann
2016-11-18 17:05 ` Bjorn Andersson [this message]
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=20161118170549.GB2769@tuxbot \
--to=bjorn.andersson@linaro.org \
--cc=arnd@arndb.de \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=peter.griffin@linaro.org \
--cc=vinod.koul@intel.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).