Gavin Shan bbc7c01e95 net/ncsi: Choose hot channel as active one if necessary ... The issue was found on BCM5718 which has two NCSI channels in one package: C0 and C1. C0 is in link-up state while C1 is in link-down state. C0 is chosen as active channel until unplugging and plugging C0's cable: On unplugging C0's cable, LSC (Link State Change) AEN packet received on C0 to report link-down event. After that, C1 is chosen as active channel. LSC AEN for link-up event is lost on C0 when plugging C0's cable back. We lose the network even C0 is usable. This resolves the issue by recording the (hot) channel that was ever chosen as active one. The hot channel is chosen to be active one if none of available channels in link-up state. With this, C0 is still the active one after unplugging C0's cable. LSC AEN packet received on C0 when plugging its cable back. Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2016-10-20 11:23:07 -04:00
..
internal.h	net/ncsi: Choose hot channel as active one if necessary	2016-10-20 11:23:07 -04:00
Kconfig	net/ncsi: Resource management	2016-07-19 20:49:16 -07:00
Makefile	net/ncsi: NCSI AEN packet handler	2016-07-19 20:49:17 -07:00
ncsi-aen.c	net/ncsi: Avoid unused-value build warning from ia64-linux-gcc	2016-10-04 02:11:50 -04:00
ncsi-cmd.c	net/ncsi: Allow to extend NCSI request properties	2016-10-04 02:11:50 -04:00
ncsi-manage.c	net/ncsi: Choose hot channel as active one if necessary	2016-10-20 11:23:07 -04:00
ncsi-pkt.h	net/ncsi: NCSI AEN packet handler	2016-07-19 20:49:17 -07:00
ncsi-rsp.c	net/ncsi: Rework the channel monitoring	2016-10-04 02:11:51 -04:00