From: Nagarjuna Kristam <nkristam@nvidia.com>
To: Corentin Labbe <clabbe@baylibre.com>, <jonathanh@nvidia.com>,
<kishon@ti.com>, <thierry.reding@gmail.com>, <treding@nvidia.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] phy: tegra: should select USB_PHY
Date: Mon, 23 Mar 2020 09:09:41 +0530 [thread overview]
Message-ID: <f720dc73-e6c3-ead7-6a45-6f2b54e0f4ff@nvidia.com> (raw)
In-Reply-To: <1584545013-19859-1-git-send-email-clabbe@baylibre.com>
Reviewed-by: Nagarjuna Kristam <nkristam@nvidia.com>
On 18-03-2020 20:53, Corentin Labbe wrote:
> External email: Use caution opening links or attachments
>
>
> I have hit the following build error:
> armv7a-hardfloat-linux-gnueabi-ld: drivers/phy/tegra/xusb.o: in function `tegra_xusb_port_unregister':
> xusb.c:(.text+0x2ac): undefined reference to `usb_remove_phy'
> armv7a-hardfloat-linux-gnueabi-ld: drivers/phy/tegra/xusb.o: in function `tegra_xusb_setup_ports':
> xusb.c:(.text+0xf30): undefined reference to `usb_add_phy_dev'
>
> PHY_TEGRA_XUSB should select USB_PHY
>
> Fixes: 23babe30fb45d ("phy: tegra: xusb: Add usb-phy support")
> Cc: stable <stable@vger.kernel.org>
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> ---
> drivers/phy/tegra/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/phy/tegra/Kconfig b/drivers/phy/tegra/Kconfig
> index df07c4dea059..a208aca4ba7b 100644
> --- a/drivers/phy/tegra/Kconfig
> +++ b/drivers/phy/tegra/Kconfig
> @@ -3,6 +3,7 @@ config PHY_TEGRA_XUSB
> tristate "NVIDIA Tegra XUSB pad controller driver"
> depends on ARCH_TEGRA
> select USB_CONN_GPIO
> + select USB_PHY
> help
> Choose this option if you have an NVIDIA Tegra SoC.
>
> --
> 2.24.1
>
prev parent reply other threads:[~2020-03-23 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 15:23 Corentin Labbe
2020-03-23 3:39 ` Nagarjuna Kristam [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=f720dc73-e6c3-ead7-6a45-6f2b54e0f4ff@nvidia.com \
--to=nkristam@nvidia.com \
--cc=clabbe@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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 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®