Commit b990da15 authored by Paul Bolle's avatar Paul Bolle Committed by Felipe Balbi

usb: phy: remove CONFIG_USB_OTG_UTILS once more

The Kconfig symbol USB_OTG_UTILS was removed in the v3.10 merge window,
in commit fd891498 ("usb: phy: remove CONFIG_USB_OTG_UTILS"). But that
symbol popped up again in a few places. Remove it there too.
Acked-by: default avatarPaul Zimmerman <paulz@synopsys.com>
Signed-off-by: default avatarPaul Bolle <pebolle@tiscali.nl>
Signed-off-by: default avatarFelipe Balbi <balbi@ti.com>
parent 17d966a3
...@@ -2,7 +2,6 @@ config USB_DWC2 ...@@ -2,7 +2,6 @@ config USB_DWC2
tristate "DesignWare USB2 DRD Core Support" tristate "DesignWare USB2 DRD Core Support"
depends on USB depends on USB
depends on VIRT_TO_BUS depends on VIRT_TO_BUS
select USB_OTG_UTILS
help help
Say Y or M here if your system has a Dual Role HighSpeed Say Y or M here if your system has a Dual Role HighSpeed
USB controller based on the DesignWare HSOTG IP Core. USB controller based on the DesignWare HSOTG IP Core.
......
...@@ -146,7 +146,6 @@ config USB_LPC32XX ...@@ -146,7 +146,6 @@ config USB_LPC32XX
depends on ARCH_LPC32XX depends on ARCH_LPC32XX
depends on USB_PHY depends on USB_PHY
select USB_ISP1301 select USB_ISP1301
select USB_OTG_UTILS
help help
This option selects the USB device controller in the LPC32xx SoC. This option selects the USB device controller in the LPC32xx SoC.
......
...@@ -139,7 +139,6 @@ config USB_ISP1301 ...@@ -139,7 +139,6 @@ config USB_ISP1301
tristate "NXP ISP1301 USB transceiver support" tristate "NXP ISP1301 USB transceiver support"
depends on USB || USB_GADGET depends on USB || USB_GADGET
depends on I2C depends on I2C
select USB_OTG_UTILS
help help
Say Y here to add support for the NXP ISP1301 USB transceiver driver. Say Y here to add support for the NXP ISP1301 USB transceiver driver.
This chip is typically used as USB transceiver for USB host, gadget This chip is typically used as USB transceiver for USB host, gadget
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment