| /Zephyr-Core-2.7.6/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.
216 # tag._match_fn(path) tests if the path matches files and/or
217 # files-regex
218 tag._match_fn = _get_match_fn(x.get("files"), x.get("files-regex"))
220 # Like tag._match_fn(path), but for files-exclude and
221 # files-regex-exclude
223 _get_match_fn(x.get("files-exclude"), x.get("files-regex-exclude"))
249 files = list(filter(lambda x: x, self.modified_files))
253 found.update(fnmatch.filter(files, pattern))
256 logging.debug(files)
[all …]
|
| /Zephyr-Core-2.7.6/ |
| D | MAINTAINERS.yml | 36 # files:
37 # List of paths and/or glob patterns giving the files in the area,
40 # If a path or glob pattern ends in a '/', it matches all files within
46 # files-regex:
51 # Can be combined with a 'files' key.
53 # Note: Prefer plain 'files' patterns where possible. get_maintainer.py
57 # files-exclude:
58 # Like 'files', but any matching files will be excluded from the area.
60 # files-regex-exclude:
61 # 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 linguist that generated test pattern files should not be included in the
|
| /Zephyr-Core-2.7.6/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")
171 # area._match_fn(path) tests if the path matches files and/or
172 # files-regex
174 _get_match_fn(area_dict.get("files"),
175 area_dict.get("files-regex"))
[all …]
|
| D | parse_syscalls.py | 13 C or header files, and building up a database of system calls and their
66 for root, dirs, files in os.walk(base_path, topdown=True):
68 files.sort()
69 for fn in files:
117 for .h files. Can be specified multiple times:
134 # Only write json files if they don't exist or have changes since
|
| D | mergehex.py | 7 # This merges a set of input hex files into a single output hex file.
37 description="Merge hex files.",
43 help="What to do when files overlap (error, ignore, replace). "
|
| /Zephyr-Core-2.7.6/doc/guides/west/ |
| D | zephyr-cmds.rst | 45 application CMakeLists.txt files that are outside of your workspace will be
60 from source files to the corresponding generated build files.
61 ``SPDX-License-Identifier`` comments in source files are scanned and filled
90 - :file:`app.spdx`: BOM for the application source files used for the build
91 - :file:`zephyr.spdx`: BOM for the specific Zephyr source code files used for
93 - :file:`build.spdx`: BOM for the built output files
101 source files that are compiled to generate the built library files.
114 files (e.g. ``.c``, ``.S``) in the bills-of-materials, also attempt to
115 determine the specific header files that are included for each ``.c`` file.
122 document, :file:`sdk.spdx`, which lists header files included from the SDK.
|
| /Zephyr-Core-2.7.6/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():
|
| D | walker.py | 27 # should also analyze for included header files?
34 # build files, and corresponding source and SDK files, and gathers the
53 # queue of pending source Files to create, process and assign
78 log.inf("parsing CMake Codemodel files")
94 # walk through pending sources and create corresponding files
95 log.inf("walking through pending sources files")
115 log.dbg("getting codemodel from CMake API reply files")
269 # get its source files
315 pkg.files[bf.spdxID] = bf
326 # collect a target's source files, add to pending sources queue, and
[all …]
|
| D | writer.py | 63 # flag whether files analyzed / any files present
64 if len(pkg.files) > 0:
67 f.write(f"FilesAnalyzed: false\nPackageComment: Utility target; no files\n\n")
75 # write package files, if any
76 if len(pkg.files) > 0:
77 bfs = list(pkg.files.values())
|
| D | datatypes.py | 37 # Packages or Files; will likely be just DESCRIBES
41 # been seen while adding files to this Document; used to calculate
78 # base directory from which this Package's Files will calculate their
105 # list of licenses found in this Package's Files
108 # Files in this Package
110 self.files = {}
131 # Files and/or Packages/targets. It is eventually parsed into a corresponding
|
| /Zephyr-Core-2.7.6/doc/guides/ |
| 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.
59 Where the first argument is the file/files and the second
101 This example will place .text, .data, .bss from 3 files to various parts in the SRAM
|
| D | modules.rst | 263 All source files in a module's codebase shall include a license header,
265 files that do not include license headers.
267 Main license files shall be added in the module's codebase by Zephyr
269 and they contain a permissive OSI-compliant license. Main license files
271 SPDX license identifier. If multiple main license files are present it
275 Individual license headers in module source files supersede the main license.
283 headers and main license files. This not a hard requirement; should
286 multiple main license files), this practice may be accepted by and
295 * import the main license files, if they exist in the external project, and
381 contain :file:`CMakeLists.txt` and :file:`Kconfig` files describing how to
[all …]
|
| /Zephyr-Core-2.7.6/doc/application/ |
| D | index.rst | 28 The files in the **application directory** link Zephyr with the
29 application. This directory contains all application-specific files, such as
45 application files, and links the application directory with Zephyr's CMake
47 such as board-specific kernel configuration files, the ability to run and
50 * **Kernel configuration files**: An application typically provides a
58 * **Application source code files**: An application typically provides one
59 or more application-specific files, written in C or assembly language. These
60 files are usually located in a sub-directory called :file:`src`.
62 Once an application has been defined, you can use CMake to create project files
63 for building it from a directory where you want to host these files. This is
[all …]
|
| /Zephyr-Core-2.7.6/doc/guides/dts/ |
| D | intro.rst | 16 There are two types of devicetree input files: *devicetree sources* and
30 All Zephyr and application source code files can include and use
503 .. _devicetree-in-out-files:
505 Input and output files
508 This section describes the input and output files shown in the figure at the
514 Devicetree input (green) and output (yellow) files
516 .. _dt-input-files: argument
518 Input files argument
521 There are four types of devicetree input files:
528 The devicetree files inside the :file:`zephyr` directory look like this::
[all …]
|
| /Zephyr-Core-2.7.6/doc/guides/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
178 ``BOARD`` and application configuration files), it will be used in preference
194 Assignments in :file:`.config` files have no effect on invisible symbols,
225 ``default`` values in :file:`Kconfig.defconfig` files have priority over
[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-2.7.6/arch/arm/ |
| D | Kconfig | 42 the specified files and places it in the required memory region. The
43 files should be specified in the CMakeList.txt file with
52 the specified files and places it in SRAM. The files should be specified
|
| /Zephyr-Core-2.7.6/doc/guides/build/ |
| D | index.rst | 75 top-level directory, which in turn refers to :file:`CMakeLists.txt` files
77 set of Makefiles or Ninja files to drive the build process, but the CMake
82 include*) files are collected from the target's architecture, SoC, board,
85 :file:`*.dtsi` files are included by :file:`*.dts` files via the C
88 :file:`*.overlay` files, and to expand macros in :file:`*.dts`,
89 :file:`*.dtsi`, and :file:`*.overlay` files.
107 Files named :file:`dts_fixup.h` from the target’s architecture, SoC, board,
109 :file:`devicetree_fixups.h` file. :file:`dts_fixup.h` files are used to
117 :file:`Kconfig` files define available configuration options for for the
121 Kconfig configurations are stored in *configuration files*. The initial
[all …]
|
| /Zephyr-Core-2.7.6/doc/getting_started/ |
| D | toolchain_custom_cmake.rst | 11 toolchain's CMake configuration files.
13 Zephyr will then include the toolchain cmake files located in the
26 See the zephyr files :zephyr_file:`cmake/generic_toolchain.cmake` and
28 :file:`generic.cmake` and :file:`target.cmake` files should contain.
54 target.cmake files located under
|
| /Zephyr-Core-2.7.6/scripts/kconfig/ |
| D | kconfig.py | 4 # files passed as arguments, e.g. board *_defconfig and application prj.conf
5 # files.
8 # output, which just updates it. This is handled in the CMake files.
36 # configuration file together with updated Kconfig files
44 # Load configuration files
61 # when using an old configuration and updating Kconfig files.
66 # during evaluation. Wait till the end to write the actual output files, so
90 # Write the list of parsed Kconfig files to a file
213 # Writes a sorted list with the absolute paths of all parsed Kconfig files
215 # removed. This file is used by CMake to look for changed Kconfig files. It
[all …]
|
| D | diffconfig | 5 # diffconfig - a tool to compare .config files.
17 Diffconfig is a simple utility for comparing two .config files.
18 Using standard diff to compare .config files often includes extraneous and
20 changes in configuration values between the two files.
28 If no config files are specified, .config and .config.old are used.
|
| /Zephyr-Core-2.7.6/doc/guides/porting/ |
| D | board_porting.rst | 7 directory* with various files in it. Files in the board directory inherit
92 CPU core support files go in ``core`` subdirectories under :zephyr_file:`arch`,
104 Zephyr SoC support files are in architecture-specific subdirectories of
109 files to avoid duplication. If there is no support for your vendor yet, you can
150 The mandatory files are:
161 The optional files are:
164 - :file:`CMakeLists.txt`: if you need to add additional source files to
267 files. :zephyr_file:`nxp_k6x.dtsi<dts/arm/nxp/nxp_k6x.dtsi>` in turn includes
284 It is up to the board :file:`.dts` or application overlay files to enable these
286 files are also responsible for any board-specific configuration of the device,
[all …]
|
| /Zephyr-Core-2.7.6/doc/ |
| D | zephyr.doxyfile.in | 65 # will distribute the generated files over these directories. Enabling this
66 # option can be useful when feeding doxygen a huge amount of source files, where
67 # putting all generated files in the same directory would otherwise causes
131 # before files name in the file list and in the header files. If set to NO the
271 # Doxygen selects the parser to use depending on the extension of the files it
279 # or free formatted code, this is the default for Fortran type files), VHDL. For
280 # instance to make doxygen treat .inc files as Fortran files (default is PHP),
281 # and .f files as C (default is Fortran), use: inc=Fortran f=C.
283 # Note: For files without extension you can use no_extension as a placeholder.
286 # the files are not read by doxygen.
[all …]
|
