[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190410062533.31535-1-qiangqing.zhang@nxp.com>
Date: Wed, 10 Apr 2019 06:27:37 +0000
From: Joakim Zhang <qiangqing.zhang@....com>
To: "wg@...ndegger.com" <wg@...ndegger.com>,
"mkl@...gutronix.de" <mkl@...gutronix.de>,
"davem@...emloft.net" <davem@...emloft.net>
CC: dl-linux-imx <linux-imx@....com>,
"linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Joakim Zhang <qiangqing.zhang@....com>
Subject: [PATCH] can: dev: clean up CAN ctrlmode when close CAN device
CAN driver always writes registers according to "ctrlmode", and now CAN
framework will keep CAN ctrlmode after device closed.
e.g. with following sequences:
1)ip link set can0 type can bitrate 1000000 loopback on
2)ip link set can0 up
3)ip link set can0 down
4)ip link set can0 type can bitrate 1000000
5)ip link set can0 up
After this sequence, we may want to test loopback for the first time and
not to test loopback second time. However, CAN device still keep
"ctrlmode" as loopback on.
This patch intends to clean up CAN ctrlmode when close CAN device. We
can set which ctrlmode we need when open CAN device again.
Signed-off-by: Joakim Zhang <qiangqing.zhang@....com>
---
drivers/net/can/dev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/can/dev.c b/drivers/net/can/dev.c
index c05e4d50d43d..4f69a8f16ba3 100644
--- a/drivers/net/can/dev.c
+++ b/drivers/net/can/dev.c
@@ -870,6 +870,7 @@ void close_candev(struct net_device *dev)
struct can_priv *priv = netdev_priv(dev);
cancel_delayed_work_sync(&priv->restart_work);
+ priv->ctrlmode = 0;
can_flush_echo_skb(dev);
}
EXPORT_SYMBOL_GPL(close_candev);
--
2.17.1
Powered by blists - more mailing lists