| /Zephyr-latest/submanifests/ |
| D | optional.yaml | 3 - name: upstream
10 remote: upstream
16 remote: upstream
22 remote: upstream
28 remote: upstream
34 remote: upstream
40 remote: upstream
46 remote: upstream
53 remote: upstream
59 remote: upstream
[all …]
|
| /Zephyr-latest/soc/intel/intel_adsp/ace/ |
| D | comm_widget.h | 195 * and cleared by HW when FW writes to upstream completion control register
227 * Completion data received for upstream non-posted read.
237 * Completion SAI received for upstream non-posted message.
251 * Completion status received for upstream non-posted message
267 * Completion EH present indication received for upstream non-posted message.
298 * Upstream Status
299 * Status register for upstream message.
317 * Upstream message sent interrupt status. Set by HW when upstream message has been
330 * Upstream Command
331 * Command register for upstream message.
[all …]
|
| /Zephyr-latest/scripts/west_commands/ |
| D | README.txt | 6 extensions in upstream west. For example, any commands which operate
7 on the multi-repo need to be in upstream west, not here. Try to limit
22 an upstream pull request, and pull requests which break the tests
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 15 The upstream MCUmgr repository is located `in this page <https://github.com/apache/mynewt-mcumgr>`_.
23 to the upstream repository of MCUmgr and then bring it to Zephyr with snapshot updates.
28 …* The fix, ported to the Zephyr held code from the upstream repository, is backported to the ``v2.…
29 * The fix, done upstream and no longer relevant to the current version, is directly backported
31 * The fix, not present upstream and not relevant for the current version of Zephyr, is
124 * A direct fix from upstream
139 * ``upstream`` - if the fix has originally been merged to the upstream repository.
144 For example, a branch named ``backport-upstream-137-to-v2.7-branch`` indicates a backport of pull
145 request 137, which has already been merged to the upstream repository of MCUmgr.
153 Merging a new fix, that is not a backport of either any upstream or Zephyr fix, does not require an…
|
| D | mcumgr_handlers.rst | 21 to reside in the upstream Zephyr tree to be usable. The first step to creating a handler is to
35 Note that the header files in upstream Zephyr MCUmgr handlers reside in the
57 header file (as upstream Zephyr has) can be used to distribute group IDs more easily.
75 central index header file (as upstream Zephyr has) can be used to distribute event IDs more
98 handler headers are included when including the upstream Zephyr callback header file.
|
| /Zephyr-latest/scripts/schemas/ |
| D | patch-schema.yml | 50 # Whether the patch should be submitted upstream
55 # The URL of the upstream pull request to merge the patch
61 # The URL of the upstream issue associated with the patch, such as an enhancement issue
71 # The SHA-1 hash of the upstream git commit incorporating the associated merge-pr
88 # e.g. "This is a workaround for xyz and probably should not go upstream"
|
| /Zephyr-latest/doc/project/ |
| D | index.rst | 51 - upstream: A parent branch the source code is based on. This is the branch you
52 pull from and push to, basically your upstream.
|
| D | code_flow.rst | 59 - Keep the branch in sync with upstream and update on a regular basis.
60 - Push changes frequently to upstream using the following methods:
|
| /Zephyr-latest/modules/thrift/ |
| D | CMakeLists.txt | 28 # Replace with upstream equivalents when Zephyr's std::thread, etc, are fixed
34 # Replace with upstream equivalents when Zephyr's std::thread, etc, are fixed
|
| /Zephyr-latest/boards/nordic/nrf7002dk/ |
| D | nrf7002dk_nrf5340_cpuapp_defconfig | 26 # ISN needs CS-Rand which isn't supported upstream for nRF boards
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 15 `upstream (vanilla) Zephyr <https://github.com/zephyrproject-rtos/zephyr>`_.
51 include a reference to a binary blob to the upstream Zephyr distribution, a
131 meets these requirements. The project may remove a blob from the upstream
171 which the upstream Zephyr software distribution is open source. As an extreme
175 To mitigate this risk, the scope of upstream library blobs is limited. The
176 project maintainers define an open source test suite that an upstream
186 for any target with upstream Zephyr support.
|
| /Zephyr-latest/drivers/wifi/infineon/ |
| D | cybsp.h | 11 /* here unless we pull in board-specific headers from the upstream driver. */
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 93 * If the module has an external (upstream) project repository, the module
94 repository should preserve the upstream repository folder structure.
109 Synchronizing with upstream
116 synchronizing a module with upstream it is mandatory to document the
123 with upstream code base, may only be applied via pull requests. These pull
145 **Updating modules with a diff from upstream:**
146 Upstream changes brought as a single *snapshot* commit (manual diff) in a
150 upstream history in the module repository.
155 the external project is not hosted in an upstream Git repository.
157 The commit message is expected to identify the upstream project URL, the
[all …]
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | README_http_parser | 5 externally maintained open source project. The original upstream code
|
| /Zephyr-latest/tests/modules/thrift/ThriftTest/ |
| D | overlay-tls.conf | 6 # Additionally, upstream Apache Thrift uses socketpair for cancellation rather
|
| /Zephyr-latest/tests/subsys/fs/common/ |
| D | test_fs_basic.c | 62 /* Anomalous behavior requiring upstream response */ in create_write_hello()
65 * an open file. See upstream issue #250. in create_write_hello()
227 /* Anomalous behavior requiring upstream response */ in truncate_hello()
230 * an open file. See upstream issue #250. in truncate_hello()
310 /* Upstream issue #250 */ in sync_goodbye()
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings.rst | 28 bindings-upstream.rst
|
| D | bindings-upstream.rst | 3 Rules for upstream bindings
7 submit to the upstream Zephyr Project. (You don't need to follow these rules
223 - Zephyr-specific extensions to bindings we share with upstream Linux. One
|
| /Zephyr-latest/samples/tfm_integration/tfm_psa_test/ |
| D | sample.yaml | 40 # issues have been sorted out upstream.
|
| /Zephyr-latest/drivers/espi/ |
| D | espi_it8xxx2.c | 1007 LOG_ERR("%s: OOB upstream busy", __func__); in espi_it8xxx2_send_oob()
1028 /* Set upstream enable */ in espi_it8xxx2_send_oob()
1030 /* Set upstream go */ in espi_it8xxx2_send_oob()
1098 /* Upstream interrupt enable */ in espi_it8xxx2_oob_init()
1140 LOG_ERR("%s: Upstream busy (tran:%d)", __func__, tran); in espi_it8xxx2_flash_trans()
1187 /* Set upstream enable */ in espi_it8xxx2_flash_read()
1189 /* Set upstream go */ in espi_it8xxx2_flash_read()
1192 /* Wait until upstream done or timeout */ in espi_it8xxx2_flash_read()
1235 /* Set upstream enable */ in espi_it8xxx2_flash_write()
1237 /* Set upstream go */ in espi_it8xxx2_flash_write()
[all …]
|
| /Zephyr-latest/ |
| D | west.yml | 1 # The west manifest file for upstream Zephyr.
19 remote: upstream
22 - name: upstream
|
| /Zephyr-latest/boards/renode/riscv32_virtual/doc/ |
| D | index.rst | 9 configurations that only exist in proprietary boards/SoCs to be tested in upstream CI.
|
| /Zephyr-latest/samples/modules/lvgl/demos/ |
| D | sample.yaml | 2 description: LVGL sample, containing all upstream demos
|
| /Zephyr-latest/modules/openthread/ |
| D | Kconfig.features | 160 bool "Forwarding DNS queries to upstream"
162 Enable forwarding DNS queries to platform DNS upstream API
|
| /Zephyr-latest/tests/lib/cmsis_dsp/interpolation/src/ |
| D | q31.c | 32 * FIXME: Remove the cast below once the upstream CMSIS is in ZTEST()
|
