| /Zephyr-latest/ |
| 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-latest/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:
39 :file:`BOARD.dts` includes one or more ``.dtsi`` files. These ``.dtsi`` files
41 ``.dtsi`` files. They can also describe other common hardware features shared by
[all …]
|
| /Zephyr-latest/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-latest/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-latest/subsys/logging/backends/ |
| D | Kconfig.fs | 28 bool "Old log files overwrite"
31 When enabled backend overwrites oldest log files.
46 User defined name of log files saved in the file system.
53 Directory to which log files will be written.
63 int "Max number of files containing logs"
66 Limit of number of files with logs. It is also limited by
|
| /Zephyr-latest/drivers/firmware/scmi/ |
| D | CMakeLists.txt | 5 # SCMI core files
10 # SCMI protocol helper files
|
| /Zephyr-latest/samples/subsys/fs/fs_sample/ |
| D | Kconfig | 11 bool "When no files are found on mounted partition create some"
14 In case when no files could be listed, because there are none,
19 easily add files with use of other device.
|
| /Zephyr-latest/cmake/modules/ |
| D | hwm_v2.cmake | 8 # The result from list_hardware.py is then used to generate Kconfig files for
11 # The following files are generated in '<kconfig-binary-dir>/soc'
12 # - Kconfig.defconfig: Contains references to SoC defconfig files for Zephyr integration.
13 # - Kconfig: Contains references to regular SoC Kconfig files for Zephyr integration.
14 # - Kconfig.soc: Contains references to generic SoC Kconfig files.
15 # - Kconfig.sysbuild: Contains references to SoC sysbuild Kconfig files.
18 # - Kconfig: Contains references to regular arch Kconfig files for Zephyr integration.
26 # Internal helper function for creation of Kconfig files.
|
| D | dts.cmake | 15 # - To Zephyr and application source code files, as a C macro API
25 # - To CMake files, after this module has finished running, using
28 # - To Kconfig files, both using some Kconfig symbols we generate
36 # files in scripts/dts to make all this work. We also optionally will
60 # - DTS_INCLUDE_FILES is set to a ;-list of all devicetree files
62 # system will be regenerated if any of those files change)
64 # will be ready for use in other CMake list files that run
68 # - BINARY_DIR_INCLUDE_GENERATED: where to put generated include files
70 # implementation files (like bindings, vendor prefixes, etc.) are
74 # may be found for devicetree files
[all …]
|
| D | configuration_files.cmake | 5 # Zephyr build system configuration files.
7 # Locate the Kconfig and DT config files that are to be used.
15 # - DTC_OVERLAY_FILE: List of devicetree overlay files
16 # - EXTRA_DTC_OVERLAY_FILE List of additional devicetree overlay files
63 Multiple files may be listed, e.g. CONF_FILE=\"prj1.conf;prj2.conf\" \
93 settings in the board's .dts file. Multiple files may be listed, e.g. \
|
| /Zephyr-latest/tests/subsys/fs/littlefs/src/ |
| D | test_lfs_basic.c | 141 struct fs_file_t files[CONFIG_FS_LITTLEFS_NUM_FILES]; in num_files() local
145 memset(files, 0, sizeof(files)); in num_files()
148 while (fi < ARRAY_SIZE(files)) { in num_files()
149 struct fs_file_t *const file = &files[fi]; in num_files()
167 struct fs_file_t *const file = &files[fi]; in num_files()
|
| /Zephyr-latest/modules/nanopb/ |
| D | nanopb.cmake | 25 # zephyr_nanopb_sources(<target> <proto-files>)
27 # Generate source and header files from provided .proto files and
|
| /Zephyr-latest/subsys/fs/ |
| D | fuse_fs_access.c | 39 static struct fs_file_t files[NUMBER_OF_OPEN_FILES]; variable
274 err = fs_open(&files[handle], path, FS_O_CREATE | FS_O_WRITE); in fuse_fs_access_create()
297 fs_close(&files[fi->fh]); in fuse_fs_access_release()
315 err = fs_seek(&files[fi->fh], off, FS_SEEK_SET); in fuse_fs_access_read()
320 err = fs_read(&files[fi->fh], buf, size); in fuse_fs_access_read()
336 err = fs_seek(&files[fi->fh], off, FS_SEEK_SET); in fuse_fs_access_write()
341 err = fs_write(&files[fi->fh], buf, size); in fuse_fs_access_write()
357 err = fs_truncate(&files[fi->fh], size); in fuse_fs_access_ftruncate()
492 while (i < ARRAY_SIZE(files)) { in fuse_fs_access_init()
493 fs_file_t_init(&files[i]); in fuse_fs_access_init()
|
| /Zephyr-latest/doc/develop/west/ |
| D | zephyr-cmds.rst | 63 application CMakeLists.txt files that are outside of your workspace will be
78 from source files to the corresponding generated build files.
79 ``SPDX-License-Identifier`` comments in source files are scanned and filled
110 - :file:`app.spdx`: BOM for the application source files used for the build
111 - :file:`zephyr.spdx`: BOM for the specific Zephyr source code files used for the build
112 - :file:`build.spdx`: BOM for the built output files
122 source files that are compiled to generate the built library files.
135 files (e.g. ``.c``, ``.S``) in the bills-of-materials, also attempt to
136 determine the specific header files that are included for each ``.c`` file.
143 document, :file:`sdk.spdx`, which lists header files included from the SDK.
[all …]
|
| /Zephyr-latest/scripts/checkpatch/ |
| D | do_checkpatch.sh | 14 files=$(for d in ${dirs_to_check}; do find $d/ -type f -name '*.[ch]'; done)
15 for i in $files; do
|
| /Zephyr-latest/cmake/util/ |
| D | fmerge.cmake | 3 # Merges a list of files into a destination file.
4 # Usage: list of files as arguments, first argument is the destination file
|
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 10 Snippets are defined using YAML files named :file:`snippet.yml`.
79 :file:`snippet.yml` files underneath a subdirectory named :file:`snippets/`,
83 system will look for :file:`snippet.yml` files underneath the following
89 The :file:`snippet.yml` files can be nested anywhere underneath these
103 And then any :file:`snippet.yml` files in ``baz/snippets`` will
133 This principle applies to both Kconfig fragments (``.conf`` files) and
134 devicetree overlays (``.overlay`` files).
152 .. _snippets-conf-files:
154 ``.conf`` files
168 Sysbuild ``.conf`` files
[all …]
|
| /Zephyr-latest/doc/services/serialization/ |
| D | nanopb.rst | 12 Nanopb uses the protocol buffer compiler to generate source and header files,
60 Adding ``proto`` files can be done with the ``zephyr_nanopb_sources()`` CMake function which
61 ensures the generated header and source files are created before building the specified target.
67 The internal CMake generator has an extension to configure ``*.options.in`` files automatically
|
| /Zephyr-latest/modules/hal_infineon/mtb-template-cat1/ |
| D | CMakeLists.txt | 7 set(cat1a_dir ${template_dir}/files/templates/cat1a)
8 set(cat1b_dir ${template_dir}/files/templates/cat1b)
|
| /Zephyr-latest/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.
59 Where the first argument is the file/files and the second
91 * Multiple files can be passed to the FILES argument, or CMake generator
92 expressions can be used to relocate a comma-separated list of files
121 used when we want to move the content of a specific file (or set of files) to a
147 Take care if relocating kernel/arch files, some contain early initialization
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/figures/ |
| D | .gitignore | 1 # Ignore drawio backup files
|
| /Zephyr-latest/modules/thrift/cmake/ |
| D | thrift.cmake | 13 out_dir # Output directory for generated files
18 # Generated files in ${ARGN}
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 31 The main zephyr repository contains Zephyr's source code, configuration files,
36 The files in the **application directory** link Zephyr and any modules with the
37 application. This directory contains all application-specific files, such as
38 application-specific configuration files and source code.
40 Here are the files in a simple Zephyr application:
55 application files, and links the application directory with Zephyr's CMake
57 such as board-specific configuration files, the ability to run and
66 more devicetree overlays, and other default files are also searched for.
77 Kconfig fragments, and other default files are also searched for.
87 * **main.c**: A source code file. Applications typically contain source files
[all …]
|
| /Zephyr-latest/scripts/west_commands/tests/nrf/ |
| D | README.rst | 1 This directory contains test data files for test_nrf.py.
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | 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/modules/FindHostTools.cmake` and
28 :file:`generic.cmake` and :file:`target.cmake` files should contain.
54 target.cmake files located under
|
