From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: Fix build error of missing devm_ioremap_resource on UM
Date: Thu, 3 Mar 2016 09:09:45 +0000 [thread overview]
Message-ID: <56D7FF59.9000005@linaro.org> (raw)
In-Reply-To: <1456993991-26119-1-git-send-email-k.kozlowski@samsung.com>
On 03/03/16 08:33, Krzysztof Kozlowski wrote:
> The devres.o gets linked if HAS_IOMEM is present so on ARCH=um
> allyesconfig (COMPILE_TEST) failed on many files with:
>
> drivers/built-in.o: In function `qfprom_probe':
> qfprom.c:(.text+0x4c5bcb): undefined reference to `devm_ioremap_resource'
>
> The users of devm_ioremap_resource() which are compile-testable should
> depend on HAS_IOMEM.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> ---
> drivers/nvmem/Kconfig | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
There is exactly same patch in the queue [1]
Could you send a patch just for MTK, others are taken care by [1]
[1]: http://lkml.iu.edu/hypermail/linux/kernel/1601.3/01577.html
thanks,
srini
> diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> index 5bd18cc1a69c..0843e4fd7e7a 100644
> --- a/drivers/nvmem/Kconfig
> +++ b/drivers/nvmem/Kconfig
> @@ -27,7 +27,7 @@ config NVMEM_IMX_OCOTP
>
> config NVMEM_LPC18XX_EEPROM
> tristate "NXP LPC18XX EEPROM Memory Support"
> - depends on ARCH_LPC18XX || COMPILE_TEST
> + depends on ARCH_LPC18XX || COMPILE_TEST && HAS_IOMEM
> help
> Say Y here to include support for NXP LPC18xx EEPROM memory found in
> NXP LPC185x/3x and LPC435x/3x/2x/1x devices.
> @@ -36,7 +36,7 @@ config NVMEM_LPC18XX_EEPROM
>
> config NVMEM_MXS_OCOTP
> tristate "Freescale MXS On-Chip OTP Memory Support"
> - depends on ARCH_MXS || COMPILE_TEST
> + depends on ARCH_MXS || COMPILE_TEST && HAS_IOMEM
> help
> If you say Y here, you will get readonly access to the
> One Time Programmable memory pages that are stored
> @@ -47,7 +47,7 @@ config NVMEM_MXS_OCOTP
>
> config MTK_EFUSE
> tristate "Mediatek SoCs EFUSE support"
> - depends on ARCH_MEDIATEK || COMPILE_TEST
> + depends on ARCH_MEDIATEK || COMPILE_TEST && HAS_IOMEM
> select REGMAP_MMIO
> help
> This is a driver to access hardware related data like sensor
> @@ -58,7 +58,7 @@ config MTK_EFUSE
>
> config QCOM_QFPROM
> tristate "QCOM QFPROM Support"
> - depends on ARCH_QCOM || COMPILE_TEST
> + depends on ARCH_QCOM || COMPILE_TEST && HAS_IOMEM
> select REGMAP_MMIO
> help
> Say y here to enable QFPROM support. The QFPROM provides access
> @@ -69,7 +69,7 @@ config QCOM_QFPROM
>
> config ROCKCHIP_EFUSE
> tristate "Rockchip eFuse Support"
> - depends on ARCH_ROCKCHIP || COMPILE_TEST
> + depends on ARCH_ROCKCHIP || COMPILE_TEST && HAS_IOMEM
> help
> This is a simple drive to dump specified values of Rockchip SoC
> from eFuse, such as cpu-leakage.
> @@ -90,7 +90,7 @@ config NVMEM_SUNXI_SID
>
> config NVMEM_VF610_OCOTP
> tristate "VF610 SoC OCOTP support"
> - depends on SOC_VF610 || COMPILE_TEST
> + depends on SOC_VF610 || COMPILE_TEST && HAS_IOMEM
> help
> This is a driver for the 'OCOTP' peripheral available on Vybrid
> devices like VF5xx and VF6xx.
>
next prev parent reply other threads:[~2016-03-03 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 8:33 [PATCH] nvmem: Fix build error of missing devm_ioremap_resource on UM Krzysztof Kozlowski
2016-03-03 9:09 ` Srinivas Kandagatla [this message]
2016-03-03 11:51 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2016-03-31 10:07 Srinivas Kandagatla
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=56D7FF59.9000005@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.