diff options
| author | hathach <[email protected]> | 2019-03-24 01:19:32 +0700 |
|---|---|---|
| committer | hathach <[email protected]> | 2019-03-24 01:19:32 +0700 |
| commit | 18f248b142a477b2134d23a2902d8d7de6e4c195 (patch) | |
| tree | 6dff75edadb85d400198659fdaf118edd5addca9 /docs | |
| parent | 29e075b8b968806c4a9ebffdbdfacbd9b01cf029 (diff) | |
remove tusb_hal_millis() usage, less work for porting
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/porting.md | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/docs/porting.md b/docs/porting.md index f5af82800..70c9f25aa 100644 --- a/docs/porting.md +++ b/docs/porting.md @@ -53,12 +53,6 @@ The OS Abstraction Layer is responsible for providing basic data structures for The code is almost entirely agnostic of MCU and lives in `src/osal`. -#### tusb_hal_millis - -The OPT_OS_NONE option is the only option which requires an MCU specific function. It needs `tusb_hal_millis` to measure the passage of time. On ARM this is commonly done with SysTick. The function returns the elapsed number of milliseconds since startup. - -`tusb_hal_millis` is also provided in `hw/bsp/<board name>/board_<board name>.c` because it may vary with MCU use. - ### Device API After the USB device is setup, the USB device code works by processing events on the main thread (by calling `tud_task`). These events are queued by the USB interrupt handler. So, there are three parts to the device low-level API: device setup, endpoint setup and interrupt processing. |