drivers: can: catch up on API naming changes
Catch up on the CAN driver API argument naming changes: - Unify naming of callback function pointers as "callback". - Unify naming of user-specified callback function arguments as "user_data". - Instances and pointers to struct zcan_frame are named "frame", not "msg", to avoid confusion with the CAN message queue support. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
This commit is contained in:
parent
deb1b455b9
commit
b21a91e468
12 changed files with 125 additions and 125 deletions
|
@ -100,7 +100,7 @@ enum can_state can_stm32fd_get_state(const struct device *dev,
|
|||
|
||||
int can_stm32fd_send(const struct device *dev, const struct zcan_frame *frame,
|
||||
k_timeout_t timeout, can_tx_callback_t callback,
|
||||
void *callback_arg)
|
||||
void *user_data)
|
||||
{
|
||||
const struct can_stm32fd_config *cfg = DEV_CFG(dev);
|
||||
const struct can_mcan_config *mcan_cfg = &cfg->mcan_cfg;
|
||||
|
@ -108,7 +108,7 @@ int can_stm32fd_send(const struct device *dev, const struct zcan_frame *frame,
|
|||
struct can_mcan_msg_sram *msg_ram = cfg->msg_sram;
|
||||
|
||||
return can_mcan_send(mcan_cfg, mcan_data, msg_ram, frame, timeout,
|
||||
callback, callback_arg);
|
||||
callback, user_data);
|
||||
}
|
||||
|
||||
int can_stm32fd_attach_isr(const struct device *dev, can_rx_callback_t isr,
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue