Lines Matching refs:handler

46 1.1) Add the handler to your driver's top-level struct:
56 1.2) Initialize the handler:
61   handler is expected to handle. It will allocate a hashtable based on this
64 1.3) Hook the control handler into the driver:
114 1.4) Clean up the handler at the end:
218 This makes it easy to init the handler and just add all controls and only check
243 		struct foo *state = container_of(ctrl->handler, struct foo, ctrl_handler);
365 by the same handler since the handler's lock is held. If you need to access
377 will result in a deadlock since these helpers lock the handler as well.
379 You can also take the handler lock yourself:
494 		struct foo *state = container_of(ctrl->handler, struct foo, ctrl_handler);
604 value of the controls owned by the given handler to the log. You can supply a
612 Usually the V4L2 driver has just one control handler that is global for
619 control handler. You do that by simply setting the ctrl_handler field in
624 manually to add the subdev's control handler (sd->ctrl_handler) to the desired
625 control handler. This control handler may be specific to the video_device or
628 handler for the audio and video controls.
630 If you want to have one handler (e.g. for a radio device node) have a subset
631 of another handler (e.g. for a video device node), then you should first add
632 the controls to the first handler, add the other controls to the second
633 handler and finally add the first handler to the second. For example:
645 Or you can add specific controls to a handler:
669 But sometimes you need to find a control from another handler that you do
678 Since v4l2_ctrl_find will lock the handler you have to be careful where you
693 attempting to find another control from the same handler will deadlock.
701 When one control handler is added to another using v4l2_ctrl_add_handler, then
748 v4l2_ctrl_notify. Note that the control's handler lock is held when the
751 There can be only one notify function per control handler. Any attempt