BMC/Intel-BMC/linux.git/include/net/ncsi.h, branch dev-4.3

net/ncsi: Introduce ncsi_stop_dev()

2015-11-25T04:25:50+00:00

This introduces ncsi_stop_dev() which is to be called when network interrupt is going to be brought down. The NCSI interface won't be disabled and we rely on the driver to stop Rx and Tx path. Signed-off-by: Gavin Shan Signed-off-by: Joel Stanley

net/ncsi: Rename ncsi_stop_dev() to ncsi_suspend_dev()

2015-11-25T04:25:49+00:00

This renames ncsi_stop_dev() to ncsi_suspend_dev(). The NCSI device state ncsi_dev_state_stop_* are renamed to ncsi_dev_state_suspend_* accordingly. No logical changes introduced. Signed-off-by: Gavin Shan Signed-off-by: Joel Stanley

net/ncsi: Manage NCSI device

2015-11-18T04:14:19+00:00

There are multiple packages and channels connecting to NCSI enabled interface. The available packages and channels are probed with NCSI packets when NCSI device is started. Among the available packages and channels, only one channel should be selected to be active to provide service. When the active channel enters to failure state, we need choose another channel as active one to do failover. This implements the state machine to support above tasks. Also, the public interfaces are exposed for NIC driver to manage NCSI device. Signed-off-by: Gavin Shan

net/ncsi: Resource management

2015-11-18T04:14:17+00:00

According to NCSI spec (DSP0222), the NCSI enabled interface can connected to multiple packages simultaneously, up to 8 packages. Each package includes multiple channels, up to 32 channels. At one moment, one channel is enabled to provide service to the NCSI enabled interface. Besides, each channel comprises capabilities, modes, filters, version and statistics etc. All of them are resources to NCSI protocol stack. At the meanwhile, the NCSI device seen from NIC driver is represented by "struct ncsi_dev", which is expected to populated and started by NIC driver before the NIC can work. All possible NCSI packages and NCSI channels connected to the NCSI interface are tracked from the NCSI device. Also, the NCSI device recognizes active channel that is currently providing service to NCSI enabled interface. Also, the NCSI requests (pairs of command and response) are embedded in NCSI device. This introduces the data structs to represents the NCSI resources mentioned as above. Also, functions used by NCSI stack internally are implemented. Besides, this introduces kernel config option CONFIG_NET_NCSI to enable NCSI stack. Signed-off-by: Gavin Shan