Searched full:files (Results 1 – 25 of 633) sorted by relevance
12345678910>>...26
| /Zephyr-Core-3.4.0/scripts/ci/ |
| D | tags.yaml | 1 # This file contains information on what files are associated with which
9 # files:
10 # List of paths and/or glob patterns giving the files in the tag,
13 # If a path or glob pattern ends in a '/', it matches all files within
19 # files-regex:
24 # Can be combined with a 'files' key.
26 # Note: Prefer plain 'files' patterns where possible. get_maintainer.py
30 # files-exclude:
31 # Like 'files', but any matching files will be excluded from the tag.
33 # files-regex-exclude:
[all …]
|
| D | test_plan.py | 5 # A script to generate twister options based on modified files.
168 # Limit search to $ZEPHYR_BASE since this is where the changed files are
234 # tag._match_fn(path) tests if the path matches files and/or
235 # files-regex
236 tag._match_fn = _get_match_fn(x.get("files"), x.get("files-regex"))
238 # Like tag._match_fn(path), but for files-exclude and
239 # files-regex-exclude
241 _get_match_fn(x.get("files-exclude"), x.get("files-regex-exclude"))
267 files = list(filter(lambda x: x, self.modified_files))
273 found.update(fnmatch.filter(files, pattern))
[all …]
|
| /Zephyr-Core-3.4.0/ |
| D | MAINTAINERS.yml | 35 # files:
36 # List of paths and/or glob patterns giving the files in the area,
39 # If a path or glob pattern ends in a '/', it matches all files within
45 # files-regex:
50 # Can be combined with a 'files' key.
52 # Note: Prefer plain 'files' patterns where possible. get_maintainer.py
56 # files-exclude:
57 # Like 'files', but any matching files will be excluded from the area.
59 # files-regex-exclude:
60 # Like 'files-regex', but any matching files will be excluded from the
[all …]
|
| D | .gitattributes | 1 # used to remove files from deployment using `git archive`
2 # git files
7 # Tell git to not diff certain files
10 # Tell linguist that generated test pattern files should not be included in the
|
| /Zephyr-Core-3.4.0/tests/application_development/code_relocation/ |
| D | CMakeLists.txt | 18 zephyr_code_relocate(FILES src/test_file1.c ${SRAM2_PHDR} LOCATION SRAM2)
20 zephyr_code_relocate(FILES src/test_file2.c ${RAM_PHDR} LOCATION RAM)
29 # Test support for a simple generator expression to relocate two files
33 zephyr_code_relocate(FILES ${genex_expr} LOCATION SRAM2)
35 zephyr_code_relocate(FILES src/test_file3.c LOCATION SRAM2_LITERAL)
36 zephyr_code_relocate(FILES src/test_file3.c LOCATION SRAM2_TEXT)
37 zephyr_code_relocate(FILES src/test_file3.c LOCATION RAM_DATA)
38 zephyr_code_relocate(FILES src/test_file3.c LOCATION SRAM2_BSS)
41 zephyr_code_relocate(FILES ${ZEPHYR_BASE}/kernel/sem.c ${RAM_PHDR} LOCATION RAM)
44 zephyr_code_relocate(FILES ${ZEPHYR_BASE}/lib/libc/minimal/source/string/string.c
|
| /Zephyr-Core-3.4.0/doc/build/dts/ |
| D | intro-input-output.rst | 1 .. _devicetree-in-out-files:
3 Input and output files
6 This section describes the input and output files shown in the figure in
12 Devicetree input (green) and output (yellow) files
14 .. _dt-input-files:
16 Input files
19 There are four types of devicetree input files:
26 The devicetree files inside the :file:`zephyr` directory look like this::
37 :file:`BOARD.dts` includes one or more ``.dtsi`` files. These ``.dtsi`` files
39 ``.dtsi`` files. They can also describe other common hardware features shared by
[all …]
|
| /Zephyr-Core-3.4.0/doc/kernel/ |
| D | code-relocation.rst | 9 required files and place them in the required memory region. The memory region
15 of ``__attribute__((section("name")))`` for a bunch of files together.
31 ``code_relocation.c`` files. The ``linker_relocate.ld`` file creates
33 selected files.
55 all the files that need relocation.
57 ``zephyr_code_relocate(FILES src/*.c LOCATION SRAM2)``
59 Where the first argument is the file/files and the second
79 zephyr_code_relocate(FILES src/file1.c LOCATION SRAM2)
80 zephyr_code_relocate(FILES src/file2.c LOCATION SRAM)
88 zephyr_code_relocate(FILES src/file1.c LOCATION SRAM2_DATA)
[all …]
|
| /Zephyr-Core-3.4.0/.github/workflows/ |
| D | bsim-tests.yaml | 78 - name: Check common triggering files
79 uses: tj-actions/changed-files@v35
80 id: check-common-files
82 files: |
91 - name: Check if Bluethooth files changed
92 uses: tj-actions/changed-files@v35
93 id: check-bluetooth-files
95 files: |
100 - name: Check if Networking files changed
101 uses: tj-actions/changed-files@v35
[all …]
|
| /Zephyr-Core-3.4.0/samples/boards/intel_adsp/code_relocation/ |
| D | CMakeLists.txt | 10 zephyr_code_relocate(FILES src/reloc.c LOCATION SRAM2_LITERAL)
11 zephyr_code_relocate(FILES src/reloc.c LOCATION SRAM2_TEXT)
12 zephyr_code_relocate(FILES src/reloc.c LOCATION SRAM3_DATA)
13 zephyr_code_relocate(FILES src/reloc.c LOCATION SRAM3_RODATA)
14 zephyr_code_relocate(FILES src/reloc.c LOCATION SRAM4_BSS)
|
| /Zephyr-Core-3.4.0/subsys/logging/backends/ |
| D | Kconfig.fs | 28 bool "Old log files overwrite"
31 When enabled backend overwrites oldest log files.
38 User defined name of log files saved in the file system.
45 Directory to which log files will be written.
55 int "Max number of files containing logs"
58 Limit of number of files with logs. It is also limited by
|
| /Zephyr-Core-3.4.0/scripts/ |
| D | get_maintainer.py | 7 Lists maintainers for files or commits. Similar in function to
92 help="List files in areas")
97 help="Name of area to list files in. If not specified, all "
98 "non-orphaned files are listed (all files that do not appear in "
115 help="List orphaned files (files that do not appear in any area)")
120 help="Limit to files under PATH")
196 # area._match_fn(path) tests if the path matches files and/or
197 # files-regex
199 _get_match_fn(area_dict.get("files"),
200 area_dict.get("files-regex"))
[all …]
|
| /Zephyr-Core-3.4.0/subsys/usb/usb_c/ |
| D | CMakeLists.txt | 5 # Common USB-C Stack files
15 # Sink USB-C Stack files
22 # Source USB-C Stack files
|
| /Zephyr-Core-3.4.0/submanifests/ |
| D | README.txt | 1 This directory can contain additional west manifest files. Any files
10 …roject.org/latest/guides/west/manifest.html#example-2-2-downstream-with-directory-of-manifest-files
|
| /Zephyr-Core-3.4.0/samples/subsys/fs/fat_fs/ |
| D | Kconfig | 10 bool "When no files are found on mounted partition create some"
13 In case when no files could be listed, because there are none,
18 easily add files with use of other device.
|
| /Zephyr-Core-3.4.0/doc/develop/west/ |
| D | zephyr-cmds.rst | 62 application CMakeLists.txt files that are outside of your workspace will be
77 from source files to the corresponding generated build files.
78 ``SPDX-License-Identifier`` comments in source files are scanned and filled
107 - :file:`app.spdx`: BOM for the application source files used for the build
108 - :file:`zephyr.spdx`: BOM for the specific Zephyr source code files used for the build
109 - :file:`build.spdx`: BOM for the built output files
117 source files that are compiled to generate the built library files.
130 files (e.g. ``.c``, ``.S``) in the bills-of-materials, also attempt to
131 determine the specific header files that are included for each ``.c`` file.
138 document, :file:`sdk.spdx`, which lists header files included from the SDK.
|
| /Zephyr-Core-3.4.0/doc/build/snippets/ |
| D | writing.rst | 10 Snippets are defined using YAML files named :file:`snippet.yml`.
70 :file:`snippet.yml` files underneath a subdirectory named :file:`snippets/`,
74 system will look for :file:`snippet.yml` files underneath the following
80 The :file:`snippet.yml` files can be nested anywhere underneath these
94 And then any :file:`snippet.yml` files in ``baz/snippets`` will
124 This principle applies to both Kconfig fragments (``.conf`` files) and
125 devicetree overlays (``.overlay`` files).
143 .. _snippets-conf-files:
145 ``.conf`` files
166 application with both :file:`prj.conf` and :file:`boards/foo.conf` files will
[all …]
|
| /Zephyr-Core-3.4.0/samples/application_development/code_relocation_nocopy/ |
| D | CMakeLists.txt | 13 zephyr_code_relocate(FILES src/ext_code.c LOCATION EXTFLASH_TEXT NOCOPY)
16 zephyr_code_relocate(FILES src/ext_code.c LOCATION RAM_DATA)
19 zephyr_code_relocate(FILES src/sram_code.c LOCATION RAM)
|
| /Zephyr-Core-3.4.0/scripts/west_commands/zspdx/ |
| D | scanner.py | 21 # Package's license, based on the licenses of its Files?
24 # when assembling a Package's Files' data, should we auto-conclude
32 # should we calculate SHA256 hashes for each Package's Files?
36 # should we calculate MD5 hashes for each Package's Files?
101 Calculate the SPDX Package Verification Code for all files in the package.
108 for f in pkg.files.values():
140 for f in pkg.files.values():
175 Scan for licenses and calculate hashes for all Files and Packages
183 log.inf(f"scanning files in package {pkg.cfg.name} in document {doc.cfg.name}")
186 for f in pkg.files.values():
|
| /Zephyr-Core-3.4.0/samples/subsys/usb/mass/ |
| D | sample.yaml | 54 - "End of files"
79 - "End of files"
105 - "End of files"
126 - "End of files"
151 - "End of files"
|
| /Zephyr-Core-3.4.0/doc/build/kconfig/ |
| D | setting.rst | 15 Before making changes to Kconfig files, it's a good idea to also go through
27 set in configuration files.
61 Setting symbols in configuration files
64 Visible symbols can be configured by setting them in configuration files. The
69 Assignments in configuration files use this syntax:
97 This style is accepted for historical reasons: Kconfig configuration files
114 Assignments in configuration files are only respected if the dependencies for
173 All configuration files will be taken from the application's configuration
174 directory except for files with an absolute path that are given with the
192 ``BOARD`` and application configuration files), it will be used in preference
[all …]
|
| D | extensions.rst | 33 If the pattern ``foo/bar/*/Kconfig`` matches the files
42 If no files match the pattern, an error is generated.
47 For cases where it's okay for a pattern to match no files (or for a plain
56 - An ``rsource`` statement is available for including files specified with a
69 This will include the two files :file:`foo/qaz/Kconfig1` and
|
| /Zephyr-Core-3.4.0/soc/arm/nxp_imx/rt/ |
| D | CMakeLists.txt | 34 zephyr_code_relocate(FILES flexspi_rt10xx.c LOCATION ITCM_TEXT)
39 zephyr_code_relocate(FILES power_rt10xx.c LOCATION ITCM_TEXT)
42 zephyr_code_relocate(FILES lpm_rt1064.c LOCATION ITCM_TEXT)
|
| /Zephyr-Core-3.4.0/doc/develop/ |
| D | modules.rst | 103 * Modules should expose all provided header files with an include pathname
299 All source files in a module's codebase shall include a license header,
301 files that do not include license headers.
303 Main license files shall be added in the module's codebase by Zephyr
305 and they contain a permissive OSI-compliant license. Main license files
307 SPDX license identifier. If multiple main license files are present it
311 Individual license headers in module source files supersede the main license.
319 headers and main license files. This not a hard requirement; should
322 multiple main license files), this practice may be accepted by and
331 * import the main license files, if they exist in the external project, and
[all …]
|
| /Zephyr-Core-3.4.0/cmake/modules/ |
| D | dts.cmake | 18 # - To Zephyr and application source code files, as a C macro API
28 # - To CMake files, after this module has finished running, using
31 # - To Kconfig files, both using some Kconfig symbols we generate
39 # files in scripts/dts to make all this work. We also optionally will
63 # - the build system will be regenerated if any devicetree files
66 # will be ready for use in other CMake list files that run
70 # - BINARY_DIR_INCLUDE_GENERATED: where to put generated include files
71 # - KCONFIG_BINARY_DIR: where to put generated Kconfig files
78 # - DTC_OVERLAY_FILE: list of devicetree overlay files which will be
80 # - EXTRA_DTC_OVERLAY_FILE: list of extra devicetree overlay files.
[all …]
|
| D | kernel.cmake | 21 # source files that must be included when building Zephyr
44 BRIEF_DOCS "Source files that are generated after Zephyr has been linked once."
46 Source files that are generated after Zephyr has been linked once.\
52 BRIEF_DOCS "Object files that are generated after symbol addresses are fixed."
54 Object files that are generated after symbol addresses are fixed.\
60 BRIEF_DOCS "Source files that are generated after symbol addresses are fixed."
62 Source files that are generated after symbol addresses are fixed.\
84 # paths can be changed, e.g. to flash signed versions of these files
117 # Dummy add to generate files.
121 # all targets exports their compile commands to fetch object files.
[all …]
|
12345678910>>...26
