Searched refs:labels (Results 26 – 50 of 72) sorted by relevance
123
| /Zephyr-latest/doc/build/dts/ |
| D | intro-syntax-structure.rst | 49 .. _dt-node-labels:
51 Nodes can be assigned *node labels*, which are unique shorthands that refer to
53 ``subnode_nodelabel``. A node can have zero, one, or multiple node labels. You
54 can use node labels to refer to the node elsewhere in the devicetree.
311 which is distinct from the standard :ref:`node label <dt-node-labels>`.
403 <dt-node-labels>`. Here is an example devicetree fragment:
441 There are two additional ways beyond :ref:`node labels <dt-node-labels>` to
|
| D | howtos.rst | 419 ``struct device``: using instance numbers, and using node labels.
531 Option 2: create devices using node labels
542 labels like ``mydevice0``, ``mydevice1``, etc. appropriately for the IP blocks
559 The driver can use the ``mydevice0`` and ``mydevice1`` node labels in the
|
| D | api-usage.rst | 43 label <dt-node-labels>`. Node labels are often provided by SoC :file:`.dtsi`
|
| /Zephyr-latest/subsys/net/lib/dns/ |
| D | dns_sd.c | 364 const char *labels[] = { in add_ptr_record() local
428 for (i = 1; i < ARRAY_SIZE(labels); ++i) { in add_ptr_record()
429 label_size = strlen(labels[i]); in add_ptr_record()
430 buf[offset++] = strlen(labels[i]); in add_ptr_record()
431 memcpy(&buf[offset], labels[i], label_size); in add_ptr_record()
433 if (i == ARRAY_SIZE(labels) - 1) { in add_ptr_record()
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 5 labels: RFC
|
| D | 001_bug_report.md | 5 labels: bug
|
| D | 007_ext-source.md | 5 labels: TSC
|
| /Zephyr-latest/samples/drivers/i2s/echo/ |
| D | README.rst | 21 a devicetree node label named ``i2s_rxtx`` or separate node labels ``i2s_rx``
|
| /Zephyr-latest/scripts/release/ |
| D | bug_bash.py | 124 issues = self._repo.get_issues(state='closed', labels=[
|
| /Zephyr-latest/boards/others/stm32f030_demo/doc/ |
| D | index.rst | 5 been exposed in the external headers with silk screen labels
|
| /Zephyr-latest/scripts/dts/ |
| D | gen_defines.py | 94 out_dt_define(f"{node.z_path_id}_NODELABEL_NUM", len(node.labels))
96 " ".join(f"fn({nodelabel})" for nodelabel in node.labels))
98 " ".join(f"fn({nodelabel}, __VA_ARGS__)" for nodelabel in node.labels))
246 idents.extend(f"N_NODELABEL_{str2ident(label)}" for label in node.labels)
|
| /Zephyr-latest/scripts/ |
| D | get_maintainer.py | 193 area.labels = area_dict.get("labels", [])
415 ", ".join(area.labels),
|
| /Zephyr-latest/boards/shields/x_nucleo_53l0a1/doc/ |
| D | index.rst | 39 The sensors have the following device tree labels and I2C addresses:
|
| /Zephyr-latest/samples/modules/tflite-micro/magic_wand/train/ |
| D | train.py | 150 labels=tf.constant(test_labels),
|
| /Zephyr-latest/doc/project/ |
| D | dev_env_and_tools.rst | 242 GitHub **labels** to classify and organize these issues and PRs by area, type,
246 Issues and PRs often have multiple labels assigned,
248 When reviewing a PR, if it has missing or incorrect labels, maintainers shall
254 These are the labels we currently have, grouped by applicability:
340 For all labels applicable to PRs: Please note that the label, together with
|
| D | proposals.rst | 6 For feature tracking we use Github labels to classify new features and
|
| /Zephyr-latest/boards/mikroe/mini_m4_for_stm32/doc/ |
| D | mikroe_mini_m4_for_stm32.rst | 20 in the external header with silk screen labels that match the SoC's pin names.
|
| /Zephyr-latest/boards/others/stm32_min_dev/doc/ |
| D | index.rst | 25 in the external header with silk screen labels that match the SoC's pin names.
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.2.rst | 103 The labels have also been changed along, so no changes are necessary for regular use.
|
| /Zephyr-latest/dts/xtensa/intel/ |
| D | intel_adsp_cavs25_tgph.dtsi | 235 * with node labels, which has problems. A better representation
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 187 - The labels ``API``, ``Breaking API Change`` and ``Release Notes``, as well as
240 `GitHub issue <https://github.com/zephyrproject-rtos/zephyr/labels/deprecation_tracker>`_
|
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 47 ``snippet-<name>`` as a namespace prefix when choosing names for node labels,
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 253 privileges to add labels to PRs, in this case the contributor should request
314 .. _dev-review: https://github.com/zephyrproject-rtos/zephyr/labels/dev-review
|
| /Zephyr-latest/scripts/west_commands/ |
| D | sign.py | 377 for label in node.labels
|
| /Zephyr-latest/scripts/kconfig/ |
| D | kconfigfunctions.py | 851 if label in node.labels:
|
123
