diff options
author | Daniel Pieczko <dpieczko@solarflare.com> | 2015-05-05 23:57:14 (GMT) |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2015-05-09 20:16:47 (GMT) |
commit | 45b2449e3f7d870bdd06c6a8557e8d95d59f8737 (patch) | |
tree | bb07cb86bc1a11b1cf3987ff48be648ba400c287 /drivers/fmc | |
parent | 8d9f9dd4487e4792601759b4376441bcc9e54f95 (diff) | |
download | linux-45b2449e3f7d870bdd06c6a8557e8d95d59f8737.tar.xz |
sfc: record the PF's vport ID in nic_data
The default port ID of EVB_PORT_ID_ASSIGNED is a "magic" number
for the MCFW to select the physical port of the PF. If other
vswitches and vports are created on top of the default firmware
configuration, the ID of the newly created vport is then required
when passed to MCDI commands. Currently, this doesn't happen so
the vport_id is never changed, but a subsequent patch will change
this behaviour so that other vswitches and vports are created.
The vport_id recorded in nic_data is only relevant for PFs.
VFs will have their vports created by their parent PF, and in
that case the parent PF will record the vport ID of each VF.
For a VF, nic_data->vport_id is expected to remain at the default
value.
Signed-off-by: Shradha Shah <sshah@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/fmc')
0 files changed, 0 insertions, 0 deletions