Searched refs:d1 (Results 1 – 11 of 11) sorted by relevance
23 ("${compile_path}" "${args_all[@]}" "${args_dev[@]}" -d=1 || echo d1 $?) &
103 int d1 = thread_deadlines[exec_order[i]]; in ZTEST() local105 zassert_true(d0 <= d1, "threads ran in wrong order"); in ZTEST()
31 DEFINE_DATA(d1, 1, 2);62 above would visit ``d1``, ``d2`` and ``d3`` in that order, regardless of how
45 group_d1: group-d1-map {
397 d1 = mock.Mock()398 d1.dep_ordinal = 2405 dev1.depends_on = [d1]
30 --link-color-hover: #3091d1;
148 distinct devicetree nodes ``n1`` and ``n2`` with dependency ordinals ``d1`` and151 - ``d1 != d2``152 - if ``n1`` depends on ``n2``, then ``d1 > d2``153 - ``d1 > d2`` does **not** necessarily imply that ``n1`` depends on ``n2``
162 fmdrr d1, r1, r1
101 … 9a 06 93 76 12 cb 0f 7e ec c5 12 6f 64 db d1 ff |...v...~ ...od...
120 uint32_t d1 = thread_1->base.prio_deadline; in z_sched_prio_cmp() local123 if (d1 != d2) { in z_sched_prio_cmp()129 return (int32_t) (d2 - d1); in z_sched_prio_cmp()
434 * Added experimental support for Mesh Protocol d1.1r18 specification, gated467 …* Added experimental support for Mesh Binary Large Object Transfer Model d1.0r04_PRr00 specificati…468 * Added experimental support for Mesh Device Firmware Update Model d1.0r04_PRr00 specification.
