Lines Matching refs:be
5 Note: The underlying DWC_OTG controller will sometimes be referred to as the Host Controller in thi…
7 …be called within critical sections. Therefore, the USB Host stack will prefix all such function na…
18 …ra notes regarding the hardware's behavior that are not specified / cannot be easily found in the …
28 - The channels will remain active (i.e., `HCCHAR.ChEna` will still be set)
29 … waiting for an interrupt) will not work for ISOC channels (the interrupt will never be generated).
52 - Models a single USB port where a single device can be attached
53 - Actions: Port can be powered ON/OFF, reset, suspended
59 …trollers abstraction of USB pipes. At any one point in time, a channel can be configured to map to…
60 - Channels have to be allocated and freed. It's possible to change a channel's endpoint characteris…
65 - A transfer descriptor list must be filled using `usbh_hal_xfer_desc_fill()`
66 - Once filled, a channel can be activated using `usbh_hal_chan_activate()`
75 …be routed through one of the ports to a device. However, note that **the underlying hardware contr…
78 …e on the host". URBs (USB Request Block) represent a USB transfer that can be enqueued into a pipe…
83 - No more than 8 pipes can be allocated at any one time due to underlying Host Controllers 8 channe…
87 - An HCD port can be thought of as a simplified version of a port on the Root Hub of the host contr…
88 - A port must first initialized before it can be used. A port is identified by its handled of type …
89 - The port can be manipulated using commands such as:
93 …be put into the HCD_PORT_STATE_RECOVERY state. The port can be deinitialized from there, or recove…
97 …be after each port reset (a port reset seems to clear the FIFO sizing registers). The sizing of th…
98 - The FIFO sizes will be set on port initialization (supplied in `hcd_port_config_t`)
99 …- FIFOs can be resized after port reset using `hcd_port_set_fifo_bias()` but some restrictions app…
103 …ipes can be opened to a particular endpoint based on a descriptor provided on allocation. If openi…
104 - URBs can be enqueued into a pipe. Pipes use a linked list internally, so there is (in theory) no …
105 - URBs need to be dequeued once they are completed.
106 … information (such as data buffer, transfer length in bytes) filled before they should be enqueued.
107 - URBs will be owned by the HCD until they are dequeued. Thus, users should not attempt to modify a…
114 - Some static functions may be blocking. Those functions will have a note in their descriptions.
115 … track of port and pipe events. Callbacks don't even need to be used, and the HCD should be able t…
116 - The port and each pipe have to be treated as completely separate entities (with their own handles…
128 - Port callback will run whenever an event a port occurs. `hcd_port_handle_event()` should be calle…
137 The HCD API is thread safe however the following limitations should be noted:
141 - `hcd_port_command()` is thread safe, but only one port command can be executed at any one time. T…
143 - Blocking HCD functions should not be called from critical sections and interrupts (e.g., `hcd_por…