From: Kishon Vijay Abraham I <kishon@ti.com>
To: Tobias Regnery <tobias.regnery@gmail.com>,
<vivek.gautam@codeaurora.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] phy: qcom-qusb2: add NVMEM dependency
Date: Mon, 10 Apr 2017 16:01:31 +0530 [thread overview]
Message-ID: <40d4fd70-01ca-fff7-a5c6-7fdab1ee58d8@ti.com> (raw)
In-Reply-To: <20170410095242.20064-1-tobias.regnery@gmail.com>
On Monday 10 April 2017 03:22 PM, Tobias Regnery wrote:
> With CONFIG_NVMEM=m and CONFIG_PHY_QCOM_QUSB2=y we get a link error from
> calls to devm_nvmem_cell_get and nvmem_cell_read:
>
> drivers/built-in.o: In function `qusb2_phy_probe':
> binder.c:(.text+0x4750): undefined reference to `devm_nvmem_cell_get'
> drivers/built-in.o: In function `qusb2_phy_init':
> binder.c:(.text+0x489c): undefined reference to `nvmem_cell_read'
>
> Fix this by adding a Kconfig dependency to ensure we can only have this
> driver built in when the nvmem functions are also built in or we see the
> empty stub functions. We can still build this driver as a module when the
> nvmem core is build as module, too.
>
> Fixes: deffad633413 ("phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips")
> Signed-off-by: Tobias Regnery <tobias.regnery@gmail.com>
merged, thanks!
-Kishon
> ---
> drivers/phy/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
> index c120071fd2c8..30a2a612ff20 100644
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
> @@ -450,6 +450,7 @@ config PHY_QCOM_QMP
> config PHY_QCOM_QUSB2
> tristate "Qualcomm QUSB2 PHY Driver"
> depends on OF && (ARCH_QCOM || COMPILE_TEST)
> + depends on NVMEM || !NVMEM
> select GENERIC_PHY
> help
> Enable this to support the HighSpeed QUSB2 PHY transceiver for USB
>
prev parent reply other threads:[~2017-04-10 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 9:52 Tobias Regnery
2017-04-10 10:31 ` Kishon Vijay Abraham I [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=40d4fd70-01ca-fff7-a5c6-7fdab1ee58d8@ti.com \
--to=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tobias.regnery@gmail.com \
--cc=vivek.gautam@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
all inboxes | Powered by JetHome®