Lines Matching full:pf
37 * (PF) communication protocol used by the drivers for all devices starting
44 * PF and VF, but uses all other fields internally. Due to this limitation,
51 * The PF is required to return a status code in v_retval for all messages
57 * PF driver, then request a reset, then get resources, then configure
136 /* Opcodes for VF-PF communication. These are placed in the v_opcode field
140 /* The PF sends status change events to VFs using
142 * VFs send requests to the PF using the other ops.
352 u32 vfid; /* used by PF when sending to VF */
360 * VF posts its version number to the PF. PF responds with its version number
362 * Reply from PF has its major/minor versions also in param0 and param1.
368 * changes in the API. The PF must always respond to this message without
389 * VF sends this request to PF with no parameters
390 * PF does NOT respond! VF driver must delay then poll VFGEN_RSTAT register
394 * When reset is complete, PF must ensure that all queues in all VSIs associated
400 /* VSI types that use VIRTCHNL interface for VF-PF communication. VSI_SRIOV
410 * Version 1.0 VF sends this request to PF with no parameters
411 * Version 1.1 VF sends this request to PF with u32 bitmap of its capabilities
412 * PF responds with an indirect message containing
486 * PF configures requested queue and returns a status code.
544 * PF configures requested queue and returns a status code. The
548 * offload must have been set prior to sending this info or the PF
576 * PF configures queues and returns status.
580 * It may send multiple messages. PF drivers must correctly handle all VF
601 * VF sends this message to request the PF to allocate additional queues to
604 * is possible the PF does not have enough queues left to support the request.
605 * If the PF cannot support the number requested it will respond with the
606 * maximum number it is able to support. If the request is successful, PF will
621 * PF configures interrupt mapping and returns status.
651 * PF performs requested action and returns status.
654 * PF drivers must correctly handle all VF requests.
671 * size supported by PF, when VIRTCHNL_VF_LARGE_NUM_QPAIRS is enabled.
676 * of 6 would inform the VF that the PF supports a maximum RSS queue region
697 * PF adds the filters and returns status.
703 * PF removes the filters and returns status.
710 * behavior. The control plane function (i.e. PF) can use a best effort method
712 * guarantee and functionality depends on the implementation of the PF.
719 * function (i.e. PF) to accurately track and use this MAC address for
750 * PF adds the filters and returns status.
751 * If a port VLAN is configured by the PF, this operation will return an
757 * PF removes the filters and returns status.
758 * If a port VLAN is configured by the PF, this operation will return an
774 * populates it the PF should return VIRTCHNL_STATUS_ERR_NOT_SUPPORTED.
781 * by the PF concurrently. For example, if the PF can support
793 * by the PF concurrently. For example if the PF can support
816 * VLAN filtering if the underlying PF supports it.
819 * certain VLAN capability can be toggled. For example if the underlying PF/CP
863 /* The PF populates these fields based on the supported VLAN filtering. If a
864 * field is VIRTCHNL_VLAN_UNSUPPORTED then it's not supported and the PF will
881 * then the request will be rejected by the PF. To prevent failures, the VF
895 * if the PF supports a different ethertype for stripping and insertion.
912 /* The PF populates these fields based on the supported VLAN offloads. If a
913 * field is VIRTCHNL_VLAN_UNSUPPORTED then it's not supported and the PF will
921 * inserted by the VF driver based on the level of offload support. The PF will
941 * PF will mark which capabilities it supports based on hardware support and
942 * current configuration. For example, if a port VLAN is configured the PF will
947 * capabilities in the response message from the PF to determine the VLAN
986 * The PF attempts to add the filters and returns status.
1012 * For example, if the PF populates the virtchnl_vlan_caps.offloads in the
1045 * For example, if the PF populates the virtchnl_vlan_caps.offloads in the
1049 * populated based on what the PF can support.
1074 * There is also the case where a PF and the underlying hardware can support
1076 * the PF populates the virtchnl_vlan_caps.offloads in the following manner the
1116 * For example, if the PF populates the virtchnl_vlan_caps.filtering in the
1154 * PF returns status code in retval.
1170 * field is ignored by the PF.
1172 * PF replies with struct virtchnl_eth_stats in an external buffer.
1192 * VF sends these messages to configure RSS. Only supported if both PF
1196 * Both the key and LUT are initialized to 0 by the PF, meaning that
1221 * VIRTCHNL_OP_GET_RSS_HENA_CAPS to determine which bits the PF is capable of
1258 * By default, the PF sets these to all possible traffic types that the
1277 /* This is used by PF driver to enforce how many channels can be supported.
1279 * PF driver will allow only max 4 channels
1288 * This struct encompasses all the information that the PF needs from
1312 * all the information that the PF needs from the VF to add/delete a
1384 * PF sends this message to inform the VF driver of events that may affect it.
1404 /* If the PF driver does not support the new speed reporting
1432 * When the PF initiates a reset, it writes 0
1434 * When the PF detects that the VF has recovered, it writes 2
1437 * If either the PF or VF reads the register while the hardware
1745 * VF FDIR related request is successfully done by PF
1784 * VF sends this request to PF by filling out vsi_id,
1785 * validate_only and rule_cfg. PF will return flow_id
1805 * VF sends this request to PF by filling out vsi_id
1806 * and flow_id. PF will return del_status to VF.
1821 * VF FLOW related request is successfully done by PF
1846 * VF sends this request to PF by filling out vsi_id,
1848 * PF will return flow_id
1866 * VF sends this request to PF by filling out vsi_id
1867 * and flow_id. PF will return status to VF.
1986 * TX. PF performs requested action and returns status.
2026 * PF maps the requested queue vector maps after validating the queue and vector