| /Zephyr-latest/dts/bindings/sensor/ |
| D | hamamatsu,s11059.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 https://datasheetspdf.com/pdf/1323325/Hamamatsu/S11059-02DT/1
10 include: [sensor-device.yaml, i2c-device.yaml]
13 high-gain:
19 integration-time:
23 Integration time (unit is us).
24 By setting this value to the desired integration time,
25 the Integration time setting and Manual timing register
|
| D | ams,tsl2561.yaml | 2 # SPDX-License-Identifier: Apache-2.0
9 include: [sensor-device.yaml, i2c-device.yaml]
12 integration-time:
16 ADC integration time in ms. The default value matches Timing Register's value at power on.
18 - 13
19 - 101
20 - 402
27 - 1
28 - 16
|
| D | vishay,vcnl4040.yaml | 2 # SPDX-License-Identifier: Apache-2.0
10 include: [sensor-device.yaml, i2c-device.yaml]
13 int-gpios:
14 type: phandle-array
18 triggered. The sensor generates an active-low level signal
21 led-current:
27 - 50
28 - 75
29 - 100
30 - 120
[all …]
|
| D | vishay,vcnl36825t.yaml | 2 # SPDX-License-Identifier: Apache-2.0
10 include: [sensor-device.yaml, i2c-device.yaml]
13 operation-mode:
19 - "auto": the sensor performs sampling continuously,
20 - "force": the sampling is performed on every fetch command.
24 Note: "force"-mode only available if low-power mode inactive.
26 measurement-period:
34 - [10, 80] ms only if low power mode is inactive
35 - [80, 320] ms only in low power mode
37 Defaults to 40 ms which is supported in both normal and low-power mode.
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/sensor/ |
| D | tsl2540.h | 2 * Copyright (c) 2022 T-Mobile USA, Inc.
4 * SPDX-License-Identifier: Apache-2.0
12 * setting the on-chip gain and integration time parameters.
25 /* Sensor Integration Time (in ms) */
|
| D | veml7700.h | 5 * SPDX-License-Identifier: Apache-2.0
50 * @brief VEML7700 integration time options for ambient light measurements.
77 * <tt>SENSOR_ATTR_LOWER_THRESH</tt> with 16-bit unsigned integer
80 * depends on the current gain and integration time settings. So a
81 * change in gain or integration time usually requires an update of
83 * into the sensor update the thresholds -after- a change of gain
84 * or integration time.
96 * @brief Integration time setting for ALS measurements (ALS_IT).
134 * enumerator as an argument will result in a <tt>-ENOTSUP</tt>.
143 * strong infrared content in the 750-800nm spectrum.
|
| D | tsl2591.h | 4 * SPDX-License-Identifier: Apache-2.0
12 * setting the on-chip gain, integration time, and persist filter parameters.
37 /* Sensor ADC Integration Time (in ms)
52 * Setting this to 1 is equivalent to the no-persist interrupt mode.
|
| /Zephyr-latest/drivers/sensor/renesas/isl29035/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
44 prompt "Integration time"
48 Lower integration time values mean lower ADC resolution.
97 depends on $(dt_compat_any_has_prop,$(DT_COMPAT_ISIL_ISL29035),int-gpios)
103 depends on $(dt_compat_any_has_prop,$(DT_COMPAT_ISIL_ISL29035),int-gpios)
130 Number of consecutive integration cycles for which the data samples
|
| /Zephyr-latest/samples/tfm_integration/ |
| D | tfm_integration.rst | 1 .. zephyr:code-sample-category:: tfm_integration
2 :name: TF-M Integration
3 :show-listing:
5 These TF-M integration examples can be used with a supported Armv8-M board, and demonstrate how
6 the TF-M APIs can be used with Zephyr.
12 secure processing environment (S), with Zephyr running in the non-secure
16 built, in addition to the TF-M S and Zephyr NS binary images. The S and NS
23 What is Trusted Firmware-M (TF-M)?
26 Trusted Firmware-M (TF-M) is the reference implementation of `Platform Security
27 Architecture (PSA) <https://pages.arm.com/psa-resources.html>`_.
[all …]
|
| /Zephyr-latest/drivers/sensor/vishay/veml7700/ |
| D | veml7700.c | 5 * SPDX-License-Identifier: Apache-2.0
30 * 16-bit command register addresses
41 * Devicetree psm-mode property value for "PSM disabled"
46 * ALS integration time setting values.
53 0x0C, /* 25 - 0b1100 */
54 0x08, /* 50 - 0b1000 */
55 0x00, /* 100 - 0b0000 */
56 0x01, /* 200 - 0b0001 */
57 0x02, /* 400 - 0b0010 */
58 0x03, /* 800 - 0b0011 */
[all …]
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 50 The main purpose of these bsim boards is to be test-benches for
51 integration testing of embedded code on workstation/simulation.
52 Integration testing in the sense that the code under test will, at the very
59 The intention being to be able to run tests much faster than real time,
80 - Unit tests:
85 - Integration tests on real HW: Allows testing with the real SW
88 As such can provide better integration coverage than simulation in some cases,
92 They otherwise serve a very similar purpose to simulation integration tests.
93 - Integration tests on workstation (what the POSIX arch and these boards enable)
95 - Using bsim boards: Allow testing the embedded SW (or a subset), including
[all …]
|
| /Zephyr-latest/tests/subsys/fs/fat_fs_api/src/ |
| D | main.c | 5 * SPDX-License-Identifier: Apache-2.0
8 #include <time.h>
14 /* Time integration for filesystem */
17 time_t unix_time = time(NULL); in get_fattime()
20 /* Convert to calendar time */ in get_fattime()
23 /* From http://elm-chan.org/fsw/ff/doc/fattime.html */ in get_fattime()
24 return (DWORD)(cal->tm_year - 80) << 25 | (DWORD)(cal->tm_mon + 1) << 21 | in get_fattime()
25 (DWORD)cal->tm_mday << 16 | (DWORD)cal->tm_hour << 11 | (DWORD)cal->tm_min << 5 | in get_fattime()
26 (DWORD)cal->tm_sec >> 1; in get_fattime()
|
| /Zephyr-latest/doc/contribute/ |
| D | external.rst | 1 .. _external-contributions:
7 order to avoid re-implementing basic functionality or features that are readily
21 :ref:`external-tooling` section at the end of the page.
28 External source code licensed under the Apache-2.0 license is not subject to
36 :ref:`external-src-process` section for more details.
42 https://www.zephyrproject.org/wp-content/uploads/2023/08/LF-Zephyr-Charter-2023.08.21.pdf
62 - Is this the most optimal way to introduce the functionality to the project?
65 - Is the external project being actively maintained? This is particularly
67 - Have alternatives to the particular implementation proposed been considered?
70 Mode of integration
[all …]
|
| D | bin_blobs.rst | 1 .. _bin-blobs:
12 Zephyr supports downloading and using third-party binary blobs via its built-in
15 `upstream (vanilla) Zephyr <https://github.com/zephyrproject-rtos/zephyr>`_.
18 the support for binary blobs in forks or third-party distributions of Zephyr. In
21 therefore free to create Zephyr-based downstream software which uses binary
30 click-through or other EULA-like workflow when users fetch and install blobs.
35 Blobs must be hosted on the Internet and managed by third-party infrastructure.
45 Blobs are fetched from official third-party sources by the :ref:`west blobs
46 <west-blobs>` command.
49 <modules-bin-blobs>` files included in separate Zephyr :ref:`module repositories
[all …]
|
| /Zephyr-latest/drivers/sensor/s11059/ |
| D | s11059.c | 4 * SPDX-License-Identifier: Apache-2.0
7 * https://datasheetspdf.com/pdf/1323325/Hamamatsu/S11059-02DT/1
70 int64_t integration_time; /* integration period (unit: us) */
83 /* Integration timing in Manual integration mode */
104 const struct s11059_dev_config *cfg = dev->config; in s11059_samples_read()
108 return -EINVAL; in s11059_samples_read()
111 rc = i2c_burst_read_dt(&cfg->bus, addr, (uint8_t *)val, size); in s11059_samples_read()
125 const struct s11059_dev_config *cfg = dev->config; in s11059_control_write()
128 return i2c_write_dt(&cfg->bus, opcode, sizeof(opcode)); in s11059_control_write()
133 const struct s11059_dev_config *cfg = dev->config; in s11059_manual_timing_write()
[all …]
|
| /Zephyr-latest/drivers/sensor/ams/tsl2591/ |
| D | tsl2591.h | 4 * SPDX-License-Identifier: Apache-2.0
62 /* Integration Time Modes */
105 /* Max integration time (in ms) for single step */
|
| D | tsl2591.c | 4 * SPDX-License-Identifier: Apache-2.0
18 const struct tsl2591_config *config = dev->config; in tsl2591_reg_read()
21 return i2c_write_read_dt(&config->i2c, &cmd, 1U, buf, size); in tsl2591_reg_read()
26 const struct tsl2591_config *config = dev->config; in tsl2591_reg_write()
29 return i2c_write_dt(&config->i2c, cmd, 2U); in tsl2591_reg_write()
52 struct tsl2591_data *data = dev->data; in tsl2591_sample_fetch()
65 /* Check if ALS has completed an integration cycle since AEN asserted. in tsl2591_sample_fetch()
66 * If not, sleep for the duration of an integration cycle to ensure valid reading. in tsl2591_sample_fetch()
69 k_msleep((data->atime / 100) * TSL2591_MAX_TIME_STEP); in tsl2591_sample_fetch()
81 LOG_ERR("Failed to re-enable ALS"); in tsl2591_sample_fetch()
[all …]
|
| /Zephyr-latest/drivers/sensor/vishay/vcnl4040/ |
| D | vcnl4040.c | 4 * SPDX-License-Identifier: Apache-2.0
21 const struct vcnl4040_config *config = dev->config; in vcnl4040_read()
25 ret = i2c_write_read_dt(&config->i2c, in vcnl4040_read()
37 const struct vcnl4040_config *config = dev->config; in vcnl4040_write()
44 ret = i2c_write_dt(&config->i2c, buf, sizeof(buf)); in vcnl4040_write()
56 struct vcnl4040_data *data = dev->data; in vcnl4040_sample_fetch()
66 k_mutex_lock(&data->mutex, K_FOREVER); in vcnl4040_sample_fetch()
70 &data->proximity); in vcnl4040_sample_fetch()
79 &data->light); in vcnl4040_sample_fetch()
86 k_mutex_unlock(&data->mutex); in vcnl4040_sample_fetch()
[all …]
|
| /Zephyr-latest/doc/services/tfm/ |
| D | testsuites.rst | 4 TF-M includes two sets of test suites:
6 * tf-m-tests - Standard TF-M specific regression tests
7 * psa-arch-tests - Test suites for specific PSA APIs (secure storage, etc.)
12 TF-M Regression Tests
19 integration between the NS RTOS (Zephyr in this case) and the secure
20 application (TF-M).
27 being followed by the secure application, TF-M being an implementation of
30 Only one of these suites can be run at a time, with the available test suites
37 your specific board, RTOS (Zephyr here), and PSA implementation (TF-M in this
41 changes to TF-M, such as enabling a new TF-M board target, or making changes
[all …]
|
| D | integration.rst | 1 Trusted Firmware-M Integration
4 The Trusted Firmware-M (TF-M) section contains information about the
5 integration between TF-M and Zephyr RTOS. Use this information to help
6 understand how to integrate TF-M with Zephyr for Cortex-M platforms and make
7 use of its secure run-time services in Zephyr applications.
12 TF-M will be built for the secure processing environment along with Zephyr if
16 and all config flags required for TF-M should be set in a board variant with
22 `modules/trusted-firmware-m/Kconfig.tfm <https://github.com/zephyrproject-rtos/zephyr/blob/main/mod…
23 to the board name that TF-M expects for this target, so that it knows which
29 The ``mps2/an521/cpu0`` board target is a dual-core Arm Cortex-M33 evaluation board that generates
[all …]
|
| /Zephyr-latest/.github/workflows/ |
| D | greet_first_time_contributor.yml | 1 name: Greet first time contributor
11 runs-on: ubuntu-22.04
12 if: github.repository == 'zephyrproject-rtos/zephyr'
15 - uses: actions/checkout@v4
16 - uses: zephyrproject-rtos/action-first-interaction@v1.1.1-zephyr-5
18 repo-token: ${{ secrets.GITHUB_TOKEN }}
20 issue-message: >
22 for our open-source project. ��
26 for your time and effort. ����
28 pr-opened-message: >
[all …]
|
| /Zephyr-latest/soc/mediatek/mt8xxx/ |
| D | CMakeLists.txt | 2 # SPDX-License-Identifier: Apache-2.0
22 # platforms are identical. The west sign integration similarly needs
25 # its own at build time. And likewise the signing key isn't provided
41 COMMAND west $<$<BOOL:${CMAKE_VERBOSE_MAKEFILE}>:--verbose> sign
42 --if-tool-available --tool rimage --build-dir ${CMAKE_BINARY_DIR}
|
| /Zephyr-latest/doc/project/ |
| D | code_flow.rst | 1 .. _code-flow-and-branches:
14 collab-\*
23 vx.y-branch
29 turnaround time, and encourages collaboration and streamlines communication
34 final integration.
37 possible to initiate in-depth discussions around new additions before
54 - Use the infrastructure and tools provided by the project (GitHub, Git)
55 - All changes to collaboration branches shall come in form of github pull requests.
56 - Force pushing a collaboration branch is only allowed when rebasing against the main branch.
57 - Review changes coming from team members and request review from branch owners
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ptp.rst | 3 Precision Time Protocol (PTP)
15 The stack supports the protocol and procedures as defined in the `IEEE 1588-2019 standard`_
24 * Integration with ptp_clock driver
35 .. csv-table:: Supported features
48 Non-volatile storage,
60 Based on Table 59 from section 15.5.2.3 of the IEEE 1588-2019 following management TLVs
63 .. csv-table:: Supported management message's IDs
70 0x0003, SAVE_IN_NON_VOLATILE_STORAGE, -
71 0x0004, RESET_NON_VOLATILE_STORAGE, -
72 0x0005, INITIALIZE, -
[all …]
|
| /Zephyr-latest/doc/introduction/ |
| D | index.rst | 6 The Zephyr OS is based on a small-footprint kernel designed for use on
7 resource-constrained and embedded systems: from simple embedded environmental
13 - ARCv2 (EM and HS) and ARCv3 (HS6X)
14 - ARMv6-M, ARMv7-M, and ARMv8-M (Cortex-M)
15 - ARMv7-A and ARMv8-A (Cortex-A, 32- and 64-bit)
16 - ARMv7-R, ARMv8-R (Cortex-R, 32- and 64-bit)
17 - Intel x86 (32- and 64-bit)
18 - MIPS (MIPS32 Release 1 specification)
19 - NIOS II Gen 2
20 - RISC-V (32- and 64-bit)
[all …]
|
