Lines Matching refs:client

454 …re invokes OSAL\_SLOWPATH\_IRQ\_REQ() callback for each HW function. The client implementation sho…
495 If ecore client is not using binary firmware file or instead using firmware from regular header fil…
751 …s need to be committed to the hardware or just cache at the driver. When client requests the commi…
755 … ecore. OSAL\_DCBX\_AEN() would be called after such notification, ecore client would need to prov…
761 …\item Pulling – if ecore can’t provide information on its own, ecore-client would be required to i…
762 \item Pushing – it’s the ecore and ecore-client’s responsibility to push the data.\\
764client. If that’s not possible, it becomes more risky as the responsibility of doing things correc…
803 …nformation with the help of ecore clients and sends it to the MFW. Ecore client need to provide ne…
805 …ation from the MFW. The execution context in interrupt mode, hence ecore client need to schedule a…
806client need to fill in the values for all the fields that it's aware of, and also need to set the …
851 …In addition, ecore would also fill a \texttt{p\_handle}. This handle is opaque to the ecore-client
940 …e correct number of HW-functions under the PCI device. The ecore and its client should access only…
969 …ocated and 2 MSI-X vectors configured to support them, as it's the ecore-client responsibility for…
1278 …add\_user}{rdma_add_user} -- this function allocates a dpi index for the client.During initializat…
1488client has the ability to signal ecore that a specific tcp port in app tlv should be recognized as…
1647 One optional auxilary function that can be used by the ecore-client is \myfunc{iov\_pf\_get\_pendin…
1753 To enable PTP support, ecore-client should call \myfunc{ptp\_enable}{ptp_enable} and then configure…
1761 As part of feature clean up, ecore client should call \myfunc{ptp\_disable}{ptp_disable} API to dis…