Home
last modified time | relevance | path

Searched +full:data +full:- +full:hold +full:- +full:time (Results 1 – 25 of 137) sorted by relevance

123456

/Zephyr-latest/dts/bindings/i2c/
Dite,enhance-i2c.yaml2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "ite,enhance-i2c"
8 include: ite,common-i2c.yaml
11 prescale-scl-low:
17 The resulting SCL cycle time is given by the following formula:
21 data-hold-time:
25 - 3
26 - 4
27 - 5
28 - 6
[all …]
/Zephyr-latest/dts/bindings/memory-controllers/
Datmel,sam-smc.yaml2 # SPDX-License-Identifier: Apache-2.0
7 The SMC allows to interface with static-memory mapped external devices such as
19 pinctrl-0 = <&smc_default>;
20 pinctrl-names = "default";
25 atmel,smc-write-mode = "nwe";
26 atmel,smc-read-mode = "nrd";
27 atmel,smc-setup-timing = <1 1 1 1>;
28 atmel,smc-pulse-timing = <6 6 6 6>;
29 atmel,smc-cycle-timing = <7 7>;
33 The above example configures a is66wv51216dbll-55 device. The device is a
[all …]
Dst,stm32-fmc-nor-psram.yaml2 # SPDX-License-Identifier: Apache-2.0
11 - 8 bits
12 - 16 bits
13 - 32 bits
15 - Asynchronous mode
16 - Burst mode for synchronous accesses with configurable option to split burst
18 - Multiplexed or non-multiplexed
20 - Asynchronous mode
21 - Burst mode for synchronous accesses
22 - Multiplexed or non-multiplexed
[all …]
/Zephyr-latest/dts/bindings/spi/
Despressif,esp32-spi.yaml3 compatible: "espressif,esp32-spi"
5 include: [spi-controller.yaml, pinctrl-device.yaml]
11 pinctrl-0:
14 pinctrl-names:
17 half-duplex:
20 Enable half-duplex communication mode.
22 Transmit data before receiving it, instead of simultaneously
24 dummy-comp:
31 Enable 3-wire mode
33 Use MOSI for both sending and receiving data
[all …]
/Zephyr-latest/dts/bindings/mtd/
Dnxp,imx-flexspi-device.yaml2 # SPDX-License-Identifier: Apache-2.0
6 include: [spi-device.yaml, "jedec,jesd216.yaml"]
9 cs-interval-unit:
13 - 1
14 - 256
20 cs-interval:
28 cs-setup-time:
32 Chip select setup time, in serial clock cycles. See the TCSS field in
36 cs-hold-time:
40 Chip select hold time, in serial clock cycles. See the TCSH field in
[all …]
/Zephyr-latest/dts/bindings/bluetooth/
Dzephyr,bt-hci-spi.yaml1 # Copyright (c) 2018, I-SENSE group of ICCS
2 # SPDX-License-Identifier: Apache-2.0
8 compatible: "zephyr,bt-hci-spi"
10 include: [spi-device.yaml, bt-hci.yaml]
13 irq-gpios:
14 type: phandle-array
17 reset-gpios:
18 type: phandle-array
21 reset-assert-duration-ms:
24 Minimum duration to hold the reset-gpios pin low for.
[all …]
/Zephyr-latest/dts/bindings/qspi/
Dnxp,s32-qspi.yaml2 # SPDX-License-Identifier: Apache-2.0
8 up to eight bidirectional bidirectional data lines, depending on the platform.
10 compatible: "nxp,s32-qspi"
12 include: [base.yaml, pinctrl-device.yaml]
20 "#address-cells":
23 "#size-cells":
26 data-rate:
29 - SDR
30 - DDR
33 - Single Data Rate (SDR): sampling of incoming data occurs on single edges.
[all …]
/Zephyr-latest/drivers/misc/coresight/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
4 DT_COMPAT_NORDIC_NRF_TBM := nordic,nrf-tbm
13 Module handles data stored in the ETR circular buffer (e.g. STM logging
14 data). Busyness is tracked using TBM (Trace Buffer Monitor) peripheral
45 In debug mode STPv2 decoded data is printed.
53 int "Thread backoff time (ms)"
56 Determines how often attempt to dump the data is performed.
59 int "Backoff time during flushing (ms)"
62 When thread triggers flushing of ETR data, it periodically checks if
63 there is still a pending ETR data. This option specifies how often
[all …]
/Zephyr-latest/boards/nxp/mimxrt1050_evk/
Dmimxrt1050_evk_mimxrt1052_hyperflash.dts4 * SPDX-License-Identifier: Apache-2.0
11 zephyr,flash-controller = &s26ks512s0;
13 zephyr,code-partition = &slot0_partition;
19 ahb-prefetch;
20 ahb-read-addr-opt;
21 pinctrl-0 = <&pinmux_flexspi1>;
22 pinctrl-names = "default";
23 ahb-bufferable;
24 ahb-cacheable;
25 sck-differential-clock;
[all …]
/Zephyr-latest/boards/nxp/mimxrt1060_evk/
Dmimxrt1060_evk_mimxrt1062_hyperflash.dts4 * SPDX-License-Identifier: Apache-2.0
11 zephyr,flash-controller = &s26ks512s0;
13 zephyr,code-partition = &slot0_partition;
19 ahb-prefetch;
20 ahb-read-addr-opt;
21 ahb-bufferable;
22 ahb-cacheable;
23 sck-differential-clock;
24 combination-mode;
25 rx-clock-source = <3>;
[all …]
/Zephyr-latest/include/zephyr/ipc/
Dipc_service.h4 * SPDX-License-Identifier: Apache-2.0
43 * - INSTANCE: an instance is the external representation of a physical
48 * OpenAMP-based backends, an instance is usually represented by a
53 * send data between domains / CPUs. To send and receive data the
58 * instance, each one used to exchange data, possibly with different
62 * init time), while the registration of the endpoints is left to
63 * the user (usually at run time).
65 * - ENDPOINT: an endpoint is the entity the user must use to send / receive
66 * data between two domains (connected by the instance). An
69 * - BACKEND: the backend must take care of at least two different things:
[all …]
/Zephyr-latest/doc/services/storage/zms/
Dzms.rst5 Zephyr Memory Storage is a new key-value storage system that is designed to work with all types
6 of non-volatile storage technologies. It supports classical on-chip NOR flash as well as new
8 data on these types of devices can be overwritten directly at any time.
12 ZMS divides the memory space into sectors (minimum 2), and each sector is filled with key-value
15 The key-value pair is divided into two parts:
17 - The key part is written in an ATE (Allocation Table Entry) called "ID-ATE" which is stored
19 - The value part is defined as "DATA" and is stored raw starting from the top of the sector
21 Additionally, for each sector we store at the last positions Header-ATEs which are ATEs that
37 .. list-table::
39 :header-rows: 1
[all …]
/Zephyr-latest/doc/kernel/memory_management/
Ddemand_paging.rst6 Demand paging provides a mechanism where data is only brought into physical
8 conceptually divided in page-sized page frames as regions to hold data.
10 * When the processor tries to access data and the data page exists in
13 * When the processor tries to access the data page that does not exist
15 the corresponding data page from backing store into physical memory if
17 the eviction algorithm is invoked to select a data page to be paged out,
18 thus freeing up a page frame for new data to be paged in. If this data
19 page has been modified after it is first paged in, the data will be
21 after written back into backing store, the data page is now considered
23 then invokes the backing store to page in the data page corresponding to
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dcore.rst21 the LPN API allows the application to trigger the polling at any time through
35 The Replay Protection List (RPL) is used to hold recently received sequence
49 RPL entry (or entries) at any time (or sufficiently before power loss)
53 Setting :kconfig:option:`CONFIG_BT_MESH_RPL_STORE_TIMEOUT` to -1 allows to completely
56 requires that sufficient power backup is available from the time this API
66 :kconfig:option:`CONFIG_BT_MESH_RPL_STORE_TIMEOUT` to -1 and not storing
80 storing of data is scheduled, it can not be rescheduled until the work item is
109 This means that the system workqueue is blocked for the time it takes to store
111 will make the device non-responsive for a noticeable amount of time.
118 All mesh stack bearers advertise data with the :c:macro:`BT_ID_DEFAULT` local identity.
Daccess.rst24 data, which is passed to :c:func:`bt_mesh_init` during initialization. The
28 <https://www.bluetooth.com/specifications/mesh-specifications/>`_. All models
45 data, and cannot be changed at runtime. The end of the opcode list is
58 The maximum number of supported application keys each model can hold is
73 can hold is configured with the :kconfig:option:`CONFIG_BT_MESH_MODEL_GROUP_COUNT`
137 Model data storage
140 Mesh models may have data associated with each model instance that needs to be
142 data, leveraging the internal model instance encoding scheme. Models can store
143 one user defined data entry per instance by calling
144 :c:func:`bt_mesh_model_data_store`. To be able to read out the data the
[all …]
/Zephyr-latest/doc/kernel/data_structures/
Dring_buffers.rst7 first-in-first-out order.
10 "streaming" copying of data, Zephyr provides a ``struct ring_buf``
11 abstraction to manage copies of such data in and out of a shared
14 Two content data modes are supported:
18 * **Data item mode**: Multiple 32-bit word data items with metadata
20 chunks of up to 1020 bytes. Each data item also has two
21 associated metadata values: a type identifier and a 16-bit
22 integer value, both of which are application-specific.
24 While the underlying data structure is the same, it is not
43 * A **data buffer** of bytes or 32-bit words. The data buffer contains the raw
[all …]
/Zephyr-latest/subsys/demand_paging/backing_store/
Dram.c4 * SPDX-License-Identifier: Apache-2.0
6 * RAM-based memory buffer backing store implementation for demo purposes
23 * management is necessary. Clean copies of paged-in data pages may be kept
27 * large to hold clean copies of all mapped memory.
32 * This implies that all data pages are treated as dirty as
33 * K_MEM_PAGE_FRAME_BACKED is never set, even if the data page was paged out before
38 * a paged-in data page in a custom field of its associated k_mem_page_frame, and
45 * eviction algorithm, to free backing store locations for loaded data pages
51 * starts getting set for certain page frames after a page-in (and possibly
52 * cleared at a later time).
[all …]
/Zephyr-latest/drivers/flash/
Dflash_stm32_xspi.h4 * SPDX-License-Identifier: Apache-2.0
30 /* Max Time value during reset or erase operation */
84 /* XSPI handle is modifiable ; so part of data struct */
103 /* Table to hold the jedec Read ID given by the octoFlash const */
Dspi_nor.c2 * Copyright (c) 2018 Savoir-Faire Linux.
8 * SPDX-License-Identifier: Apache-2.0
36 * * Some devices support a Deep Power-Down mode which reduces current
41 * * PM_DEVICE_STATE_SUSPENDED corresponds to deep-power-down mode;
63 #define DEV_CFG(_dev_) ((const struct spi_nor_config * const) (_dev_)->config)
66 /* MXICY Low-power/high perf mode is second bit in configuration register 2 */
72 /* Build-time data associated with the device. */
92 /* Expected JEDEC ID, from jedec-id property */
96 /* Optional support for entering 32-bit address mode. */
101 /* Length of BFP structure, in 32-bit words. */
[all …]
/Zephyr-latest/drivers/usb_c/tcpc/
Ducpd_stm32_priv.h4 * SPDX-License-Identifier: Apache-2.0
17 * @brief The packet type(SOP*) consists of 2-bytes
22 * @brief The message header consists of 2-bytes
98 #define UCPD_ANASUB_TO_RP(r) ((r - 1) & 0x3)
168 /* Data Role */
194 TX_MSG_NONE = -1,
219 /* Power Deliver message data including the message header */
234 union pd_buffer data; member
243 /* Application supplied data that's passed to the
246 void *data; member
[all …]
/Zephyr-latest/drivers/console/
DKconfig3 # Copyright (c) 2014-2015 Wind River Systems, Inc.
5 # SPDX-License-Identifier: Apache-2.0
82 int "Fixed amount of time to keep the UART console in use flag true"
86 Fixed amount of time which unit is milliseconds to keep the UART
95 Useful in board bring-up if there aren't any working serial
99 DT_CHOSEN_Z_RAM_CONSOLE := zephyr,ram-console
107 be examined at runtime with a debugger. Useful in board bring-up
117 examined by a debugger or software tool from a parallel-running OS.
126 NULL-terminated leave one byte unused, the actual length is
136 Segger J-Link software and displayed on a computer in real-time.
[all …]
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_pkt.rst13 Network packets are the main data the networking stack manipulates.
14 Such data is represented through the net_pkt structure which provides
15 a means to hold the packet, write and read it, as well as necessary
16 metadata for the core to hold important information. Such an object is
19 The data structure and the whole API around it are defined in
37 All net_pkt objects come from a pre-defined pool of struct net_pkt.
40 .. code-block:: c
49 .. code-block:: c
59 .. code-block:: c
66 .. code-block:: c
[all …]
/Zephyr-latest/dts/bindings/pinctrl/
Dpincfg-node.yaml2 # SPDX-License-Identifier: Apache-2.0
7 Many data items that are represented in a pin configuration node are
16 https://www.kernel.org/doc/Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml
19 bias-disable:
23 bias-high-impedance:
25 description: high impedance mode ("third-state", "floating")
27 bias-bus-hold:
31 bias-pull-up:
33 description: enable pull-up resistor
35 bias-pull-down:
[all …]
/Zephyr-latest/dts/bindings/mspi/
Dmspi-device.yaml2 # SPDX-License-Identifier: Apache-2.0
8 on-bus: mspi
14 mspi-max-frequency:
22 mspi-io-mode:
25 - "MSPI_IO_MODE_SINGLE"
26 - "MSPI_IO_MODE_DUAL"
27 - "MSPI_IO_MODE_DUAL_1_1_2"
28 - "MSPI_IO_MODE_DUAL_1_2_2"
29 - "MSPI_IO_MODE_QUAD"
30 - "MSPI_IO_MODE_QUAD_1_1_4"
[all …]
/Zephyr-latest/samples/boards/st/ccm/
DREADME.rst1 .. zephyr:code-sample:: stm32_ccm
17 are initialized. Like the normal data section the initial
26 buffers that will receive data). Compared to bss or data the
33 .. code-block:: console
45 .. zephyr-app-commands::
46 :zephyr-app: samples/boards/st/ccm
49 The first time the example is run after power on, the output will
52 .. code-block:: console
54 ***** BOOTING ZEPHYR OS v1.10.99 - BUILD: Jan 14 2018 09:32:46 *****
61 Initialised DATA area : [0x10000014, 0x10000021)
[all …]

123456