Home
last modified time | relevance | path

Searched refs:patterns (Results 1 – 25 of 28) sorted by relevance

12

/Zephyr-latest/doc/_scripts/
Dgen_boards_catalog.py72 def guess_file_from_patterns(directory, patterns, name, extensions): argument
73 for pattern in patterns:
83 patterns = [
89 board_or_shield.dir, patterns, board_or_shield.name, img_exts
96 patterns = [
103 board_or_shield.dir, patterns, board_or_shield.name, ["rst"]
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/hal/nrf5/radio/
Dradio_df.h47 void radio_df_ant_switch_pattern_set(const uint8_t *patterns, uint8_t len);
Dradio_df.c93 void radio_df_ant_switch_pattern_set(const uint8_t *patterns, uint8_t len) in radio_df_ant_switch_pattern_set() argument
111 NRF_RADIO->SWITCHPATTERN = patterns[idx]; in radio_df_ant_switch_pattern_set()
121 NRF_RADIO->SWITCHPATTERN = patterns[GUARD_REF_ANTENNA_PATTERN_IDX]; in radio_df_ant_switch_pattern_set()
/Zephyr-latest/samples/application_development/
Dapplication_development.rst5 These samples illustrate some useful application development patterns and techniques.
/Zephyr-latest/drivers/entropy/
DKconfig.cc13xx_cc26xx35 int "Threshold for detected repeated patterns"
39 The number of samples detected with repeating patterns before an alarm
/Zephyr-latest/doc/build/kconfig/
Dextensions.rst60 - The ``source`` statement supports glob patterns and includes each matching
80 The wildcard patterns accepted are the same as for the Python `glob
111 ``rsource`` also supports glob patterns.
/Zephyr-latest/scripts/ci/
Dtwister_ignore.txt3 # The patterns listed in this file will be compared with the list of files
/Zephyr-latest/scripts/tests/twister/
Dtest_harness.py218 def test_harness_parse_record(lines, patterns, expected_records, as_json, merge): argument
220 harness.record = {"regex": patterns}
221 harness.record_patterns = [re.compile(p) for p in patterns]
441 assert len(console.patterns) == num_patterns
442 assert [pattern.pattern for pattern in console.patterns] == [
495 console.patterns = [re.compile("pattern1"), re.compile("pattern2")]
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dharness.py281 self.patterns = []
283 self.patterns.append(re.compile(r))
284 self.patterns_expected = len(self.patterns)
303 if (self.next_pattern < len(self.patterns) and
304 self.patterns[self.next_pattern].search(line)):
309 if self.next_pattern >= len(self.patterns):
312 for i, pattern in enumerate(self.patterns):
/Zephyr-latest/doc/kernel/services/data_passing/
Dpipes.rst45 Pipes are well-suited for scenarios like producer-consumer patterns or
209 - Implementing producer-consumer patterns.
/Zephyr-latest/samples/bluetooth/direction_finding_connectionless_tx/
DREADME.rst84 Finding locator when the AoA mode is enabled, also update the antenna patterns
/Zephyr-latest/include/zephyr/bluetooth/
Dhci_vs.h356 struct bt_hci_mesh_pattern patterns[0]; member
/Zephyr-latest/doc/services/rtio/
Dindex.rst16 and common usage patterns with peripheral devices.
/Zephyr-latest/cmake/linker/armlink/
Dscatter_script.cmake376 # ToDo: add patterns here.
/Zephyr-latest/doc/releases/
Drelease-notes-1.5.rst268 * ``ZEP-517`` - build on windows failed "zephyr/Makefile:869: \*\*\* multiple target patterns"
Drelease-notes-1.6.rst282 * ``ZEP-517`` - build on windows failed "zephyr/Makefile:869: \*\*\* multiple target patterns"
/Zephyr-latest/doc/develop/west/
Dbuilt-in.rst251 - ``west grep``: search for patterns in local project repositories
/Zephyr-latest/subsys/bluetooth/controller/hci/
Dhci.c178 uint8_t patterns[CONFIG_BT_CTLR_MESH_SF_PATTERNS] member
5586 if (!cmd->patterns[i].pattern_len ||
5587 cmd->patterns[i].pattern_len >
5592 f->lengths[i] = cmd->patterns[i].pattern_len;
5593 memcpy(f->patterns[i], cmd->patterns[i].pattern, f->lengths[i]);
6554 !memcmp(data, f->patterns[i], f->lengths[i])) {
/Zephyr-latest/doc/build/dts/
Dintro-syntax-structure.rst259 Here are some common patterns:
/Zephyr-latest/doc/develop/tools/
Dcoccinelle.rst13 tree-wide patches and detection of problematic programming patterns.
/Zephyr-latest/
DKconfig.zephyr20 # $ARCH and $KCONFIG_BOARD_DIR will be glob patterns when building documentation.
882 match more than one section name. Multiple such patterns can be given
/Zephyr-latest/arch/xtensa/core/
DREADME_MMU.txt251 This may or may not be desirable depending on access patterns. It
/Zephyr-latest/doc/
Dzephyr.doxyfile.in1006 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
1013 # Note the list of default checked file patterns might differ from the list of
1016 # If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cxxm,
1052 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
1128 # patterns match the file name, INPUT_FILTER is applied.
2452 # patterns (like *.h and *.hpp) to filter out the header-files in the
2453 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.ll_sw_split194 int "Number of Mesh scan filter patterns"
199 Set the number of unique Mesh Scan Filter patterns available per
/Zephyr-latest/scripts/
Dspelling.txt1154 pattrns||patterns

12