Lines Matching full:cluster

405 In that case you need to 'cluster' them:
422 cluster is set (or 'gotten', or 'tried'), only the control ops of the first
435 			struct v4l2_ctrl *mute = ctrl->cluster[AUDIO_CL_MUTE];
449 	ctrl == ctrl->cluster[AUDIO_CL_VOLUME] == state->audio_cluster[AUDIO_CL_VOLUME]
450 	ctrl->cluster[AUDIO_CL_MUTE] == state->audio_cluster[AUDIO_CL_MUTE]
452 In practice using cluster arrays like this becomes very tiresome. So instead
456 		/* audio cluster */
461 The anonymous struct is used to clearly 'cluster' these two control pointers,
471 Note that controls in a cluster may be NULL. For example, if for some
474 cluster of 2 controls, of which only 1 is actually instantiated. The
475 only restriction is that the first control of the cluster must always be
476 present, since that is the 'master' control of the cluster. The master
477 control is the one that identifies the cluster and that provides the
478 pointer to the v4l2_ctrl_ops struct that is used for that cluster.
480 Obviously, all controls in the cluster array must be initialized to either
483 In rare cases you might want to know which controls of a cluster actually
485 each control. For example, in the case of a volume/mute cluster the 'is_new'
496 A common type of control cluster is one that handles 'auto-foo/foo'-type
502 If the cluster is in automatic mode, then the manual controls should be
507 If the cluster is put in manual mode, then the manual controls should become
523 tells the framework which value switches the cluster into manual mode. The
530 The first control of the cluster is assumed to be the 'auto' control.