Lines Matching full:subdevice

158 run-time bridge-subdevice interaction is in both cases the same.
182 In the **asynchronous** case subdevice probing can be invoked independently of
183 the bridge driver availability. The subdevice driver then has to verify whether
187 attempts. Once all conditions are met the subdevice shall be registered using
202 Second, bridge drivers can then begin to form a list of subdevice descriptors
204 to add subdevice descriptors to a notifier, depending on the type of device and
243 .complete() callback is called. When a subdevice is removed from the
318 opt for making the subdevice operations directly accessible from userpace.
373 want userspace to be able to change the same parameters through the subdevice
376 It is sometimes useful to report to userspace the current subdevice
378 change to the device parameters but allows interfacing to the subdevice device
384 such use cases, bridge drivers may expose the subdevice operations to userspace
399 	These ioctls are only allowed on a read-only subdevice device node
407 	These ioctls are not allowed on a read-only subdevice node.