Home
last modified time | relevance | path

Searched full:change (Results 1 – 25 of 994) sorted by relevance

12345678910>>...40

/Zephyr-latest/.github/ISSUE_TEMPLATE/
D003_rfc-proposal.md14 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/scripts/release/
Dlist_devicetree_bindings_changes.py41 '''Marker type for an individual change that happened to a
450 for change in changes:
451 self.print_change(change)
454 def print_change(self, change: BindingChange) -> None:
458 print(f'property ``{change.property}`` {details} changed from '
459 f'{change.start} to {change.end}')
460 if isinstance(change, ModifiedSpecifier2Cells):
461 print(f'specifier cells for space "{change.space}" '
462 f'are now named: {change.end} (old value: {change.start})')
463 elif isinstance(change, ModifiedBuses):
[all …]
/Zephyr-latest/tests/bsim/bluetooth/host/gatt/settings/src/
Dserver.c51 printk("register second service, peer will be change-unaware\n"); in server_round_1()
54 * start, the peer will be marked as change-unaware in server_round_1()
70 * that the change-aware status has been written correctly to in server_round_2()
87 printk("register second service, peer will be change-unaware\n"); in server_round_3()
90 * start, the peer will be marked as change-unaware in server_round_3()
137 * Round 1 -> 2: test change-awareness is updated if GATT DB changes _after_ the
142 * writes the change-awareness before we get disconnected. Basically, this
151 * Round 4 -> 5: tests change-awareness status is still written on disconnect.
158 * time to execute and store that the peers are now change-unaware. Round 6 then
159 * makes sure that we are indeed change-unaware.
Dclient.c31 * become change-aware. in client_round_0()
56 /* server should remember we are change-aware */ in client_round_1()
72 /* We are change-unaware. wait until the Service Changed indication is in client_round_2()
73 * received, that should then make us change-aware. in client_round_2()
97 /* server should remember we are change-aware */ in client_round_3()
102 * In the next round, we will be change-unaware, so the first ATT read in client_round_3()
104 * change-aware again. in client_round_3()
/Zephyr-latest/samples/subsys/zbus/uart_bridge/
DREADME.rst35 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/doc/develop/api/
Dapi_lifecycle.rst7 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:
141 Title: RFC: Breaking API Change: <subsystem>
143 - Background information on why the change is required
144 - Proposed Change (detailed):
145 - Brief description of the API change
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dcfg.rst6 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/hello_world/
DREADME.rst41 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/dts/bindings/sensor/
Despressif,esp32-pcnt.yaml119 0 (Default) - Inhibit counter (counter value will not change in this condition).
132 0 (Default) - Inhibit counter (counter value will not change in this condition).
145 0 (Default) - Don't change counter mode.
147 2 - Control mode: Inhibit counter (counter value will not change in this condition).
158 0 (Default) - Don't change counter mode.
160 2 - Control mode: Inhibit counter (counter value will not change in this condition).
/Zephyr-latest/samples/boards/nordic/system_off/
Dsample.yaml114 - "Entering system off; change signal level at comparator input to restart"
117 - "Entering system off; change signal level at comparator input to restart"
120 - "Entering system off; change signal level at comparator input to restart"
144 - "Entering system off; change signal level at comparator input to restart"
150 - "Entering system off; change signal level at comparator input to restart"
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/priv_beacon/
Dpriv_beacon_ivu_long_interval.sh8 # Random value is expected to change before Random Interval is reached due to
9 # Flags field change.
Dpriv_beacon_kr_long_interval.sh8 # Random value is expected to change before Random Interval is reached due to
9 # Flags field change.
/Zephyr-latest/tests/net/conn_mgr_monitor/src/
Dmain.c297 "No events should be fired if connectivity availability did not change."); in cycle_ready_ifaces()
318 "No events should be fired if connectivity availability did not change."); in cycle_ready_ifaces()
327 "No events should be fired if connectivity availability did not change."); in cycle_ready_ifaces()
345 * At several points, change the readiness state of ifa and ensure events are fired.
367 /* Set one: Change A state between B state toggles */ in cycle_ignored_iface()
379 "No events should be fired if connectivity availability did not change."); in cycle_ignored_iface()
381 "No events should be fired if connectivity availability did not change."); in cycle_ignored_iface()
383 "No events should be fired if connectivity availability did not change."); in cycle_ignored_iface()
392 "No events should be fired if connectivity availability did not change."); in cycle_ignored_iface()
394 "No events should be fired if connectivity availability did not change."); in cycle_ignored_iface()
[all …]
/Zephyr-latest/dts/bindings/pinctrl/
Dmicrochip,xec-pinctrl.yaml48 To change a pin's pinctrl default properties add a reference to the
99 default: "no-change"
101 - "no-change"
112 default: "no-change"
114 - "no-change"
/Zephyr-latest/submanifests/
Dexample.yaml.sample6 # Then change the 'name' and 'url' below and run 'west update'.
12 # branch, change the 'revision' line accordingly.
/Zephyr-latest/samples/drivers/led/is31fl3216a/src/
Dmain.c31 LOG_ERR("Could not change brightness: %i", status); in pulse_led()
41 LOG_ERR("Could not change brightness: %i", status); in pulse_led()
60 LOG_ERR("Could not change brightness: %i", status); in pulse_leds()
73 LOG_ERR("Could not change brightness: %i", status); in pulse_leds()
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Drpr.h59 /** Change the Device key. */
61 /** Change the Device key and address. Device composition may change. */
63 /** Change the Device key and composition. */
/Zephyr-latest/doc/project/
Ddev_env_and_tools.rst22 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/dts/bindings/power-domain/
Dpower-domain-gpio-monitor.yaml9 change physical state of power rails and that action won't be triggered on
11 pending transaction won't be interrupted by power state change.
/Zephyr-latest/drivers/flash/
DKconfig.simulator31 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/include/zephyr/drivers/misc/grove_lcd/
Dgrove_lcd.h59 * @brief Function to change the display state.
60 * @details This function provides the user the ability to change the state
80 /* Defines for the GLCD_CMD_INPUT_SET to change text direction */
86 * @brief Function to change the input state.
87 * @details This function provides the user the ability to change the state
119 * @details This function provides the user the ability to change the state
/Zephyr-latest/dts/bindings/pwm/
Dnxp,pca9685.yaml23 Outputs change on ACK. Otherwise the outputs change on STOP
/Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt_client/
DKconfig27 Change default value when platform needs different data alignment.
33 Change default value when platform needs a different time.
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/provision/
Dpb_remote_pst_ncrp.sh8 # 1. Prepare for Composition Data change.
17 # - call bt_mesh_comp_change_prepare() to prepare for Composition Data change
27 # 3. Verify that old settings are removed on the 3rd device after Composition Data change.
/Zephyr-latest/modules/hal_nordic/nrfs/dvfs/
Dld_dvfs_handler.h17 * @brief Function to request LD frequency change.
20 * @return EBUSY Frequency change request pending.

12345678910>>...40