Home
last modified time | relevance | path

Searched refs:of (Results 1 – 25 of 2649) sorted by relevance

12345678910>>...106

/Zephyr-latest/subsys/bluetooth/audio/
DKconfig.mpl24 Use this option to set the name of the media player.
27 int "Max length of media player name"
31 Sets the maximum number of bytes (including the null termination) of
32 the name of the media player.
38 Use this option to set the URL of the Media Player Icon.
41 int "Max length of media player icon URL"
45 Sets the maximum number of bytes (including the null termination) of
49 int "Max length of the title of a track"
53 Sets the maximum number of bytes (including the null termination) of
54 the title of any track in the media player.
[all …]
DKconfig.ascs16 int "Maximum number of Audio Stream Endpoint Sink Characteristics"
20 An ASE Sink characteristic represents the state of an ASE, which is
21 coupled to a single direction of a unicast Audio Stream.
24 int "Maximum number of Audio Stream Endpoint Source Characteristics"
28 An ASE Source characteristic represents the state of an ASE, which is
29 coupled to a single direction of a unicast Audio Stream.
38 int "Number of simultaneously supported ASE sessions"
42 The number of simultanesouly supported active ASEs, in particular
43 meaning the number of ASEs that are allowed to be in a non-idle state at
47 int "Milliseconds of delay before ASCS disconnects ISO after stream stop"
[all …]
/Zephyr-latest/samples/subsys/sip_svc/
DREADME.rst9 This sample demonstrates the usage of SiP SVC subsystem.This sample
39 Got response of transaction id 0x00 and voltage is 0.846878v
40 Got response of transaction id 0x01 and voltage is 0.858170v
41 Got response of transaction id 0x02 and voltage is 0.860168v
42 Got response of transaction id 0x03 and voltage is 0.846832v
43 Got response of transaction id 0x04 and voltage is 0.858337v
44 Got response of transaction id 0x05 and voltage is 0.871704v
45 Got response of transaction id 0x06 and voltage is 0.859421v
46 Got response of transaction id 0x07 and voltage is 0.857254v
47 Got response of transaction id 0x08 and voltage is 0.858429v
[all …]
/Zephyr-latest/subsys/net/lib/lwm2m/
DKconfig.ucifi20 int "Maximum # of uCIFI Battery object instances"
23 This setting establishes the total count of uCIFI Battery
37 int "Maximum # of uCIFI LPWAN object instances"
41 This value sets the maximum allowable number of LPWAN instances.
44 int "Maximum # of IPv4 addresses"
48 This value sets the maximum number of IPv4 addresses assigned to a
52 int "Maximum # of IPv6 addresses"
56 This value sets the maximum number of IPv6 addresses assigned to a
60 int "Maximum # of network addresses"
64 This value sets the maximum number of LPWAN network addresses assigned
[all …]
/Zephyr-latest/
DCODE_OF_CONDUCT.md1 # Contributor Covenant Code of Conduct
6 community a harassment-free experience for everyone, regardless of age, body
8 identity and expression, level of experience, education, socio-economic status,
17 Examples of behavior that contributes to a positive environment for our
21 * Being respectful of differing opinions, viewpoints, and experiences
28 Examples of unacceptable behavior include:
30 * The use of sexualized language or imagery, and sexual attention or advances of
41 Community leaders are responsible for clarifying and enforcing our standards of
48 not aligned to this Code of Conduct, and will communicate reasons for moderation
53 This Code of Conduct applies within all community spaces, and also applies when
[all …]
DLICENSE10 and distribution as defined by Sections 1 through 9 of this document.
15 "Legal Entity" shall mean the union of the acting entity and all
17 control with that entity. For the purposes of this definition,
19 direction or management of such entity, whether by contract or
20 otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 outstanding shares, or (iii) beneficial ownership of such entity.
31 transformation or translation of a Source form, including but
35 "Work" shall mean the work of authorship, whether in Source or
43 represent, as a whole, an original work of authorship. For the purposes
44 of this License, Derivative Works shall not include works that remain
[all …]
/Zephyr-latest/samples/arch/smp/pktqueue/
DREADME.rst10 (essentially checksum calculation from IP Header Validation) of the Internet protocol
13 provides an indication of the potential performance of a microprocessor in an
16 At the beginning of the application the array (size defined in SIZE_OF_QUEUE)
17 of packet headers is initialized. Each header contains some random data of size
19 in appropriate field defined by CRC_BYTE_1 and CRC_BYTE_2. The contents of
25 |Version| IHL |Type of Service| Total Length |
39 in QUEUE_NUM). After that for each pair of "sender"/"receiver" queues one thread
43 of them first pick the header from "sender" queue, calculates crc and if
47 As soon as all headers in each pair of queues are moved from "sender" to
48 "receiver" queue the execution of threads(related to pair) are terminated.
[all …]
/Zephyr-latest/lib/libc/common/
DKconfig7 common implementation of abort().
12 common implementation of asctime().
15 bool "Thread-safe version of asctime()"
18 common implementation of asctime_r().
24 common implementation of ctime().
27 bool "Thread-safe version of ctime()"
30 common implementation of ctime_r().
35 common implementation of gmtime_r().
41 Simple implementation of localtime() & localtime_r().
48 common implementation of time().
[all …]
/Zephyr-latest/subsys/fs/
DKconfig.littlefs19 int "Maximum number of opened files"
25 int "Maximum number of opened directories"
31 int "Minimum size of a block read"
34 All read operations will be a multiple of this value.
37 int "Minimum size of a block program"
40 All program operations will be a multiple of this value.
43 int "Size of block caches in bytes"
46 Each cache buffers a portion of a block in RAM. The littlefs
49 more data and reducing the number of disk accesses. Must be a
50 multiple of the read and program sizes of the underlying flash
[all …]
/Zephyr-latest/doc/kernel/timing_functions/
Dindex.rst6 The timing functions can be used to obtain execution time of
7 a section of code to aid in analysis and optimization.
26 2. Call :c:func:`timing_start` to signal the start of gathering of
29 3. Call :c:func:`timing_counter_get` to mark the start of code
32 4. Call :c:func:`timing_counter_get` to mark the end of code
35 5. Call :c:func:`timing_cycles_get` to get the number of timer cycles
36 between start and end of code execution.
38 6. Call :c:func:`timing_cycles_to_ns` with total number of cycles
39 to convert number of cycles to nanoseconds.
42 blocks of code.
[all …]
/Zephyr-latest/lib/posix/options/
DKconfig.mqueue13 int "Maximum number of messages in a POSIX message queue"
16 Mention maximum number of messages in message queue in POSIX compliant
20 int "Maximum number of POSIX message priorities"
23 Maximum number of message priorities supported by the implementation.
26 int "Maximum size of a POSIX message"
29 Mention maximum size of message in bytes.
36 Mention size of message queue name in number of characters.
/Zephyr-latest/drivers/can/
DKconfig.mcp251xfd19 int "Maximum number of queued messages"
23 Defines the array size of transmit callback pointers and semaphores,
24 as well as the number of messages in the TX queue.
27 int "Number of CAN messages in the RX fifo"
31 Defines the number of CAN messages in the RX fifo.
37 Size of the stack used for internal thread which is ran for
44 Thread priority of the interrupt handler. A higher number implies a
49 int "Number of retries during SFR register read"
52 Number of retries during SFR register read if CRC fails.
55 int "Maximum number of concurrent active filters"
[all …]
DKconfig.stm3218 int "Maximum number of standard (11-bit) ID filters"
22 Defines the maximum number of filters with standard ID (11-bit)
25 One standard ID filter with mask occupies 1/2 of the 14 available
28 The following equation determines the maximum total number of
34 int "Maximum number of extended (29-bit) ID filters"
38 Defines the maximum number of filters with extended ID (29-bit)
41 One extended ID filter with mask occupies 1 of the 14 available
44 The following equation determines the maximum total number of
62 int "Maximum number of standard (11-bit) ID filters"
66 Defines the maximum number of filters with standard ID (11-bit)
[all …]
/Zephyr-latest/drivers/mdio/
DKconfig.nxp_enet_qos9 Enable NXP ENET QOS (Quality of Service) MDIO driver.
14 int "Number of times to recheck MDIO transaction status"
17 Number of times that the driver should recheck the status
18 of an MDIO bus transaction before timing out
23 int "Time between rechecks of transaction status (us)"
26 The amount of time in microseconds that the driver should
27 busy wait between checks of the MDIO transaction status.
/Zephyr-latest/subsys/mgmt/osdp/
DKconfig.pd13 In PD mode, number of connected PDs is always 1 and cannot
20 The number of commands that can be queued to a given PD. In CP mode,
21 the queue size is multiplied by number of connected PD so this can grow
29 The 7 least significant bits represent the address of the PD to which
30 the message is directed, or the address of the PD sending the reply.
40 Hexadecimal string representation of the 16 byte OSDP PD Secure
71 Manufacturer's version of this product. Least 8 bits are valid.
102 - 01: PD monitors and reports the state of the circuit without any
104 interpretation of contact state to active/inactive status.
105 - 02: Like 01, plus: The PD accepts configuration of the encoding of the
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dsar_cfg.rst6 Segmentation and reassembly (SAR) provides a way of handling larger upper transport layer messages
7 in a mesh network, with a purpose of enhancing the Bluetooth Mesh throughput. The segmentation and
18 Transport PDU before passing it up the stack. Delivery of a segmented message is acknowledged by the
19 lower transport layer of the receiving node, while an unsegmented message delivery is not
26 message (PDU) size of 384 octets. To configure message size for the Bluetooth Mesh stack, use the
29 * :kconfig:option:`CONFIG_BT_MESH_RX_SEG_MAX` to set the maximum number of segments in an incoming …
30 * :kconfig:option:`CONFIG_BT_MESH_TX_SEG_MAX` to set the maximum number of segments in an outgoing …
37 Incoming and outgoing segmented messages share the same pool for allocation of their segments. This
39 Both incoming and outgoing messages allocate segments at the start of the transaction. The outgoing
42 Keep this in mind when defining the size of the buffers.
[all …]
/Zephyr-latest/drivers/ethernet/eth_nxp_enet_qos/
DKconfig27 int "Number of tx buffer descriptors"
31 Number of TX buffer descriptors.
34 int "Number of rx buffer descriptors"
38 Number of RX buffer descriptors.
46 Value of 0 will allow the driver to wait unlimited time.
49 int "Size of ENET QOS RX thread stack"
52 Size in bytes of the ENET QOS RX thread stack.
55 int "Cooperative priority of the ENET QOS RX thread"
58 Cooperative priority of the ENET QOS RX thread
/Zephyr-latest/drivers/dma/
DKconfig.mcux_lpc14 int "Number of DMA descriptors to use"
17 Each DMA descriptor can be used to transfer (1024*width) bytes of data.
18 Increase or decrease this value depending on the max number of data
22 int "Number of DMA channels to allocate memory for in driver"
27 space by setting this value to suit its needs. The meaning of the value
28 is "total number of unique DMA channels ever expected to be used, maximum
29 out of all DMA controllers". A value of 0 (default) means to allocate
30 as many channel data structures as the maximum number of DMA channels
/Zephyr-latest/subsys/net/l2/ethernet/lldp/
DKconfig28 Interval between transmissions of LLDPDUs during normal
30 please refer to section 9.2.5.7 of the LLDP spec.
33 int "Multiplier of Tx Interval to result on Time to Live value"
37 This value (msgTxHold) is used as a multiplier of
40 refer to section 9.2.5.6 of the LLDP spec.
43 # End of LLDPDU TLV CONFIG
46 bool "End of LLDPDU TLV"
49 Tells whether LLDPDU packet will have marker at the end of the packet.
60 Please refer to section 8.5.2.2 of the 802.1AB for more info.
78 Byte 0 of the MAC address.
[all …]
/Zephyr-latest/drivers/entropy/
DKconfig.cc13xx_cc26xx19 int "Number of bytes in the entropy pool"
22 The size in bytes of the buffer used to store entropy generated by the
23 hardware. Should be a power of two for high performance.
26 int "Number of samples to generate entropy"
30 The number of samples used to generate entropy. The time required to
31 generate 64 bits of entropy is determined by the number of FROs enabled,
39 The number of samples detected with repeating patterns before an alarm
43 int "Threshold for the number of FROs automatically shut down"
47 The number of FROs allowed to be shutdown before the driver attempts to
/Zephyr-latest/tests/benchmarks/thread_metric/
DKconfig12 The Thread-Metric benchmark suite consists of eight RTOS tests.
13 These tests measure the total number of RTOS events that can be
19 The baseline basic benchmark consists of a single thread that counts
20 the number of times it performs a set of calculations. This number
27 of equal priority that yield to each other and increment counters
28 on each context switch. The sum total of the counters is reported
40 takes that semaphore. The sum total of the counters is reported
49 The interrupt preemption benchmark counts the number of times that
51 of a thread. The total number of context switches is reported every
57 The memory allocation benchmark counts the number of times a thread
[all …]
/Zephyr-latest/doc/security/
Dsecurity-overview.rst9 This document outlines the steps of the Zephyr Security Subcommittee towards a
12 the key ideas of the security process and outlines which documents need
20 We begin with an overview of the Zephyr development process, which
23 In subsequent sections, the individual parts of the process are treated
31 to enforce them. A security architecture of the system and
34 validity of the threat models are checked by code reviews.
38 3. **Security Certification:** Defines the certifiable part of the
50 This document is a guideline for the development of a security process
52 Committee. It provides an overview of the Zephyr security process for
65 with security implications. The effects on security of not implementing
[all …]
/Zephyr-latest/doc/kernel/usermode/
Dmpu_stack_objects.rst13 has implications for the placement of stacks in memory, as well as the
14 implementation of other features such as stack protection and userspace. The
23 to memory. Memory protection units can provide this kind of support.
24 The MPU provides a fixed number of regions. Each region contains information
31 address) of the stack.
36 During stack creation, a set of constraints are enforced on the allocation of
37 memory. These constraints include determining the alignment of the stack and
38 the correct sizing of the stack. During linking of the binary, these
41 The main source of the memory constraints is the MPU design for the SoC. The
43 can include alignment of beginning and end addresses, sizes of allocations,
[all …]
/Zephyr-latest/doc/services/device_mgmt/smp_groups/
Dsmp_group_10.rst14 | ``0`` | Count of supported groups |
23 Count of supported groups command
26 Count of supported groups returns the total number of MCUmgr command groups that a device supports.
28 Count of supported groups request
44 Count of supported groups response
47 Count of supported groups response header fields:
58 CBOR data of successful response:
66 In case of error the CBOR data takes the form:
95 | "count" | contains the total number of supported MCUmgr groups on the device. |
97 | "err" -> "group" | :c:enum:`mcumgr_group_t` group of the group-based error code. Only |
[all …]
/Zephyr-latest/doc/safety/
Dsafety_requirements.rst9 The safety committee leads the effort to gather requirements that reflect the **actual** state of
11 approach of the project's safety effort. The goal is **NOT** to create new requirements to request
21 Below are the guidelines for the requirements repository and the expectations of the safety
27 The scope of the requirements covers the KERNEL functionalities.
32 Maintain consistency across all requirements. The language and choice of words shall be consistent.
35 Levels of requirements in the repository
39 System requirements describe the behaviour of the Zephyr RTOS (= the system here).
40 They describe the functionality of the Zephyr RTOS from a very high-level perspective,
41 without going into details of the functionality itself.
42 The purpose of the system requirements is to get an overview of the currently implemented features
[all …]

12345678910>>...106