/* Macros: */\r
/** Raises a given event name, with the specified parameters. For events with no parameters the\r
* only argument to the macro is the event name, events with parameters list the parameter values\r
- * after the name as a comma seperated list.\r
+ * after the name as a comma separated list.\r
*\r
* When a given event is fired, its corresponding event handler code is executed.\r
*\r
*/\r
#define RAISE_EVENT(e, ...) Event_ ## e (__VA_ARGS__)\r
\r
- /** Indicates that a given module can raise a given event. This is the equivelent of putting the\r
+ /** Indicates that a given module can raise a given event. This is the equivalent of putting the\r
* event function's prototype into the module, but in a cleaner way. Each event which may be\r
* fired via the RAISE_EVENT macro in the module should have an accompanying RAISES_EVENT\r
* prototype in the module's header file.\r
*\r
* Only one event handler may be defined in any user project for each individual event. Events may\r
* or may not have parameters - for each event, refer to its documentation elsewhere in this module\r
- * to determine the presense and purpose of any event parameters.\r
+ * to determine the presence and purpose of any event parameters.\r
*\r
* Usage Example:\r
* \code\r
*/\r
#define EVENT_HANDLER(e) void Event_ ## e e ## _P\r
\r
- /** Indicates that a given module handles an event. This is the equivelent of putting the\r
+ /** Indicates that a given module handles an event. This is the equivalent of putting the\r
* event function's prototype into the module, but in a cleaner way. Each event which may be\r
* handled via the EVENT_HANDLER macro in the module should have an accompanying HANDLES_EVENT\r
* prototype in the module's header file.\r
*/\r
#define HANDLES_EVENT(e) EVENT_HANDLER(e)\r
\r
- /* Psudo-Functions for Doxygen: */\r
+ /* Pseudo-Functions for Doxygen: */\r
#if defined(__DOXYGEN__)\r
/** Event for VBUS level change. This event fires when the VBUS line of the USB AVR changes from\r
* high to low or vice-versa.\r
* has been attached (but not yet fully enumerated), or when in device mode and the device is connected\r
* to a host, beginning the enumeration process.\r
*\r
- * When in device mode, this can be used to progmatically start the USB management task to reduce\r
+ * When in device mode, this can be used to programmatically start the USB management task to reduce\r
* CPU usage.\r
*\r
* \note For the smaller USB AVRs (AT90USBXX2) with limited USB controllers, VBUS is not available to the USB controller.\r
* attached and enumerated device has been disconnected, or when in device mode and the device is\r
* disconnected from the host.\r
*\r
- * When in device mode, this can be used to progmatically stop the USB management task to reduce\r
+ * When in device mode, this can be used to programmatically stop the USB management task to reduce\r
* CPU usage.\r
*\r
* \note For the smaller USB AVRs (AT90USBXX2) with limited USB controllers, VBUS is not available to the USB controller.\r
\r
/** Event for USB device attachment. This event fires when a the USB interface is in host mode, and\r
* a USB device has been connected to the USB interface. This is interrupt driven, thus fires before\r
- * the standard USB_DeviceConnect event and so can be used to programatically start the USB management\r
+ * the standard USB_DeviceConnect event and so can be used to programmatically start the USB management\r
* task to reduce CPU consumption.\r
*\r
* \note This event only exists on USB AVR models which supports host mode.\r
\r
/** Event for USB device removal. This event fires when a the USB interface is in host mode, and\r
* a USB device has been removed the USB interface whether or not it has been enumerated. This\r
- * can be used to programatically stop the USB management task to reduce CPU consumption.\r
+ * can be used to programmatically stop the USB management task to reduce CPU consumption.\r
*\r
* \note This event only exists on USB AVR models which supports host mode.\r
*\r
projects / pub / USBasp.git / blobdiff