Home
last modified time | relevance | path

Searched refs:line (Results 426 – 450 of 819) sorted by relevance

1...<<11121314151617181920>>...33

/Zephyr-latest/boards/m5stack/m5stack_atoms3_lite/
Dm5stack_atoms3_lite_procpu.dts80 line-idle-low;
/Zephyr-latest/doc/contribute/
Dguidelines.rst136 The "sign-off" in the DCO is a "Signed-off-by:" line in each commit's log
137 message. The Signed-off-by: line must be in the following format::
149 You can automatically add the Signed-off-by: line to your commit body using
157 your Signed-off-by: line without removing the existing one.
159 - If you forget to add the Signed-off-by: line, you can add it to your previous
238 the west command-line tool.
414 This line is called the commit's *title*. Titles must be:
416 * one line
418 * followed by a completely blank line
463 Each line in your commit message should usually be 75 characters or
[all …]
/Zephyr-latest/samples/net/sockets/http_server/
DREADME.rst132 line = input("> ")
133 if line == "quit":
135 ws.send(line)
/Zephyr-latest/boards/arduino/due/doc/
Dindex.rst142 There are GUI and command line versions of the bossa tool. The following
143 section provides the steps to build the command line version. Please
162 #. Build the command line version of the bossa tool.
/Zephyr-latest/arch/
DKconfig192 line option for gen_isr_tables.py.
503 indexed by IRQ line. In the latter case, the vector table must be
1048 bool "Detect d-cache line size at runtime"
1052 finding the d-cache line size at the expense of taking more memory and
1055 If the CPU's d-cache line size is known in advance, disable this option and
1057 using the 'd-cache-line-size' property.
1060 int "d-cache line size"
1064 Size in bytes of a CPU d-cache line. If this is set to 0 the value is
1065 obtained from the 'd-cache-line-size' DT property instead if present.
1071 bool "Detect i-cache line size at runtime"
[all …]
/Zephyr-latest/drivers/interrupt_controller/
DKconfig.multilevel14 all interrupts routed to it into one IRQ line in the first level
16 aggregator combines its input interrupts into one IRQ line at the
/Zephyr-latest/drivers/gpio/
Dgpio_gd32.c64 static void gpio_gd32_isr(uint8_t line, void *arg) in gpio_gd32_isr() argument
69 gpio_fire_callbacks(&data->callbacks, dev, BIT(line)); in gpio_gd32_isr()
/Zephyr-latest/tests/lib/mpsc_pbuf/src/
Dconcurrent.c115 static void test_fail(int line, struct test_packet *packet) in test_fail() argument
118 test_failed_line = line; in test_fail()
/Zephyr-latest/boards/gaisler/generic_leon3/doc/
Dindex.rst98 icache: 1 * 4 KiB, 16 bytes/line (4 KiB total)
99 dcache: 1 * 4 KiB, 16 bytes/line (4 KiB total)
/Zephyr-latest/doc/_doxygen/
Ddoxygen-awesome.css74 --content-line-height: 27px;
77 --table-line-height: 24px;
323 line-height: initial;
709 line-height: var(--content-line-height);
807 line-height: var(--tree-item-height);
911 line-height: initial;
958 line-height: var(--content-line-height);
1063 line-height: var(--table-line-height);
1116 line-height: var(--toc-font-size);
1282 …, pre.fragment, div.fragment, div.fragment .line, div.fragment span, div.fragment .line a, div.fra…
[all …]
/Zephyr-latest/doc/connectivity/networking/api/
Dppp.rst17 cannot be transmitted over a modem line on their own, without some data link
/Zephyr-latest/cmake/linker_script/common/
Ddebug-sections.cmake19 zephyr_linker_section(NAME .line ADDRESS 0)
/Zephyr-latest/samples/bluetooth/hci_spi/
DREADME.rst23 :dtcompatible:`zephyr,bt-hci-spi-slave`. This node sets an interrupt line to
/Zephyr-latest/dts/arm/infineon/cat3/xmc/
Dxmc4xxx.dtsi236 interrupts = <0 1>; // shared interrupt line with rtc
243 interrupts = <0 1>; // shared interrupt line with wdt0
/Zephyr-latest/subsys/bluetooth/host/
Dconn_internal.h540 const char *func, int line);
560 const char *func, int line);
/Zephyr-latest/drivers/spi/
DKconfig.nrfx112 for SPI slave to wake up after the WAKE line is asserted. Used only
113 by instances that have the WAKE line configured (see the wake-gpios
/Zephyr-latest/doc/build/dts/
Dtroubleshooting.rst37 This usually happens on a line like this:
147 line:
179 looking for a line similar to this one in the :file:`CMakeLists.txt` file in
181 :zephyr_file:`drivers/i2c/CMakeLists.txt` has a line that looks like this:
193 adding a line like this to your application's :file:`prj.conf` file and then
314 identifier and property. For example, if you get a build error on a line that
/Zephyr-latest/soc/nordic/nrf54l/
DKconfig1 # Nordic Semiconductor nRF54 MCU line
/Zephyr-latest/
DCONTRIBUTING.rst22 contributions, and documented with a ``Signed-off-by`` line in commits.
/Zephyr-latest/lib/net_buf/
DKconfig58 to a certain byte boundary, or dealing with cache line restrictions.
/Zephyr-latest/boards/espressif/esp32c3_rust/
Desp32c3_rust.dts62 line-idle-low;
/Zephyr-latest/tests/arch/arm/arm_no_multithreading/
DREADME.txt52 Available IRQ line: 25
/Zephyr-latest/scripts/west_commands/completion/
Dwest-completion.fish15 # exclude the caller if one of the arguments is present in the command line
17 # return 1 if one of the arguments is present in the command line
36 …ents to count, if not specified will count all arguments after 'west <command>' on the command line
38 # return 1 if the command line contain more than $argv[1] element from $argv[n...]
72 # check if a given token is the last one in the command line
241 for line in $config
242 if string match -rq '^\s*\[manifest\]\s*$' $line
245 else if string match -rq '^\[.*\]$' $line
251 set -l tmp_manifest_path (string match -r '^path\s*=\s*(\S*)\s*$' $line)[2]
257 set -l tmp_manifest_file (string match -r '^file\s*=\s*(\S*)\s*$' $line)[2]
/Zephyr-latest/doc/develop/test/
Dztest.rst239 In the command line above ``tests/foo/bar`` is the path to your test application and
485 When an assertion fails, it will print the current file, line and function,
488 file and line numbers, reducing the binary size of the test.
505 test at the end of its execution. When an expectation fails, it will print the current file, line,
508 file and line numbers, reducing the binary size of the test.
532 When an assumption fails, it will print the current file, line, and function,
535 file and line numbers, reducing the binary size of the test.
582 Add the line ``zephyr_include_directories(my_folder)`` to
617 For tests built for native simulator, use command line arguments to list
/Zephyr-latest/boards/native/doc/
Dbsim_boards_design.rst179 program, command line argument handling, and the overall time scheduling of
306 From the command line the user can query what tests are present, and select
311 and Zephyr OS, a hook to process possible command line arguments, and, a hook
337 for each MCU separatedly with the command line options.
339 Command line argument parsing
342 bsim boards need to handle command line arguments. There are several sets of
349 - The HW models command line arguments: The HW models will expose which
355 Command line argument parsing is handled by using the bs_cmd_line component

1...<<11121314151617181920>>...33