Lines Matching full:pf

36  * This header file describes the VF-PF communication protocol used
43  * PF and VF, but uses all other fields internally. Due to this limitation,
50  * The PF is required to return a status code in v_retval for all messages
56  * PF driver, then request a reset, then get resources, then configure
117 /* Opcodes for VF-PF communication. These are placed in the v_opcode field
121 /* The PF sends status change events to VFs using
123  * VFs send requests to the PF using the other ops.
184 	u32 vfid;			 /* used by PF when sending to VF */
192  * VF posts its version number to the PF. PF responds with its version number
194  * Reply from PF has its major/minor versions also in param0 and param1.
200  * changes in the API. The PF must always respond to this message without
218  * VF sends this request to PF with no parameters
219  * PF does NOT respond! VF driver must delay then poll VFGEN_RSTAT register
223  * When reset is complete, PF must ensure that all queues in all VSIs associated
229 /* VSI types that use VIRTCHNL interface for VF-PF communication. VSI_SRIOV
239  * Version 1.0 VF sends this request to PF with no parameters
240  * Version 1.1 VF sends this request to PF with u32 bitmap of its capabilities
241  * PF responds with an indirect message containing
306  * PF configures requested queue and returns a status code.
324  * PF configures requested queue and returns a status code. The
328  * offload must have been set prior to sending this info or the PF
354  * PF configures queues and returns status.
358  * It may send multiple messages. PF drivers must correctly handle all VF
379  * VF sends this message to request the PF to allocate additional queues to
382  * is possible the PF does not have enough queues left to support the request.
383  * If the PF cannot support the number requested it will respond with the
384  * maximum number it is able to support.  If the request is successful, PF will
399  * PF configures interrupt mapping and returns status.
429  * PF performs requested action and returns status.
432  * PF drivers must correctly handle all VF requests.
446  * PF adds the filters and returns status.
452  * PF removes the filters and returns status.
472  * PF adds the filters and returns status.
473  * If a port VLAN is configured by the PF, this operation will return an
479  * PF removes the filters and returns status.
480  * If a port VLAN is configured by the PF, this operation will return an
494  * PF returns status code in retval.
510  * field is ignored by the PF.
512  * PF replies with struct virtchnl_eth_stats in an external buffer.
532  * VF sends these messages to configure RSS. Only supported if both PF
536  * Both the key and LUT are initialized to 0 by the PF, meaning that
558  * By default, the PF sets these to all possible traffic types that the
568 /* This is used by PF driver to enforce how many channels can be supported.
570  * PF driver will allow only max 4 channels
579  * This struct encompasses all the information that the PF needs from
603  * all the information that the PF needs from the VF to add/delete a
663  * PF sends this message to inform the VF driver of events that may affect it.
682 		/* If the PF driver does not support the new speed reporting
707  * VF uses this message to request PF to map IWARP vectors to IWARP queues.
715  * PF configures interrupt mapping and returns status.
765  * When the PF initiates a reset, it writes 0
767  * When the PF detects that the VF has recovered, it writes 2
770  * If either the PF or VF reads the register while the hardware