Lines Matching full:be
16 * contributors may be used to endorse or promote products derived from this
22 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
58 * This number would be shared between IN and OUT endpoint.
59 * It may be also assigned totaly to one endpoint.
130 * Enumeration of possible events that may be generated by the driver.
154 * Status codes that may be returned by @ref nrfx_usbd_ep_status_get or, except for
162 … * This error would also be returned when next_transfer function has been defined
169 NRFX_USBD_EP_ABORTED, /**< EP0 transfer can be aborted when new setup comes.
170 * Any other transfer can be aborted by USB reset or driver stopping.
208 * Universal data pointer that can be used for any type of transfer.
218 * @brief Structure to be filled with information about the next transfer.
222 * can never be higher than the endpoint size.
233 * Flags configured for the transfer that can be merged using the bitwise 'or' operator (|).
294 * The transfers provided by the feeder must be simple:
301 * that can be used to prepare transfer.
303 * @param[out] p_next Structure with the data for the next transfer to be filled.
310 * @retval true There is more data to be prepared and when the current transfer
311 * finishes, the feeder function is expected to be called again.
327 * @param[out] p_next Structure with the data for the next transfer to be filled.
335 * @retval true There is more data to be prepared and when current transfer
336 * finishes, the feeder function is expected to be called again.
383 * @param[in] event_handler Event handler provided by the user. Cannot be null.
398 * After calling this function USBD peripheral would be enabled.
399 * The USB LDO would be enabled.
402 * program after enabling USBD driver HFINT would be used for the USBD peripheral.
405 * In normal situation this function should be called in reaction to USBDETECTED
416 * After calling this function USBD peripheral would be disabled.
417 * No events would be detected or processed by the driver.
418 * Clock for the peripheral would be disconnected.
425 * After calling this function USBD peripheral should be fully functional
426 * and all new incoming events / interrupts would be processed by the driver.
436 * If it is false, SOF interrupt is left disabled and will not be generated.
439 * @note If the isochronous endpoints are going to be used,
454 * This function can also be used to logically disconnect USB from the HOST that
488 * The function has to be called in the reaction to @ref NRFX_USBD_EVT_SUSPEND event
491 * After successful call of this function most of the USBD registers would be unavailable.
504 * After calling this function all the USBD registers would be available.
515 * has just begun to be generated.
534 * @brief Enable only interrupts that should be processed in SUSPEND mode.
537 * It enables only the interrupts that can be properly processed without stable HFCLK.
575 * @brief Configure packet size that should be supported by the endpoint.
578 * This value sets max packet size that would be transmitted over the endpoint.
636 * Disable all endpoints that can be disabled in USB device while it is still active.
647 * @note Data buffer pointed by p_data have to be kept active till
651 * For IN endpoint sending would be initiated.
652 * For OUT endpoint receiving would be initiated.
683 * @brief Get the temporary buffer to be used by the feeder.
685 * This buffer is used for TX transfers and it can be reused automatically
689 * May be used inside the feeder configured in @ref nrfx_usbd_ep_handled_transfer.
691 * @return Pointer to the buffer that can be used temporarily.
729 * Endpoint that is busy cannot be accessed by MCU.
732 * to be received by the host.
736 * - OUT (TX) endpoint: New data can be uploaded.
737 * - IN (RX) endpoint: New data can be downloaded using @ref nrfx_usbd_ep_transfer
754 * @note Stalled endpoint would not be cleared when DMA transfer finishes.
765 * If it is OUT endpoint (receiving) it would be also prepared for reception.
766 * It means that busy flag would be set.
768 * In endpoint (transmitting) would not be cleared - it gives possibility to
799 * @param[out] p_setup Pointer to data structure that would be filled by
807 * This function may be called if any more data in control write transfer is expected.
808 * Clears only OUT endpoint to be able to take another OUT data token.
818 * It has to be called if no data respond for the SETUP command is sent.