Lines Matching refs:cluster

468 In that case you need to 'cluster' them:
485 cluster is set (or 'gotten', or 'tried'), only the control ops of the first
498 			struct v4l2_ctrl *mute = ctrl->cluster[AUDIO_CL_MUTE];
512 	ctrl == ctrl->cluster[AUDIO_CL_VOLUME] == state->audio_cluster[AUDIO_CL_VOLUME]
513 	ctrl->cluster[AUDIO_CL_MUTE] == state->audio_cluster[AUDIO_CL_MUTE]
515 In practice using cluster arrays like this becomes very tiresome. So instead
519 		/* audio cluster */
524 The anonymous struct is used to clearly 'cluster' these two control pointers,
534 Note that controls in a cluster may be NULL. For example, if for some
537 cluster of 2 controls, of which only 1 is actually instantiated. The
538 only restriction is that the first control of the cluster must always be
539 present, since that is the 'master' control of the cluster. The master
540 control is the one that identifies the cluster and that provides the
541 pointer to the v4l2_ctrl_ops struct that is used for that cluster.
543 Obviously, all controls in the cluster array must be initialized to either
546 In rare cases you might want to know which controls of a cluster actually
548 each control. For example, in the case of a volume/mute cluster the 'is_new'
559 A common type of control cluster is one that handles 'auto-foo/foo'-type
565 If the cluster is in automatic mode, then the manual controls should be
570 If the cluster is put in manual mode, then the manual controls should become
586 tells the framework which value switches the cluster into manual mode. The
593 The first control of the cluster is assumed to be the 'auto' control.