mirror of
https://github.com/Rockbox/rockbox.git
synced 2025-11-09 13:12:37 -05:00
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
This commit is contained in:
parent
99f333c64f
commit
672bbe434b
16 changed files with 36 additions and 38 deletions
|
|
@ -68,8 +68,7 @@ void usb_drv_stall(int endpoint, bool stall,bool in);
|
|||
bool usb_drv_stalled(int endpoint,bool in);
|
||||
int usb_drv_send(int endpoint, void* ptr, int length);
|
||||
int usb_drv_send_nonblocking(int endpoint, void* ptr, int length);
|
||||
int usb_drv_recv(int endpoint, void* ptr, int length);
|
||||
void usb_drv_ack(struct usb_ctrlrequest* req);
|
||||
int usb_drv_recv_nonblocking(int endpoint, void* ptr, int length);
|
||||
void usb_drv_set_address(int address);
|
||||
void usb_drv_reset_endpoint(int endpoint, bool send);
|
||||
bool usb_drv_powered(void);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue