LUFA/CompileTimeTokens.txt

   1 /** \file
   2  *
   3  *  This file contains special DoxyGen information for the generation of the main page and other special
   4  *  documentation pages. It is not a project source file.
   5  */
   6
   7 /** \page TokenSummary Summary of Compile Tokens
   8  *
   9  *  The following lists all the possible tokens which can be defined in a project makefile, and passed to the
  10  *  compiler via the -D switch, to alter the LUFA library code. These tokens may alter the library behaviour,
  11  *  or remove features unused by a given application in order to save flash space.
  12  *
  13  *
  14  *  \section Sec_SummaryNonUSBTokens Non USB Related Tokens
  15  *  This section describes compile tokens which affect non-USB sections of the LUFA library.
  16  *
  17  *  <b>DISABLE_TERMINAL_CODES</b> - ( \ref Group_Terminal ) \n
  18  *  If an application contains ANSI terminal control codes listed in TerminalCodes.h, it might be desired to remove them
  19  *  at compile time for use with a terminal which is non-ANSI control code aware, without modifying the source code. If
  20  *  this token is defined, all ANSI control codes in the application code from the TerminalCodes.h header are removed from
  21  *  the source code at compile time.
  22  *
  23  *  <b>NUM_BLOCKS</b> - ( \ref Group_MemoryAllocator ) \n
  24  *  Sets the number of allocable blocks in the pseudo-heap of the dynamic memory allocation driver. This should be
  25  *  defined as a constant larger than zero.
  26  *
  27  *  <b>BLOCK_SIZE</b> - ( \ref Group_MemoryAllocator ) \n
  28  *  Sets the size of each allocable block in the pseudo-heap of the dynamic memory allocation driver. This should be
  29  *  defined as a constant larger than zero.
  30  *
  31  *  <b>NUM_HANDLES</b> - ( \ref Group_MemoryAllocator ) \n
  32  *  Sets the maximum number of managed memory handles which can be handed out by the dynamic memory allocation driver
  33  *  simultaneously, before a handle (and its associated allocated memory) must be freed.
  34  *
  35  *
  36  *  \section Sec_SummaryUSBClassTokens USB Class Driver Related Tokens
  37  *  This section describes compile tokens which affect USB class-specific drivers in the LUFA library.
  38  *
  39  *  <b>HID_ENABLE_FEATURE_PROCESSING</b> - ( \ref Group_HIDParser ) \n
  40  *  Define this token to enable the processing of FEATURE HID report items, if any, into the processed HID structure.
  41  *  By default FEATURE items (which are device features settable by the host but not directly visible by the user) are
  42  *  skipped when processing a device HID report.
  43  *
  44  *  <b>HID_INCLUDE_CONSTANT_DATA_ITEMS</b> - ( \ref Group_HIDParser ) \n
  45  *  By default, constant data items (usually used as spacers to align separate report items to a byte or word boundary)
  46  *  in the HID report are skipped during report processing. It is highly unusual for an application to make any use of
  47  *  constant data items (as they do not carry any useful data and only occupy limited RAM) however if required defining
  48  *  this switch will put constant data items into the processed HID report structure.
  49  *
  50  *  <b>HID_STATETABLE_STACK_DEPTH</b> - ( \ref Group_HIDParser ) \n
  51  *  HID reports may contain PUSH and POP elements, to store and retrieve the current HID state table onto a stack. This
  52  *  allows for reports to save the state table before modifying it slightly for a data item, and then restore the previous
  53  *  state table in a compact manner. This token may be defined to a non-zero value to give the maximum depth of the state
  54  *  table stack. If not defined, this defaults to the value indicated in the HID.h file documentation.
  55  *
  56  *  <b>HID_USAGE_STACK_DEPTH</b> - ( \ref Group_HIDParser ) \n
  57  *  HID reports generally contain many USAGE elements, which are assigned to INPUT, OUTPUT and FEATURE items in succession
  58  *  when multiple items are defined at once (via REPORT COUNT elements). This allows for several items to be defined with
  59  *  different usages in a compact manner. This token may be defined to a non-zero value to set the maximum depth of the
  60  *  usage stack, indicating the maximum number of USAGE items which can be stored temporarily until the next INPUT, OUTPUT
  61  *  and FEATURE item. If not defined, this defaults to the value indicated in the HID.h file documentation.
  62  *
  63  *  <b>HID_MAX_COLLECTIONS</b> - ( \ref Group_HIDParser ) \n
  64  *  HID reports generally contain several COLLECTION elements, used to group related data items together. Collection information
  65  *  is stored separately in the processed usage structure (and referred to by the data elements in the structure) to save space.
  66  *  This token may be defined to a non-zero value to set the maximum number of COLLECTION items which can be processed by the
  67  *  parser into the resultant processed report structure. If not defined, this defaults to the value indicated in the HID.h file
  68  *  documentation.
  69  *
  70  *  <b>HID_MAX_REPORTITEMS</b> - ( \ref Group_HIDParser ) \n
  71  *  All HID reports contain one or more INPUT, OUTPUT and/or FEATURE items describing the data which can be sent to and from the HID
  72  *  device. Each item has associated usages, bit offsets in the item reports and other associated data indicating the manner in which
  73  *  the report data should be interpreted by the host. This token may be defined to a non-zero value to set the maximum number of
  74  *  data elements which can be stored in the processed HID report structure, including INPUT, OUTPUT and (if enabled) FEATURE items.
  75  *  If a item has a multiple count (i.e. a REPORT COUNT of more than 1), each item in the report count is placed separately in the
  76  *  processed HID report table. If not defined, this defaults to the value indicated in the HID.h file documentation.
  77  *
  78  *
  79  *  \section Sec_SummaryUSBTokens USB Driver Related Tokens
  80  *  This section describes compile tokens which affect USB driver stack as a whole in the LUFA library.
  81  *
  82  *  <b>USE_RAM_DESCRIPTORS</b> - ( \ref Group_Descriptors ) \n
  83  *  Define this token to indicate to the USB driver that device descriptors are stored in RAM, rather than the default of
  84  *  the AVR's flash. RAM descriptors may be desirable in applications where speed or minimizing flash usage is more important
  85  *  than RAM usage, or applications where the descriptors need to be modified at runtime.
  86  *
  87  *  <b>USE_EEPROM_DESCRIPTORS</b> - ( \ref Group_Descriptors ) \n
  88  *  Similar to USE_RAM_DESCRIPTORS, but descriptors are stored in the AVR's EEPROM memory rather than RAM.
  89  *
  90  *  <b>USE_NONSTANDARD_DESCRIPTOR_NAMES</b> - ( \ref Group_Descriptors ) \n
  91  *  The USB 2.0 standard gives some rather obscure names for the elements in the standard descriptor types (device, configuration,
  92  *  string, endpoint, etc.). By default the LUFA library uses these names in its predefined descriptor structure types for
  93  *  compatibility. If this token is defined, the structure element names are switched to the LUFA-specific but more descriptive
  94  *  names documented in the StdDescriptors.h source file.
  95  *
  96  *  <b>FIXED_CONTROL_ENDPOINT_SIZE</b> - ( \ref Group_EndpointManagement ) \n
  97  *  By default, the library determines the size of the control endpoint (when in device mode) by reading the device descriptor.
  98  *  Normally this reduces the amount of configuration required for the library, allows the value to change dynamically (if
  99  *  descriptors are stored in EEPROM or RAM rather than flash memory) and reduces code maintenance. However, this token can be
 100  *  defined to a non-zero value instead to give the size in bytes of the control endpoint, to reduce the size of the compiled
 101  *  binary at the expense of flexibility.
 102  *
 103  *  <b>STATIC_ENDPOINT_CONFIGURATION</b> - ( \ref Group_EndpointManagement ) \n
 104  *  By default, the endpoint configuration routine is designed to accept dynamic inputs, so that the endpoints can be configured
 105  *  using variable values known only at runtime. This allows for a great deal of flexibility, however uses a small amount of binary
 106  *  space which may be wasted if all endpoint configurations are static and known at compile time. Define this token via the -D switch
 107  *  to optimize the endpoint configuration routine for constant inputs, to reduce the size of the compiled binary at the expense of
 108  *  flexibility. Note that with this option dynamic values may still be used, but will result in many times more code to be generated than
 109  *  if the option was disabled. This is designed to be used only if the FIXED_CONTROL_ENDPOINT_SIZE option is also used.
 110  *
 111  *  <b>USE_SINGLE_DEVICE_CONFIGURATION</b> - ( \ref Group_Device ) \n
 112  *  By default, the library determines the number of configurations a USB device supports by reading the device descriptor. This reduces
 113  *  the amount of configuration required to set up the library, and allows the value to change dynamically (if descriptors are stored in
 114  *  EEPROM or RAM rather than flash memory) and reduces code maintenance. However, many USB device projects use only a single configuration.
 115  *  Defining this token enables single-configuration mode, reducing the compiled size of the binary at the expense of flexibility.
 116  *
 117  *  <b>FEATURELESS_CONTROL_ONLY_DEVICE</b> \n
 118  *  In some limited USB device applications, device features (other than self-power) and endpoints other than the control endpoint aren't
 119  *  used. In such limited situations, this token may be defined to remove the handling of the Set Feature Chapter 9 request entirely and
 120  *  parts of the Get Feature chapter 9 request to save space. Generally, this is usually only useful in (some) bootloaders and is best avoided.
 121  *
 122  *  <b>NO_STREAM_CALLBACKS</b> - ( \ref Group_EndpointPacketManagement , \ref Group_PipePacketManagement )\n
 123  *  Both the endpoint and the pipe driver code contains stream functions, allowing for arrays of data to be sent to or from the
 124  *  host easily via a single function call (rather than complex routines worrying about sending full packets, waiting for the endpoint/
 125  *  pipe to become ready, etc.). By default, these stream functions require a callback function which is executed after each byte processed,
 126  *  allowing for early-aborts of stream transfers by the application. If callbacks are not required in an application, they can be removed
 127  *  by defining this token, reducing the compiled binary size. When removed, the stream functions no longer accept a callback function as
 128  *  a parameter.
 129  *
 130  *  <b>USB_HOST_TIMEOUT_MS</b> - ( \ref Group_Host ) \n
 131  *  When a control transfer is initiated in host mode to an attached device, a timeout is used to abort the transfer if the attached
 132  *  device fails to respond within the timeout period. This token may be defined to a non-zero value to set the timeout period for
 133  *  control transfers, specified in milliseconds. If not defined, the default value specified in Host.h is used instead.
 134  *
 135  *  <b>HOST_DEVICE_SETTLE_DELAY_MS</b> - ( \ref Group_Host ) \n
 136  *  Some devices require a delay of up to 5 seconds after they are connected to VBUS before the enumeration process can be started, or
 137  *  they will fail to enumerate correctly. By placing a delay before the enumeration process, it can be ensured that the bus has settled
 138  *  back to a known idle state before communications occur with the device. This token may be defined to a non-zero value to set the
 139  *  device settle period, specified in milliseconds. If not defined, the default value specified in Host.h is used instead.
 140  *
 141  *  <b>USE_STATIC_OPTIONS</b> - ( \ref Group_USBManagement ) \n
 142  *  By default, the USB_Init() function accepts dynamic options at runtime to alter the library behaviour, including whether the USB pad
 143  *  voltage regulator is enabled, and the device speed when in device mode. By defining this token to a mask comprised of the USB options
 144  *  mask defines usually passed as the Options parameter to USB_Init(), the resulting compiled binary can be decreased in size by removing
 145  *  the dynamic options code, and replacing it with the statically set options. When defined, the USB_Init() function no longer accepts an
 146  *  Options parameter.
 147  *
 148  *  <b>USB_DEVICE_ONLY</b> - ( \ref Group_USBManagement ) \n
 149  *  For the USB AVR models supporting both device and host USB modes, the USB_Init() function contains a Mode parameter which specifies the
 150  *  mode the library should be initialized to. If only device mode is required, the code for USB host mode can be removed from the binary to
 151  *  save space. When defined, the USB_Init() function no longer accepts a Mode parameter. This define is irrelevant on smaller USB AVRs which
 152  *  do not support host mode.
 153  *
 154  *  <b>USB_HOST_ONLY</b> - ( \ref Group_USBManagement ) \n
 155  *  Same as USB_DEVICE_ONLY, except the library is fixed to USB host mode rather than USB device mode. Not available on some USB AVR models.
 156  *
 157  *  <b>USB_STREAM_TIMEOUT_MS</b> - ( \ref Group_USBManagement ) \n
 158  *  When endpoint and/or pipe stream functions are used, by default there is a timeout between each transfer which the connected device or host
 159  *  must satisfy, or the stream function aborts the remaining data transfer. This token may be defined to a non-zero value to set the timeout
 160  *  period for stream transfers, specified in milliseconds. If not defined, the default value specified in LowLevel.h is used instead.
 161  *
 162  *  <b>NO_LIMITED_CONTROLLER_CONNECT</b> - ( \ref Group_Events ) \n
 163  *  On the smaller USB AVRs, the USB controller lacks VBUS events to determine the physical connection state of the USB bus to a host. In lieu of
 164  *  VBUS events, the library attempts to determine the connection state via the bus suspension and wake up events instead. This however may be
 165  *  slightly inaccurate due to the possibility of the host suspending the bus while the device is still connected. If accurate connection status is
 166  *  required, the VBUS line of the USB connector should be routed to an AVR pin to detect its level, so that the USB_IsConnected global
 167  *  can be accurately set and the USB_Connect and USB_Disconnect events manually raised by the RAISE_EVENT macro. When defined, this token disables
 168  *  the library's auto-detection of the connection state by the aforementioned suspension and wake up events.
 169  */