summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorhathach <[email protected]>2018-12-12 16:41:12 +0700
committerGitHub <[email protected]>2018-12-12 16:41:12 +0700
commit908931320e206e6ae6610cfc56b2a0950f252172 (patch)
tree8ae966733204841d54cf15f3e1154699cc884526 /docs
parentb7ad49332cd9a5539e35a75785adb5ca2e79715a (diff)
parent142f274c1d0cef2a1a5623885be29e2fecef4445 (diff)
Merge pull request #21 from hathach/devlocal
Devlocal
Diffstat (limited to 'docs')
-rw-r--r--docs/porting.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/porting.md b/docs/porting.md
index 5a464fa6b..040112d9c 100644
--- a/docs/porting.md
+++ b/docs/porting.md
@@ -113,10 +113,10 @@ As before with `dcd_event_bus_signal` the first argument is the USB peripheral n
Endpoints are the core of the USB data transfer process. They come in a few forms such as control, isochronous, bulk, and interrupt. We won't cover the details here except with some caveats in open below. In general, data is transferred by setting up a buffer of a given length to be transferred on a given endpoint address and then waiting for an interrupt to signal that the transfer is finished. Further details below.
-Endpoints within USB have an address which encodes both the number and direction of an endpoint. TinyUSB provides `edpt_number` and `edpt_dir` to unpack this data from the address. Here is a snippet that does it.
+Endpoints within USB have an address which encodes both the number and direction of an endpoint. TinyUSB provides `tu_edpt_number` and `tu_edpt_dir` to unpack this data from the address. Here is a snippet that does it.
- uint8_t epnum = edpt_number(ep_addr);
- uint8_t dir = edpt_dir(ep_addr);
+ uint8_t epnum = tu_edpt_number(ep_addr);
+ uint8_t dir = tu_edpt_dir(ep_addr);
##### dcd_edpt_open