Lines Matching full:subdevice

158 run-time bridge-subdevice interaction is in both cases the same.
189 In the **asynchronous** case subdevice probing can be invoked independently of
190 the bridge driver availability. The subdevice driver then has to verify whether
194 attempts. Once all conditions are met the subdevice shall be registered using
361 opt for making the subdevice operations directly accessible from userspace.
416 want userspace to be able to change the same parameters through the subdevice
419 It is sometimes useful to report to userspace the current subdevice
421 change to the device parameters but allows interfacing to the subdevice device
427 such use cases, bridge drivers may expose the subdevice operations to userspace
442 	These ioctls are only allowed on a read-only subdevice device node
450 	These ioctls are not allowed on a read-only subdevice node.
585 by initializing the subdevice state with a call to v4l2_subdev_init_finalize()
600 subdevice active state, which drivers can exclusively access by
607 While the V4L2 core passes the correct try or active state to the subdevice
610 issues with subdevice drivers that let the V4L2 core manage the active state,
612 conversion of subdevice drivers to a managed active state without having to
636 A subdevice driver can implement support for multiplexed streams by setting