From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Rohit kumar <rohitkr@codeaurora.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: qcom q6v5: fix modular build
Date: Tue, 10 Jul 2018 14:08:16 -0700 [thread overview]
Message-ID: <20180710210816.GB21402@builder> (raw)
In-Reply-To: <20180706125804.3572356-1-arnd@arndb.de>
On Fri 06 Jul 05:57 PDT 2018, Arnd Bergmann wrote:
> The new driver only works as built-in code at the moment but fails
> with a link error when configured as a loadable module:
>
> WARNING: modpost: missing MODULE_LICENSE() in drivers/remoteproc/qcom_q6v5.o
> see include/linux/module.h for more information
> ERROR: "qcom_q6v5_init" [drivers/remoteproc/qcom_q6v5_pil.ko] undefined!
> ERROR: "qcom_q6v5_wait_for_start" [drivers/remoteproc/qcom_q6v5_pil.ko] undefined!
> ERROR: "qcom_q6v5_prepare" [drivers/remoteproc/qcom_q6v5_pil.ko] undefined!
> ERROR: "qcom_q6v5_unprepare" [drivers/remoteproc/qcom_q6v5_pil.ko] undefined!
> ERROR: "qcom_q6v5_request_stop" [drivers/remoteproc/qcom_q6v5_pil.ko] undefined!
> ERROR: "qcom_q6v5_init" [drivers/remoteproc/qcom_adsp_pil.ko] undefined!
> ERROR: "qcom_q6v5_wait_for_start" [drivers/remoteproc/qcom_adsp_pil.ko] undefined!
> ERROR: "qcom_q6v5_prepare" [drivers/remoteproc/qcom_adsp_pil.ko] undefined!
> ERROR: "qcom_q6v5_unprepare" [drivers/remoteproc/qcom_adsp_pil.ko] undefined!
> ERROR: "qcom_q6v5_request_stop" [drivers/remoteproc/qcom_adsp_pil.ko] undefined!
>
> This exports the internal symbols as needed and adds the MODULE_LICENSE()
> and MODULE_DESCRIPTION() tags. I could not figure out the author, so I
> did not add a MODULE_AUTHOR() tag for now.
>
> Fixes: 3b415c8fb263 ("remoteproc: q6v5: Extract common resource handling")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Thanks Arnd.
Regards,
Bjorn
> ---
> drivers/remoteproc/qcom_q6v5.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/remoteproc/qcom_q6v5.c b/drivers/remoteproc/qcom_q6v5.c
> index 400cdf936f6b..61a760ee4aac 100644
> --- a/drivers/remoteproc/qcom_q6v5.c
> +++ b/drivers/remoteproc/qcom_q6v5.c
> @@ -9,6 +9,7 @@
> #include <linux/kernel.h>
> #include <linux/platform_device.h>
> #include <linux/interrupt.h>
> +#include <linux/module.h>
> #include <linux/soc/qcom/smem.h>
> #include <linux/soc/qcom/smem_state.h>
> #include <linux/remoteproc.h>
> @@ -32,6 +33,7 @@ int qcom_q6v5_prepare(struct qcom_q6v5 *q6v5)
>
> return 0;
> }
> +EXPORT_SYMBOL_GPL(qcom_q6v5_prepare);
>
> /**
> * qcom_q6v5_unprepare() - unprepare the qcom_q6v5 context after stop
> @@ -45,6 +47,7 @@ int qcom_q6v5_unprepare(struct qcom_q6v5 *q6v5)
>
> return !q6v5->handover_issued;
> }
> +EXPORT_SYMBOL_GPL(qcom_q6v5_unprepare);
>
> static irqreturn_t q6v5_wdog_interrupt(int irq, void *data)
> {
> @@ -114,6 +117,7 @@ int qcom_q6v5_wait_for_start(struct qcom_q6v5 *q6v5, int timeout)
>
> return !ret ? -ETIMEDOUT : 0;
> }
> +EXPORT_SYMBOL_GPL(qcom_q6v5_wait_for_start);
>
> static irqreturn_t q6v5_handover_interrupt(int irq, void *data)
> {
> @@ -157,6 +161,7 @@ int qcom_q6v5_request_stop(struct qcom_q6v5 *q6v5)
>
> return ret == 0 ? -ETIMEDOUT : 0;
> }
> +EXPORT_SYMBOL_GPL(qcom_q6v5_request_stop);
>
> /**
> * qcom_q6v5_init() - initializer of the q6v5 common struct
> @@ -241,3 +246,7 @@ int qcom_q6v5_init(struct qcom_q6v5 *q6v5, struct platform_device *pdev,
>
> return 0;
> }
> +EXPORT_SYMBOL_GPL(qcom_q6v5_init);
> +
> +MODULE_LICENSE("GPL v2");
> +MODULE_DESCRIPTION("Qualcomm Peripheral Image Loader for Q6V5");
> --
> 2.9.0
>
prev parent reply other threads:[~2018-07-10 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 12:57 [PATCH] remoteproc: qcom q6v5: fix modular build Arnd Bergmann
2018-07-10 21:08 ` 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=20180710210816.GB21402@builder \
--to=bjorn.andersson@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=rohitkr@codeaurora.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