diff options
author | Aidan MacDonald <amachronic@protonmail.com> | 2021-09-19 10:54:26 +0100 |
---|---|---|
committer | Aidan MacDonald <amachronic@protonmail.com> | 2021-09-20 22:41:29 +0100 |
commit | 672bbe434b12d4730cf270f7245753fb98cf162d (patch) | |
tree | 3fdaa08ddc41f942336c968bb169e8806c7c3fa8 /firmware/target/arm/usb-tcc.c | |
parent | 99f333c64f13c3f9a62b9f5e184ae87f053bf65a (diff) | |
download | rockbox-672bbe434b12d4730cf270f7245753fb98cf162d.tar.gz rockbox-672bbe434b12d4730cf270f7245753fb98cf162d.zip |
usb: rename usb_drv_recv() to usb_recv_recv_nonblocking()
IMHO the current name is somewhat misleading:
- usb_drv_send() is blocking and we have usb_drv_send_nonblocking()
for the non-blocking case. This inconsistent naming can only
promote confusion. (And what would we call a blocking receive?)
- Other hardware abstraction APIs in Rockbox are usually blocking:
storage, LCD, backlight, audio... in other words, blocking is the
default expected behavior, with non-blocking calls being a rarity.
Change-Id: I05b41088d09eab582697674f4f06fdca0c8950af
Diffstat (limited to 'firmware/target/arm/usb-tcc.c')
-rw-r--r-- | firmware/target/arm/usb-tcc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/firmware/target/arm/usb-tcc.c b/firmware/target/arm/usb-tcc.c index 1b5f16c223..8ce75b6764 100644 --- a/firmware/target/arm/usb-tcc.c +++ b/firmware/target/arm/usb-tcc.c | |||
@@ -609,7 +609,7 @@ int usb_drv_send_nonblocking(int endpoint, void *ptr, int length) | |||
609 | return rc; | 609 | return rc; |
610 | } | 610 | } |
611 | 611 | ||
612 | int usb_drv_recv(int endpoint, void* ptr, int length) | 612 | int usb_drv_recv_nonblocking(int endpoint, void* ptr, int length) |
613 | { | 613 | { |
614 | volatile struct tcc_ep *tcc_ep = &tcc_endpoints[endpoint & 0x7f]; | 614 | volatile struct tcc_ep *tcc_ep = &tcc_endpoints[endpoint & 0x7f]; |
615 | int flags; | 615 | int flags; |