summaryrefslogtreecommitdiff
path: root/drivers/ntb/test/Kconfig
diff options
context:
space:
mode:
authorSerge Semin <fancer.lancer@gmail.com>2017-01-11 03:13:20 +0300
committerJon Mason <jdmason@kudzu.us>2017-07-06 18:30:07 +0300
commitd67288a39584daad11edee9b03d53264ba147453 (patch)
treeaafe4d840838bda5445c517ff702e5c141589034 /drivers/ntb/test/Kconfig
parent443b9a14ecbe811071467d54d6f2f1182835cc4d (diff)
downloadlinux-d67288a39584daad11edee9b03d53264ba147453.tar.xz
NTB: Alter Scratchpads API to support multi-ports devices
Even though there is no any real NTB hardware, which would have both more than two ports and Scratchpad registers, it is logically correct to have Scratchpad API accepting a peer port index as well. Intel/AMD drivers utilize Primary and Secondary topology to split Scratchpad between connected root devices. Since port-index API introduced, Intel/AMD NTB hardware drivers can use device port to determine which Scratchpad registers actually belong to local and peer devices. The same approach can be used if some potential hardware in future will be multi-port and have some set of Scratchpads. Here are the brief of changes in the API: ntb_spad_count() - return number of Scratchpads per each port ntb_peer_spad_addr(pidx, sidx) - address of Scratchpad register of the peer device with pidx-index ntb_peer_spad_read(pidx, sidx) - read specified Scratchpad register of the peer with pidx-index ntb_peer_spad_write(pidx, sidx) - write data to Scratchpad register of the peer with pidx-index Since there is hardware which doesn't support Scratchpad registers, the corresponding API methods are now made optional. Signed-off-by: Serge Semin <fancer.lancer@gmail.com> Acked-by: Allen Hubbe <Allen.Hubbe@dell.com> Signed-off-by: Jon Mason <jdmason@kudzu.us>
Diffstat (limited to 'drivers/ntb/test/Kconfig')
0 files changed, 0 insertions, 0 deletions