Lines Matching full:subdevice

161 run-time bridge-subdevice interaction is in both cases the same.
185 In the **asynchronous** case subdevice probing can be invoked independently of
186 the bridge driver availability. The subdevice driver then has to verify whether
190 attempts. Once all conditions are met the subdevice shall be registered using
206 begin to form a list of subdevice descriptors that the bridge device
207 needs for its operation. Subdevice descriptors are added to the notifier
210 and a pointer to the subdevice descripter, which is of type struct
216 .complete() callback is called. When a subdevice is removed from the
291 opt for making the subdevice operations directly accessible from userpace.
346 want userspace to be able to change the same parameters through the subdevice
349 It is sometimes useful to report to userspace the current subdevice
351 change to the device parameters but allows interfacing to the subdevice device
357 such use cases, bridge drivers may expose the subdevice operations to userspace
372 	These ioctls are only allowed on a read-only subdevice device node
380 	These ioctls are not allowed on a read-only subdevice node.