d991f855cb
'default n' is the default value for any bool or tristate Kconfig
setting so there is no need to write it explicitly.
Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
is not set' for visible symbols") the Kconfig behavior is the same
regardless of 'default n' being present or not:
...
One side effect of (and the main motivation for) this change is making
the following two definitions behave exactly the same:
config FOO
bool
config FOO
bool
default n
With this change, neither of these will generate a
'# CONFIG_FOO is not set' line (assuming FOO isn't selected/implied).
That might make it clearer to people that a bare 'default n' is
redundant.
...
Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
18 lines
603 B
Plaintext
18 lines
603 B
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
#
|
|
# Renesas USBHS Controller Drivers
|
|
#
|
|
|
|
config USB_RENESAS_USBHS
|
|
tristate 'Renesas USBHS controller'
|
|
depends on USB_GADGET
|
|
depends on ARCH_RENESAS || SUPERH || COMPILE_TEST
|
|
depends on EXTCON || !EXTCON # if EXTCON=m, USBHS cannot be built-in
|
|
help
|
|
Renesas USBHS is a discrete USB host and peripheral controller chip
|
|
that supports both full and high speed USB 2.0 data transfers.
|
|
It has nine or more configurable endpoints, and endpoint zero.
|
|
|
|
Say "y" to link the driver statically, or "m" to build a
|
|
dynamically linked module called "renesas_usbhs"
|