Lines Matching defs:peer
256 * This is indicated by bit 1 being set in the peer
263 * then the peer side driver loads. In this case, we would have
264 * received LINK_UP event and bit 1 of peer SIDEINFO is also
266 * peer SIDEINFO remains set, but LINK_DOWN bit is set in
268 * that, we clear bit 1 of peer SIDEINFO to 0, since the peer
273 * LINK_UP event will always occur before the peer side driver
275 * the LINK_UP event has occurred, but the peer side driver hasn't
284 * If bit 1 of peer SIDEINFO register is not set, then we
300 /* Clear peer sideinfo register */
607 /* polling peer status */
660 * Since we had reserved highest order bit of DB for signaling peer of
670 * If we are here, that means the peer has signalled a special
671 * event which notifies that the peer driver has been
673 * peer will load its driver again sometime, we schedule link
999 static void amd_set_side_info_reg(struct amd_ntb_dev *ndev, bool peer)
1004 if (peer)
1016 static void amd_clear_side_info_reg(struct amd_ntb_dev *ndev, bool peer)
1021 if (peer)
1131 * be used to notify peer when the driver on this side is being
1271 * to the peer. This will make sure that when the peer handles the