diff options
author | Arindam Nath <arindam.nath@amd.com> | 2020-02-05 21:24:31 +0530 |
---|---|---|
committer | Jon Mason <jdmason@kudzu.us> | 2020-03-13 10:04:20 -0400 |
commit | ac10d4f6c2a8247de21655f4564b0e209c3c1dd4 (patch) | |
tree | db6d4d02b30cc98e9b12e8b7bbdb803f6eb14249 /drivers/net | |
parent | 41dfc3f79650504f5047f20a4faacaff217ce37b (diff) | |
download | linux-ac10d4f6c2a8247de21655f4564b0e209c3c1dd4.tar.gz linux-ac10d4f6c2a8247de21655f4564b0e209c3c1dd4.tar.bz2 linux-ac10d4f6c2a8247de21655f4564b0e209c3c1dd4.zip |
NTB: send DB event when driver is loaded or un-loaded
When the driver on the local side is loaded, it sets
SIDE_READY bit in SIDE_INFO register. Likewise, when
it is un-loaded, it clears the bit.
Also just after being loaded, the driver polls for
peer SIDE_READY bit to be set. Since that bit is set
when the peer side driver has loaded, the polling on
local side breaks as soon as this condition is met.
But the situation is different when the driver is
un-loaded. Since the polling has already been stopped
as mentioned before, if the peer side driver gets
un-loaded, the driver on the local side is not notified
implicitly.
So, we improvise using existing doorbell mechanism.
We reserve the highest order bit of the DB register to
send a notification to peer when the driver on local
side is un-loaded. This also means that now we are one
short of 16 DB events and that is taken care of in the
valid DB mask.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Signed-off-by: Jon Mason <jdmason@kudzu.us>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions