Commit f65735c2 authored by Dario Binacchi's avatar Dario Binacchi Committed by Marc Kleine-Budde

can: c_can: remove unused code

Commit 9d23a981 ("can: c_can: Remove unused inline function") left
behind C_CAN_MSG_OBJ_TX_LAST constant.

Commit fa39b54c ("can: c_can: Get rid of pointless interrupts") left
behind C_CAN_MSG_RX_LOW_LAST and C_CAN_MSG_OBJ_RX_SPLIT constants.

The removed code also made a comment useless and misleading.

Link: https://lore.kernel.org/r/20210302215435.18286-2-dariobin@libero.itSigned-off-by: default avatarDario Binacchi <dariobin@libero.it>
Signed-off-by: default avatarMarc Kleine-Budde <mkl@pengutronix.de>
parent dd477500
...@@ -822,8 +822,7 @@ static inline u32 c_can_get_pending(struct c_can_priv *priv) ...@@ -822,8 +822,7 @@ static inline u32 c_can_get_pending(struct c_can_priv *priv)
* c_can core saves a received CAN message into the first free message * c_can core saves a received CAN message into the first free message
* object it finds free (starting with the lowest). Bits NEWDAT and * object it finds free (starting with the lowest). Bits NEWDAT and
* INTPND are set for this message object indicating that a new message * INTPND are set for this message object indicating that a new message
* has arrived. To work-around this issue, we keep two groups of message * has arrived.
* objects whose partitioning is defined by C_CAN_MSG_OBJ_RX_SPLIT.
* *
* We clear the newdat bit right away. * We clear the newdat bit right away.
* *
......
...@@ -32,11 +32,7 @@ ...@@ -32,11 +32,7 @@
C_CAN_MSG_OBJ_RX_NUM - 1) C_CAN_MSG_OBJ_RX_NUM - 1)
#define C_CAN_MSG_OBJ_TX_FIRST (C_CAN_MSG_OBJ_RX_LAST + 1) #define C_CAN_MSG_OBJ_TX_FIRST (C_CAN_MSG_OBJ_RX_LAST + 1)
#define C_CAN_MSG_OBJ_TX_LAST (C_CAN_MSG_OBJ_TX_FIRST + \
C_CAN_MSG_OBJ_TX_NUM - 1)
#define C_CAN_MSG_OBJ_RX_SPLIT 9
#define C_CAN_MSG_RX_LOW_LAST (C_CAN_MSG_OBJ_RX_SPLIT - 1)
#define RECEIVE_OBJECT_BITS 0x0000ffff #define RECEIVE_OBJECT_BITS 0x0000ffff
enum reg { enum reg {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment