Lines Matching refs:subfunction

39        subfunction (SF).
130 SRIOV VFs, a subfunction doesn't require its own PCI virtual function.
131 A subfunction communicates with the hardware through the parent PCI function.
133 To use a subfunction, 3 steps setup sequence is followed.
134 (1) create - create a subfunction;
135 (2) configure - configure subfunction attributes;
136 (3) deploy - deploy the subfunction;
139 User performs setup on the subfunction management device.
143 A subfunction is created using a devlink port interface. A user adds the
144 subfunction by adding a devlink port of subfunction flavour. The devlink
145 kernel code calls down to subfunction management driver (devlink ops) and asks
146 it to create a subfunction devlink port. Driver then instantiates the
147 subfunction port and any associated objects such as health reporters and
152 A subfunction devlink port is created but it is not active yet. That means the
154 but the subfunction device itself is not created. A user might use e-switch port
157 subfunction while subfunction is inactive.
161 Once a subfunction is configured, user must activate it to use it. Upon
162 activation, subfunction management driver asks the subfunction management
163 device to instantiate the subfunction device on particular PCI function.
164 A subfunction device is created on the :ref:`Documentation/driver-api/auxiliary_bus.rst <auxiliary_…
165 At this point a matching subfunction driver binds to the subfunction's auxiliary device.
222      -  A bus device of the subfunction, usually on a auxiliary bus.
224      -  A device driver for the subfunction auxiliary device.
226      -  A PCI physical function that supports subfunction management.
229         subfunction management using devlink port interface.
231      -  A device driver for PCI physical function that hosts subfunction
232         devices. In most cases it is same as subfunction management driver. When
233         subfunction is used on external controller, subfunction management and