Lines Matching refs:subfunction

39        subfunction (SF).
303 SRIOV VFs, a subfunction doesn't require its own PCI virtual function.
304 A subfunction communicates with the hardware through the parent PCI function.
306 To use a subfunction, 3 steps setup sequence is followed:
308 1) create - create a subfunction;
309 2) configure - configure subfunction attributes;
310 3) deploy - deploy the subfunction;
313 User performs setup on the subfunction management device.
317 A subfunction is created using a devlink port interface. A user adds the
318 subfunction by adding a devlink port of subfunction flavour. The devlink
319 kernel code calls down to subfunction management driver (devlink ops) and asks
320 it to create a subfunction devlink port. Driver then instantiates the
321 subfunction port and any associated objects such as health reporters and
326 A subfunction devlink port is created but it is not active yet. That means the
328 but the subfunction device itself is not created. A user might use e-switch port
331 subfunction while subfunction is inactive.
335 Once a subfunction is configured, user must activate it to use it. Upon
336 activation, subfunction management driver asks the subfunction management
337 device to instantiate the subfunction device on particular PCI function.
338 A subfunction device is created on the :ref:`Documentation/driver-api/auxiliary_bus.rst <auxiliary_…
339 At this point a matching subfunction driver binds to the subfunction's auxiliary device.
431      -  A bus device of the subfunction, usually on a auxiliary bus.
433      -  A device driver for the subfunction auxiliary device.
435      -  A PCI physical function that supports subfunction management.
438         subfunction management using devlink port interface.
440      -  A device driver for PCI physical function that hosts subfunction
441         devices. In most cases it is same as subfunction management driver. When
442         subfunction is used on external controller, subfunction management and