Kconfig (14e77332e74603efab8347c89d3cda447c3b97c9) Kconfig (22683e480b370ad1b3a34cfa461028d1f51da12d)
1# SPDX-License-Identifier: GPL-2.0
2#
3# USB Miscellaneous driver configuration
4#
5comment "USB Miscellaneous drivers"
6
7config USB_EMI62
8 tristate "EMI 6|2m USB Audio interface support"

--- 284 unchanged lines hidden (view full) ---

293 default ARCH_BRCMSTB && PHY_BRCM_USB
294 help
295 This option enables support for remapping some USB external
296 signals, which are typically on dedicated pins on the chip,
297 to any gpio.
298
299config USB_ONBOARD_HUB
300 tristate "Onboard USB hub support"
1# SPDX-License-Identifier: GPL-2.0
2#
3# USB Miscellaneous driver configuration
4#
5comment "USB Miscellaneous drivers"
6
7config USB_EMI62
8 tristate "EMI 6|2m USB Audio interface support"

--- 284 unchanged lines hidden (view full) ---

293 default ARCH_BRCMSTB && PHY_BRCM_USB
294 help
295 This option enables support for remapping some USB external
296 signals, which are typically on dedicated pins on the chip,
297 to any gpio.
298
299config USB_ONBOARD_HUB
300 tristate "Onboard USB hub support"
301 depends on OF || COMPILE_TEST
301 depends on OF
302 help
303 Say Y here if you want to support discrete onboard USB hubs that
304 don't require an additional control bus for initialization, but
305 need some non-trivial form of initialization, such as enabling a
306 power regulator. An example for such a hub is the Realtek
307 RTS5411.
308
309 This driver can be used as a module but its state (module vs
310 builtin) must match the state of the USB subsystem. Enabling
311 this config will enable the driver and it will automatically
312 match the state of the USB subsystem. If this driver is a
313 module it will be called onboard_usb_hub.
302 help
303 Say Y here if you want to support discrete onboard USB hubs that
304 don't require an additional control bus for initialization, but
305 need some non-trivial form of initialization, such as enabling a
306 power regulator. An example for such a hub is the Realtek
307 RTS5411.
308
309 This driver can be used as a module but its state (module vs
310 builtin) must match the state of the USB subsystem. Enabling
311 this config will enable the driver and it will automatically
312 match the state of the USB subsystem. If this driver is a
313 module it will be called onboard_usb_hub.