From: Felipe Balbi <balbi@ti•com>
To: Stephen Warren <swarren@wwwdotorg•org>
Cc: balbi@ti•com, Venu Byravarasu <vbyravarasu@nvidia•com>,
USB list <linux-usb@vger•kernel.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-tegra@vger•kernel.org" <linux-tegra@vger•kernel.org>
Subject: Re: USB-related build errors on Tegra in next-20130319
Date: Wed, 20 Mar 2013 19:11:47 +0200 [thread overview]
Message-ID: <20130320171147.GM1567@arwen.pp.htv.fi> (raw)
In-Reply-To: <5149E925.7030302@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 3765 bytes --]
Hi,
On Wed, Mar 20, 2013 at 10:51:49AM -0600, Stephen Warren wrote:
> On 03/20/2013 10:45 AM, Felipe Balbi wrote:
> > Hi,
> >
> > On Wed, Mar 20, 2013 at 10:39:11AM -0600, Stephen Warren wrote:
> >> On 03/20/2013 06:20 AM, Felipe Balbi wrote:
> ...
> >> The patch you gave fixes the Kconfig warnings, but not the build
> >> failure.
> ...
> >> For now, I think the correct solution is to have USB_EHCI_TEGRA
> >> select USB_PHY. I validated that solves the build problem, and
> >> has the bonus of not needing any changes to tegra_defconfig.
> ...
> > Alright, do you want to send that patch ? My bad that I missed
> > that build error...
>
> Sure. Do you want to roll it into your patch and repost it, or me to
> send a separate patch?
updated patch below:
From c2b3334a624e4231952ab050e29445b8c62f662d Mon Sep 17 00:00:00 2001
From: Felipe Balbi <balbi@ti•com>
Date: Wed, 20 Mar 2013 14:18:28 +0200
Subject: [PATCH] arm: tegra: fix Kconfig select clauses
USB_ULPI and USB_ULPI_VIEWPORT shouldn't really
be selected directly by anyone, but since Tegra
still needs some time before turning ulpi viewport
into a proper PHY driver, we need to keep the
selects in place.
This patch just fixes the conditional select
so that it will continue to build after merging
the latest PHY layer changes.
Signed-off-by: Felipe Balbi <balbi@ti•com>
---
arch/arm/mach-tegra/Kconfig | 8 ++++----
drivers/usb/host/Kconfig | 1 +
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-tegra/Kconfig b/arch/arm/mach-tegra/Kconfig
index d1c4893..dbc653e 100644
--- a/arch/arm/mach-tegra/Kconfig
+++ b/arch/arm/mach-tegra/Kconfig
@@ -18,8 +18,8 @@ config ARCH_TEGRA_2x_SOC
select PL310_ERRATA_727915 if CACHE_L2X0
select PL310_ERRATA_769419 if CACHE_L2X0
select USB_ARCH_HAS_EHCI if USB_SUPPORT
- select USB_ULPI if USB
- select USB_ULPI_VIEWPORT if USB_SUPPORT
+ select USB_ULPI if USB_PHY
+ select USB_ULPI_VIEWPORT if USB_PHY
help
Support for NVIDIA Tegra AP20 and T20 processors, based on the
ARM CortexA9MP CPU and the ARM PL310 L2 cache controller
@@ -37,8 +37,8 @@ config ARCH_TEGRA_3x_SOC
select PINCTRL_TEGRA30
select PL310_ERRATA_769419 if CACHE_L2X0
select USB_ARCH_HAS_EHCI if USB_SUPPORT
- select USB_ULPI if USB
- select USB_ULPI_VIEWPORT if USB_SUPPORT
+ select USB_ULPI if USB_PHY
+ select USB_ULPI_VIEWPORT if USB_PHY
help
Support for NVIDIA Tegra T30 processor family, based on the
ARM CortexA9MP CPU and the ARM PL310 L2 cache controller
diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
index ba1347c..1b58587 100644
--- a/drivers/usb/host/Kconfig
+++ b/drivers/usb/host/Kconfig
@@ -179,6 +179,7 @@ config USB_EHCI_TEGRA
boolean "NVIDIA Tegra HCD support"
depends on USB_EHCI_HCD && ARCH_TEGRA
select USB_EHCI_ROOT_HUB_TT
+ select USB_PHY
help
This driver enables support for the internal USB Host Controllers
found in NVIDIA Tegra SoCs. The controllers are EHCI compliant.
--
1.8.2
Another possibility would be to:
select USB_PHY if USB
select USB_ULPI
select USB_ULPI_VIEWPORT
Would you prefer that one instead ?
> I assume you'd apply both to the same branch that contains the patches
> that add the USB_PHY config option? If the arch/arm patch gets applied
> to the Tegra tree instead, it'll cause breakage there since USB_PHY
> won't exist yet, so USB will be disabled until merged with the USB
> tree in 3.10-rc1.
alright, but I need your Acked-by to the updated patch. I have now
compiled it with tegra_defconfig (is that the one which should be used?)
and it's compiling fine without any issues.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-20 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 16:29 USB-related build errors on Tegra in next-20130319 Stephen Warren
2013-03-20 12:20 ` Felipe Balbi
[not found] ` <20130320122031.GI29659-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-03-20 16:39 ` Stephen Warren
[not found] ` <5149E62F.9090705-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-20 16:45 ` Felipe Balbi
[not found] ` <20130320164553.GL1567-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-03-20 16:51 ` Stephen Warren
2013-03-20 17:11 ` Felipe Balbi [this message]
2013-03-20 17:26 ` Stephen Warren
[not found] ` <5149F15A.1000806-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-20 17:30 ` Felipe Balbi
2013-03-20 17:42 ` Stephen Warren
2013-03-20 17:56 ` Felipe Balbi
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=20130320171147.GM1567@arwen.pp.htv.fi \
--to=balbi@ti$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-tegra@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=swarren@wwwdotorg$(echo .)org \
--cc=vbyravarasu@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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