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>
Showing
- board/freescale/lx2160a/lx2160a.c 1 addition, 1 deletionboard/freescale/lx2160a/lx2160a.c
- board/freescale/mpc837xerdb/mpc837xerdb.c 1 addition, 1 deletionboard/freescale/mpc837xerdb/mpc837xerdb.c
- board/tplink/wdr4300/wdr4300.c 1 addition, 1 deletionboard/tplink/wdr4300/wdr4300.c
- cmd/Kconfig 1 addition, 1 deletioncmd/Kconfig
- include/configs/lx2160a_common.h 1 addition, 1 deletioninclude/configs/lx2160a_common.h
- include/configs/stm32mp1.h 1 addition, 1 deletioninclude/configs/stm32mp1.h
- include/configs/topic_miami.h 1 addition, 1 deletioninclude/configs/topic_miami.h
Loading
Please register or sign in to comment