treewide: Test on CONFIG_USB_HOST (or CONFIG_CMD_USB) not CONFIG_USB

As the logic here is only used when we have a USB host controller, test
on CONFIG_USB_HOST rather than CONFIG_USB in general.  This lets us move
towards using CONFIG_USB only as a menu symbol to say that we have some
form of USB, and then USB_HOST or USB_GADGET depending on the role that
USB plays within the build.

Signed-off-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
Tom Rini
2021-07-09 10:11:55 -04:00
parent 3fa03bcf8c
commit e8d3eaadcd
7 changed files with 7 additions and 7 deletions

View File

@@ -142,7 +142,7 @@
#endif
/* USB */
#ifdef CONFIG_USB
#ifdef CONFIG_USB_HOST
#define CONFIG_HAS_FSL_XHCI_USB
#ifndef CONFIG_TARGET_LX2162AQDS
#define CONFIG_USB_MAX_CONTROLLER_COUNT 2

View File

@@ -101,7 +101,7 @@
#define BOOT_TARGET_UBIFS(func)
#endif
#ifdef CONFIG_USB
#ifdef CONFIG_CMD_USB
#define BOOT_TARGET_USB(func) func(USB, usb, 0)
#else
#define BOOT_TARGET_USB(func)

View File

@@ -34,7 +34,7 @@
/* Setup proper boot sequences for Miami boards */
#if defined(CONFIG_USB)
#if defined(CONFIG_USB_HOST)
# define EXTRA_ENV_USB \
"usbreset=i2c dev 1 && i2c mw 41 1 ff && i2c mw 41 3 fe && "\
"i2c mw 41 1 fe && i2c mw 41 1 ff\0" \