Searched refs:schedulable (Results 1 – 6 of 6) sorted by relevance
843 bool schedulable = false; in subvp_drr_schedulable() local896 schedulable = true; in subvp_drr_schedulable()898 return schedulable; in subvp_drr_schedulable()920 bool schedulable = false; in subvp_vblank_schedulable() local959 schedulable = subvp_drr_schedulable(dc, context, &context->res_ctx.pipe_ctx[vblank_index]); in subvp_vblank_schedulable()984 schedulable = true; in subvp_vblank_schedulable()986 return schedulable; in subvp_vblank_schedulable()1007 bool schedulable = true; // true by default for single display case in subvp_validate_static_schedulability() local1035 schedulable = subvp_subvp_schedulable(dc, context); in subvp_validate_static_schedulability()1040 schedulable = false; in subvp_validate_static_schedulability()[all …]
139 configuration schedulable:
385 necessary: there are task sets that are schedulable, but do not respect the
64 W - group is weak and will fallback to non-group if not schedulable,
2639 int schedulable = mod_flags & FTRACE_MODIFY_MAY_SLEEP_FL; in ftrace_replace_code() local2656 if (schedulable) in ftrace_replace_code()
1963 Another note is that this callback is non-atomic (schedulable) as1965 because the ``trigger`` callback is atomic (non-schedulable). That is,
