summaryrefslogtreecommitdiff
path: root/apps/examples/usbstorage
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2013-04-25 15:52:00 -0600
committerGregory Nutt <gnutt@nuttx.org>2013-04-25 15:52:00 -0600
commit561c54964b2c99b1709fa79ee98aea31e7d7d449 (patch)
treec6f4c2610a9850b76b54b9716d3c51bdf4af3e56 /apps/examples/usbstorage
parent1ffc15c3233c8d61953fc2ebc80b5d3c46fc429f (diff)
downloadpx4-nuttx-561c54964b2c99b1709fa79ee98aea31e7d7d449.tar.gz
px4-nuttx-561c54964b2c99b1709fa79ee98aea31e7d7d449.tar.bz2
px4-nuttx-561c54964b2c99b1709fa79ee98aea31e7d7d449.zip
Various Kconfig files still have references to CONFIG_ variables. Some in harmless comments, some in config definionts which is not harmless. All removed
Diffstat (limited to 'apps/examples/usbstorage')
-rw-r--r--apps/examples/usbstorage/Kconfig10
1 files changed, 5 insertions, 5 deletions
diff --git a/apps/examples/usbstorage/Kconfig b/apps/examples/usbstorage/Kconfig
index 96af82b21..823ae2953 100644
--- a/apps/examples/usbstorage/Kconfig
+++ b/apps/examples/usbstorage/Kconfig
@@ -90,7 +90,7 @@ config EXAMPLES_USBMSC_TRACEINIT
default n
depends on EXAMPLES_USBMSC
---help---
- If USBDEV_TRACE is enabled (or CONFIG_DEBUG and CONFIG_DEBUG_USB),
+ If USBDEV_TRACE is enabled (or DEBUG and DEBUG_USB),
then the example code will also manage the USB trace output. The
amount of trace output can be controlled this configuration value:
This setting will show USB initialization events
@@ -100,7 +100,7 @@ config EXAMPLES_USBMSC_TRACECLASS
default n
depends on EXAMPLES_USBMSC
---help---
- If USBDEV_TRACE is enabled (or CONFIG_DEBUG and CONFIG_DEBUG_USB),
+ If USBDEV_TRACE is enabled (or DEBUG and DEBUG_USB),
then the example code will also manage the USB trace output. The
amount of trace output can be controlled this configuration value:
This setting will show USB class driver events
@@ -110,7 +110,7 @@ config EXAMPLES_USBMSC_TRACETRANSFERS
default n
depends on EXAMPLES_USBMSC
---help---
- If USBDEV_TRACE is enabled (or CONFIG_DEBUG and CONFIG_DEBUG_USB),
+ If USBDEV_TRACE is enabled (or DEBUG and DEBUG_USB),
then the example code will also manage the USB trace output. The
amount of trace output can be controlled this configuration value:
This setting will show USB data transfer events
@@ -120,7 +120,7 @@ config EXAMPLES_USBMSC_TRACECONTROLLER
default n
depends on EXAMPLES_USBMSC
---help---
- If USBDEV_TRACE is enabled (or CONFIG_DEBUG and CONFIG_DEBUG_USB),
+ If USBDEV_TRACE is enabled (or DEBUG and DEBUG_USB),
then the example code will also manage the USB trace output. The
amount of trace output can be controlled this configuration value:
This setting will show USB device controller events
@@ -130,7 +130,7 @@ config EXAMPLES_USBMSC_TRACEINTERRUPTS
default n
depends on EXAMPLES_USBMSC
---help---
- If USBDEV_TRACE is enabled (or CONFIG_DEBUG and CONFIG_DEBUG_USB),
+ If USBDEV_TRACE is enabled (or DEBUG and DEBUG_USB),
then the example code will also manage the USB trace output. The
amount of trace output can be controlled this configuration value:
This setting will show USB device controller interrupt-related events.