Home
last modified time | relevance | path

Searched full:what (Results 1 – 25 of 659) sorted by relevance

12345678910>>...27

/Zephyr-latest/drivers/disk/nvme/
DKconfig22 Do not touch this unless you know what you are doing.
30 Do not touch this unless you know what you are doing.
38 Do not touch this unless you know what you are doing.
45 Do not touch this unless you know what you are doing.
53 Do not touch this unless you know what you are doing.
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D001_bug_report.md23 A clear and concise description of what the bug is.
27 - What target platform are you using?
28 - What have you tried to diagnose or workaround this issue?
45 A clear and concise description of what you expected to happen.
50 What impact does this issue have on your progress (e.g., annoyance, showstopper)
D003_rfc-proposal.md19 Why do we want this change and what problem are we trying to address?
24 A brief summary of the proposed change - the 10,000 ft view on what it will
31 reading this section each engineer should have a rather clear picture of what
41 By reading this section, each team member should be able to know what exactly
D007_ext-source.md17 Brief description of what this software does
43 What is its primary functionality (e.g., SQLLite is a lightweight
46 What problem are you trying to solve? (e.g., a state store is
63 What other components does this package depend on?
D002_enhancement.md12 A clear and concise description of what the problem is.
17 A clear and concise description of what you want to happen.
D004_feature_request.md12 A clear and concise description of what the problem is.
17 A clear and concise description of what you want to happen.
D008_bin-blobs.md25 Brief description of what the blob(s) do. It is especially important to describe
36 What other components do the blob(s) depend on, if any?
/Zephyr-latest/drivers/ieee802154/
DKconfig.cc120025 you know what you are doing. Beware cc1200 requires gpio and spi to
72 This value should follow what has been set in the RF settings via
73 SmartRF tool. Do not touch this unless you know what you are doing.
111 more information. Do not touch this unless you know what you are doing.
118 more information. Do not touch this unless you know what you are doing.
120 # Do no touch below settings unless you know what you are doing
DKconfig.cc252026 you know what you are doing. Beware cc2520 requires gpio and spi to
83 you know what you are doing. It should be initialized after CC2520
/Zephyr-latest/drivers/wifi/winc1500/
DKconfig.winc150032 WINC1500 HAL callbacks. Do not touch it unless you know what you are
40 callbacks. Do not touch it unless you know what you are doing.
55 Do not modify it unless you know what you are doing.
/Zephyr-latest/tests/kernel/pipe/deprecated/pipe_api/src/
Dtest_pipe_fail.c119 * @details See what will happen if an uninitialized
137 * @details See what will happen if an uninitialized
157 * @details See what will happen if the parameter
181 * @details See what will happen if the parameter
205 * @details See what will happen if a null pointer
225 * @details See what will happen if the parameter
249 * @details See what will happen if the parameter
273 * @details See what will happen if a null pointer
289 * @details See what will happen if a null pointer
/Zephyr-latest/subsys/net/ip/
DKconfig.stack16 be bigger depending on what features are enabled.
25 be bigger depending on what features are enabled.
/Zephyr-latest/tests/kernel/queue/src/
Dtest_queue_fail.c131 * NULL, what will happen.
147 * NULL, what will happen.
166 * NULL, what will happen.
185 * NULL, what will happen.
201 * NULL, what will happen.
217 * NULL, what will happen.
233 * NULL, what will happen.
249 * NULL, what will happen.
/Zephyr-latest/include/zephyr/dt-bindings/pinctrl/
Dpinctrl-zynq.h14 * corresponds to what is written to the IO_Type field in the MIO_PIN_xx SLCR register.
28 * corresponds to what is written to the Speed field in the MIO_PIN_xx SLCR register.
/Zephyr-latest/doc/connectivity/networking/
Dnetwork_tracing.rst22 API support are enabled. The system will start to collect what BSD socket
23 API calls are made and what parameters the API calls are using and returning.
/Zephyr-latest/soc/nordic/nrf92/
DKconfig.soc14 # and user-configurable Kconfigs, since that's what visible to users.
17 # the engineering version, because that's what the MDK/nrfx expects
/Zephyr-latest/dts/bindings/sensor/
Despressif,esp32-pcnt.yaml118 Define what to do on the positive edge of pulse input.
131 Define what to do on the negative edge of pulse input.
144 Define what to do when the control input is high.
157 Define what to do when the control input is low.
/Zephyr-latest/doc/kernel/services/threads/
Dnothread.rst15 been limited, there are conditions on what can be expected to work in
18 What Can be Expected to Work
47 What Cannot be Expected to Work
/Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32_common_core/boards/
Dclear_msi.overlay8 * Warning: This overlay clears the msi clock back to a state equivalent to what could
/Zephyr-latest/samples/net/sockets/http_client/src/
Dca_certificate.h11 /* This is the same cert as what is found in net-tools/https-cert.pem file
/Zephyr-latest/samples/net/sockets/websocket_client/src/
Dca_certificate.h11 /* This is the same cert as what is found in net-tools/https-cert.pem file
/Zephyr-latest/drivers/ethernet/
DKconfig.smsc911x16 Tells what Qemu network model to use. This value is given as
DKconfig.stellaris18 Tells what Qemu network model to use. This value is given as
/Zephyr-latest/subsys/testsuite/ztest/include/zephyr/
Dztest_error_hook.h35 * Usage: Define your own hook function in your test case code, and do what
65 * Usage: Define your own hook function in your test case code, and do what
/Zephyr-latest/include/zephyr/tracing/
Dtracing_macros.h231 * match the name of the function but should rather match what the user called in case of
244 * match the name of the function but should rather match what the user called in case of
256 * match the name of the function but should rather match what the user called in case of
270 * match the name of the function but should rather match what the user called in case of
296 * match the name of the function but should rather match what the user called in case of
315 * match the name of the function but should rather match what the user called in case of
331 * match the name of the function but should rather match what the user called in case of
350 * match the name of the function but should rather match what the user called in case of

12345678910>>...27