Home
last modified time | relevance | path

Searched full:consider (Results 1 – 25 of 174) sorted by relevance

1234567

/Zephyr-latest/scripts/ci/
Dpylintrc47 # consider-using-get
69 consider-using-enumerate,
70 consider-iterating-dictionary,
177 consider-merging-isinstance,
183 consider-swap-variables,
184 consider-using-join,
185 consider-using-in,
187 consider-using-dict-comprehension,
188 consider-using-set-comprehension,
/Zephyr-latest/samples/application_development/
Dapplication_development.rst7 For application development you should also consider looking at
/Zephyr-latest/tests/bsim/bluetooth/ll/conn/src/
Dtest_connect2.c71 * (and finish) we consider it failed in test_con2_tick()
83 * (and finish) we consider it failed in test_con2_repeat_tick()
109 if (repeat_connect >= 20) { /* We consider it passed */ in connected()
225 if (notify_count++ == 1) { /* We consider it passed */ in test_con2_main()
/Zephyr-latest/tests/bsim/bluetooth/host/att/retry_on_sec_err/
Dtest_utils.c18 bs_trace_error("Test did not pass before simulation ended. Consider increasing " in test_tick()
/Zephyr-latest/subsys/testsuite/arch/unit_testing/
DKconfig6 # defined CONFIG_X86 manually. To consider, is ARCH_POSIX a better choice?
/Zephyr-latest/soc/nordic/nrf53/
DCMakeLists.txt15 Consider enabling the system clock to apply the workaround.
/Zephyr-latest/soc/raspberrypi/rpi_pico/rp2350/
DKconfig29 RP23XX devices to consider this a valid image in flash.
/Zephyr-latest/include/zephyr/net/
Dconn_mgr_monitor.h42 * Ignoring an iface forces conn_mgr to consider it unready/disconnected.
55 * conn_mgr will no longer be forced to consider the iface unreadly/disconnected.
/Zephyr-latest/doc/build/dts/
Ddt-vs-kconfig.rst22 For example, consider a board containing a SoC with 2 UART, or serial port,
38 As another example, consider a device with a 2.4GHz, multi-protocol radio
/Zephyr-latest/dts/bindings/gpio/
Dnordic,nrf-gpio-forwarder.yaml16 combined with a nRF21540 Front-End module. Consider the following node
30 the nRF5340 application core to the network core. Consider the following
/Zephyr-latest/scripts/west_commands/
DREADME.txt5 Before adding more here, consider whether you might want to put new
/Zephyr-latest/dts/bindings/sensor/
Dsensirion,shtcx.yaml8 such that a generic driver can consider chip specific behaviour.
/Zephyr-latest/tests/bsim/bluetooth/host/att/read_fill_buf/
Dbs_main.c26 bs_trace_error("Test did not pass before simulation ended. Consider increasing " in test_tick()
/Zephyr-latest/samples/modules/tflite-micro/magic_wand/src/
Dconstants.hpp33 * more robust results though, so consider retraining if you are seeing poor
/Zephyr-latest/dts/bindings/input/
Dadc-keys.yaml65 Array of millivolt values to consider a key pressed.
/Zephyr-latest/doc/develop/optimizations/
Dfootprint.rst57 support to gain some memory and improve performance. Consider the consequences
/Zephyr-latest/tests/bsim/bluetooth/audio_samples/bap_broadcast_sink/src/
Dbroadcast_sink_test.c43 * we consider the test failed in test_broadcast_sink_sample_tick()
/Zephyr-latest/tests/bsim/bluetooth/audio_samples/bap_unicast_client/src/
Dunicast_client_sample_test.c43 * we consider the test failed in test_unicast_client_sample_tick()
/Zephyr-latest/tests/bsim/bluetooth/samples/central_hr_peripheral_hr/src/
Dsample_test.c43 * we consider the test failed in test_sample_tick()
/Zephyr-latest/doc/develop/test/twister/
Dtwister_blackbox.rst80 consider whether they will be used in just one test file, or in many.
89 - Consider using class fields instead - look at TESTDATAs for an example.
/Zephyr-latest/drivers/sensor/bosch/bme280/
Dbme280_async.c80 LOG_ERR("RTIO work item allocation failed. Consider to increase " in bme280_submit()
/Zephyr-latest/tests/bsim/bluetooth/audio_samples/cap/initiator/src/
Dcap_initiator_sample_test.c44 * we consider the test failed in test_cap_initiator_sample_tick()
/Zephyr-latest/tests/bsim/net/sockets/echo_test/src/
Decho_test.c50 * we consider the test failed in test_echo_client_tick()
/Zephyr-latest/tests/kernel/timer/timer_behavior/src/
Dtick_timer_train.c162 TC_PRINT("!! Consider making CONFIG_SYS_CLOCK_TICKS_PER_SEC smaller.\n"); in ZTEST()
170 TC_PRINT("!! Consider making CONFIG_SYS_CLOCK_TICKS_PER_SEC smaller.\n"); in ZTEST()
/Zephyr-latest/doc/contribute/
Dproposals_and_rfcs.rst15 Contributors and project stakeholders should consider using this process if

1234567