From: Kishon Vijay Abraham I <kishon@ti.com>
To: "Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>,
"Vivek Gautam" <vivek.gautam@codeaurora.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] phy: qcom-qmp: select COMMON_CLK
Date: Mon, 10 Apr 2017 10:31:57 +0530 [thread overview]
Message-ID: <bcb76eb8-586c-0ff8-4cae-ce4d75472ed8@ti.com> (raw)
In-Reply-To: <20170409211539.12680-1-jeremy.lefaure@lse.epita.fr>
Hi,
On Monday 10 April 2017 02:45 AM, Jérémy Lefaure wrote:
> It is impossible to build Qualcom QMP phy driver without COMMON_CLK
> enabled:
> CC drivers/phy/phy-qcom-qmp.o
> drivers/phy/phy-qcom-qmp.c: In function ‘phy_pipe_clk_register’:
> drivers/phy/phy-qcom-qmp.c:932:9: error: variable ‘init’ has initializer
> but incomplete type
> struct clk_init_data init = { };
> ^~~~~~~~~~~~~
> drivers/phy/phy-qcom-qmp.c:932:23: error: storage size of ‘init’ isn’t
> known
> struct clk_init_data init = { };
> ^~~~
> ...
>
> Selecting COMMON_CLK when PHY_QCOM_QMP is enabled fix this issue.
>
> Fixes: 93a8c0c7b1ad ("phy: qcom-qmp: new qmp phy driver for qcom-chipsets")
> Signed-off-by: Jérémy Lefaure <jeremy.lefaure@lse.epita.fr>
Vivek has already sent a patch for this. I have picked that.
Thanks
Kishon
> ---
> drivers/phy/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
> index c120071fd2c8..e881eb2ef305 100644
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
> @@ -443,6 +443,7 @@ config PHY_QCOM_QMP
> tristate "Qualcomm QMP PHY Driver"
> depends on OF && (ARCH_QCOM || COMPILE_TEST)
> select GENERIC_PHY
> + select COMMON_CLK
> help
> Enable this to support the QMP PHY transceiver that is used
> with controllers such as PCIe, UFS, and USB on Qualcomm chips.
>
prev parent reply other threads:[~2017-04-10 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 21:15 Jérémy Lefaure
2017-04-10 5:01 ` 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=bcb76eb8-586c-0ff8-4cae-ce4d75472ed8@ti.com \
--to=kishon@ti.com \
--cc=jeremy.lefaure@lse.epita.fr \
--cc=linux-kernel@vger.kernel.org \
--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®