usb: ehci-omap: Remove OMAP_EHCI_PHYx_RESET_GPIO from Kconfig
With the omap-ehci driver now using the phy subsystem to enable and disable reset, the driver no longer needs to know which GPIO's are used, and they can be removed from Kconfig. Signed-off-by: Adam Ford <aford173@gmail.com>
This commit is contained in:
parent
70dbff1f9e
commit
fc4bee1830
1 changed files with 0 additions and 34 deletions
|
@ -198,40 +198,6 @@ config USB_EHCI_OMAP
|
|||
Enables support for the on-chip EHCI controller on OMAP3 and later
|
||||
SoCs.
|
||||
|
||||
if USB_EHCI_OMAP
|
||||
|
||||
config HAS_OMAP_EHCI_PHY1_RESET_GPIO
|
||||
bool "PHY #1 requires a GPIO hold to it in RESET while PHY settles"
|
||||
help
|
||||
Enable this to be able to configure the GPIO number used to hold the
|
||||
PHY in RESET for enough time until the PHY is settled and ready.
|
||||
|
||||
config OMAP_EHCI_PHY1_RESET_GPIO
|
||||
int "GPIO number to hold PHY #1 in RESET"
|
||||
depends on HAS_OMAP_EHCI_PHY1_RESET_GPIO
|
||||
|
||||
config HAS_OMAP_EHCI_PHY2_RESET_GPIO
|
||||
bool "PHY #2 requires a GPIO hold to it in RESET while PHY settles"
|
||||
help
|
||||
Enable this to be able to configure the GPIO number used to hold the
|
||||
PHY in RESET for enough time until the PHY is settled and ready.
|
||||
|
||||
config OMAP_EHCI_PHY2_RESET_GPIO
|
||||
int "GPIO number to hold PHY #2 in RESET"
|
||||
depends on HAS_OMAP_EHCI_PHY2_RESET_GPIO
|
||||
|
||||
config HAS_OMAP_EHCI_PHY3_RESET_GPIO
|
||||
bool "PHY #3 requires a GPIO hold to it in RESET while PHY settles"
|
||||
help
|
||||
Enable this to be able to configure the GPIO number used to hold the
|
||||
PHY in RESET for enough time until the PHY is settled and ready.
|
||||
|
||||
config OMAP_EHCI_PHY3_RESET_GPIO
|
||||
int "GPIO number to hold PHY #3 in RESET"
|
||||
depends on HAS_OMAP_EHCI_PHY3_RESET_GPIO
|
||||
|
||||
endif
|
||||
|
||||
config USB_EHCI_VF
|
||||
bool "Support for Vybrid on-chip EHCI USB controller"
|
||||
depends on ARCH_VF610
|
||||
|
|
Loading…
Reference in a new issue