summaryrefslogtreecommitdiff
path: root/drivers/bcma/README
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2017-09-11 22:54:17 +0300
committerBjorn Andersson <bjorn.andersson@linaro.org>2017-10-10 21:28:20 +0300
commitab759b9732fd8a4ae0252bb2087e90d776f74b9f (patch)
treed06f82c1cae3501a66ac9479888d135591e5c343 /drivers/bcma/README
parent68c2d645ebbd4a636cf93ed56f15912bcf9376bc (diff)
downloadlinux-ab759b9732fd8a4ae0252bb2087e90d776f74b9f.tar.xz
remoteproc: qcom: fix RPMSG_QCOM_GLINK_SMEM dependencies
When RPMSG_QCOM_GLINK_SMEM=m and one driver causes the qcom_common.c file to be compiled as built-in, we get a link error: drivers/remoteproc/qcom_common.o: In function `glink_subdev_remove': qcom_common.c:(.text+0x130): undefined reference to `qcom_glink_smem_unregister' qcom_common.c:(.text+0x130): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `qcom_glink_smem_unregister' drivers/remoteproc/qcom_common.o: In function `glink_subdev_probe': qcom_common.c:(.text+0x160): undefined reference to `qcom_glink_smem_register' qcom_common.c:(.text+0x160): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `qcom_glink_smem_register' Out of the three PIL driver instances, QCOM_ADSP_PIL already has a Kconfig dependency to prevent this from happening, but the other two do not. This adds the same dependency there. Fixes: eea07023e6d9 ("remoteproc: qcom: adsp: Allow defining GLINK edge") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Diffstat (limited to 'drivers/bcma/README')
0 files changed, 0 insertions, 0 deletions