Searched refs:change (Results 1 – 25 of 317) sorted by relevance
12345678910>>...13
/Zephyr-latest/.github/ISSUE_TEMPLATE/ |
D | 003_rfc-proposal.md | 14 need a quick explanation of your proposed change. 19 Why do we want this change and what problem are we trying to address? 22 ### Proposed change 24 A brief summary of the proposed change - the 10,000 ft view on what it will 25 change once this change is implemented. 35 ### Proposed change (Detailed) 37 This section is freeform - you should describe your change in as much detail 42 you're planning to change and how. 47 Highlight how the change may affect the rest of the project (new components,
|
/Zephyr-latest/samples/subsys/zbus/hello_world/ |
D | README.rst | 41 D: START processing channel acc_data change 43 D: FINISH processing channel acc_data change 45 D: START processing channel acc_data change 47 D: FINISH processing channel acc_data change
|
/Zephyr-latest/scripts/release/ |
D | list_devicetree_bindings_changes.py | 450 for change in changes: 451 self.print_change(change) 454 def print_change(self, change: BindingChange) -> None: 460 if isinstance(change, ModifiedSpecifier2Cells): 463 elif isinstance(change, ModifiedBuses): 465 elif isinstance(change, AddedProperty): 467 elif isinstance(change, RemovedProperty): 469 elif isinstance(change, ModifiedPropertyType): 471 elif isinstance(change, ModifiedPropertyEnum): 473 elif isinstance(change, ModifiedPropertyConst): [all …]
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | cfg.rst | 6 The runtime configuration API allows applications to change their runtime 12 Configuration Client can communicate with to change the node configuration. In some 15 scenarios, this API can be used to change the configuration locally.
|
/Zephyr-latest/samples/subsys/zbus/uart_bridge/ |
D | README.rst | 35 D: START processing channel start_measurement change 36 D: FINISH processing channel start_measurement change 38 D: START processing channel sensor_data change 39 D: FINISH processing channel sensor_data change 48 D: START processing channel start_measurement change 49 D: FINISH processing channel start_measurement change 54 D: START processing channel sensor_data change 55 D: FINISH processing channel sensor_data change
|
/Zephyr-latest/submanifests/ |
D | example.yaml.sample | 6 # Then change the 'name' and 'url' below and run 'west update'. 12 # branch, change the 'revision' line accordingly.
|
/Zephyr-latest/doc/connectivity/usb/device_next/api/ |
D | usbd.rst | 6 New USB device stack API is experimental and is subject to change without notice.
|
/Zephyr-latest/boards/infineon/cy8cproto_063_ble/ |
D | Kconfig.defconfig | 9 # No defaults to change for now
|
/Zephyr-latest/samples/drivers/led/led_strip/boards/ |
D | bbc_microbit.overlay | 14 chain-length = <16>; /* arbitrary; change at will */
|
D | nucleo_g071rb.overlay | 19 chain-length = <16>; /* arbitrary; change at will */
|
D | nucleo_l476rg.overlay | 19 chain-length = <16>; /* arbitrary; change at will */
|
D | nrf5340dk_nrf5340_cpuapp.overlay | 24 chain-length = <42>; /* arbitrary; change at will */
|
/Zephyr-latest/drivers/flash/ |
D | Kconfig.simulator | 31 to erase-value prior to write as it only allows to change bits from erase-value 46 Keep in mind that write operations can only change value of a bit from erase-value to the 50 but only change from erase-value to opposite will be registered.
|
/Zephyr-latest/doc/develop/api/ |
D | overview.rst | 14 change at any time. The public API SHOULD NOT be considered stable. 31 change that fixes incorrect behavior. 41 breaking change was made to the API.
|
D | api_lifecycle.rst | 7 given API will not change in future releases. At the same time, developers 29 Experimental APIs denote that a feature was introduced recently, and may change 127 A breaking API change is defined as one that forces users to modify their 130 itself) is not considered a breaking API change. 132 In order to restrict and control the introduction of a change that breaks the 134 such a change is considered necessary in order to accept it in the project: 143 - Background information on why the change is required 145 - Brief description of the API change 152 to adapt out-of-tree users of the API to the change 167 opened on GitHub. It is left to the person proposing the change to decide [all …]
|
/Zephyr-latest/doc/connectivity/usb/host/api/ |
D | uhc.rst | 10 UHC driver API is experimental and is subject to change without notice.
|
/Zephyr-latest/doc/project/ |
D | dev_env_and_tools.rst | 22 submitting a change or an enhancement to any Zephyr component, a developer 57 - An author of a change can suggest in his pull-request which category a change 59 changes can change the label of a pull request by adding a comment justifying 60 why a change should belong to another category. 70 Any change that is a fix to an issue that blocks developers from doing their 83 involvement. Such changes should not change the logic or the design of a 84 subsystem or component. For example a trivial change can be: 112 Changes that introduce new features or functionality or change the way the 116 stakeholders are made aware of the change. 140 when reviewers are not available and there is a need to get a code change into [all …]
|
/Zephyr-latest/boards/nordic/nrf9131ek/ |
D | board.cmake | 11 # TODO: change to nRF9131_xxAA when such device is available in JLink
|
/Zephyr-latest/boards/nordic/nrf9151dk/ |
D | board.cmake | 11 # TODO: change to nRF9151_xxAA when such device is available in JLink
|
/Zephyr-latest/boards/nordic/nrf9161dk/ |
D | board.cmake | 11 # TODO: change to nRF9161_xxAA when such device is available in JLink
|
/Zephyr-latest/tests/drivers/gpio/gpio_api_1pin/boards/ |
D | up_squared.overlay | 11 * Need to change the BIOS settings:
|
/Zephyr-latest/drivers/clock_control/ |
D | Kconfig.litex | 12 It gives ability to change clock parameters
|
/Zephyr-latest/doc/build/dts/ |
D | main-example.dts | 7 * If you change it for one example, you could break others, so be careful.
|
/Zephyr-latest/tests/subsys/settings_commit_prio/ |
D | README.rst | 18 To build for another board, change ``native_sim`` above to that board's name.
|
/Zephyr-latest/tests/drivers/gpio/gpio_basic_api/boards/ |
D | up_squared.overlay | 11 * Need to change the BIOS settings:
|
12345678910>>...13