From 831a38483cf21b395bb0d9d7a34fb9b430e9bb86 Mon Sep 17 00:00:00 2001 From: Tom Rini Date: Fri, 14 Mar 2025 19:27:36 -0600 Subject: usb: ulpi: Clean up how we enable support The way we enable ULPI support today isn't something that should work. The "optional" keyword in a choice statement is not a documented feature. To make this work in a supported way, make USB_ULPI something we ask about if USB_HOST is set. Next, we move the choice of what viewer to use to be after the framework portion and to depend on that. We then borrow a few words from the top-level README to make the help text here clearer. Finally we make the Qualcomm driver select ULPI as it's required and we make the tegra driver not duplicate a check that Kconfig now handles for us. Signed-off-by: Tom Rini --- README | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'README') diff --git a/README b/README index 334bbcf0dd1..88b6e6f2772 100644 --- a/README +++ b/README @@ -482,18 +482,6 @@ The following options need to be configured: for your device - CONFIG_USBD_PRODUCTID 0xFFFF -- ULPI Layer Support: - The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via - the generic ULPI layer. The generic layer accesses the ULPI PHY - via the platform viewport, so you need both the genric layer and - the viewport enabled. Currently only Chipidea/ARC based - viewport is supported. - To enable the ULPI layer support, define CONFIG_USB_ULPI and - CONFIG_USB_ULPI_VIEWPORT in your board configuration file. - If your ULPI phy needs a different reference clock than the - standard 24 MHz then you have to define CFG_ULPI_REF_CLK to - the appropriate value in Hz. - - MMC Support: CONFIG_SH_MMCIF Support for Renesas on-chip MMCIF controller -- cgit v1.2.3