aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/power/bq24190_charger.c
diff options
context:
space:
mode:
authorYuval Mintz <Yuval.Mintz@qlogic.com>2016-05-11 16:36:17 +0300
committerDavid S. Miller <davem@davemloft.net>2016-05-12 00:04:07 -0400
commit36558c3d77032feb2a49ff7818338256378a774f (patch)
tree73d6637c437ab59c4fa0b5bf450a2fdb8cc5a675 /drivers/power/bq24190_charger.c
parentdacd88d6f6851510735e8db7a5981d4abcda6cb2 (diff)
downloadlinux-36558c3d77032feb2a49ff7818338256378a774f.tar.gz
qed: Bulletin and Link
Up to this point, VF and PF communication always originates from VF. As a result, VF cannot be notified of any async changes, and specifically cannot be informed of the current link state. This introduces the bulletin board, the mechanism through which the PF is going to communicate async notifications back to the VF. basically, it's a well-defined structure agreed by both PF and VF which the VF would continuously poll and into which the PF would DMA messages when needed. [Bulletin board is actually allocated and communicated in previous patches but never before used] Based on the bulletin infrastructure, the VF can query its link status and receive said async carrier changes. Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/power/bq24190_charger.c')
0 files changed, 0 insertions, 0 deletions