Home
last modified time | relevance | path

Searched +full:least +full:- +full:specific (Results 1 – 25 of 202) sorted by relevance

123456789

/Zephyr-latest/dts/bindings/mtd/
Datmel,at25.yaml2 # SPDX-License-Identifier: Apache-2.0
11 - Microchip AT25xxx
12 - ST M95xxx
15 width, and timeout) available from the datasheet of the specific EEPROM. The compatible string for
16 these can list the specific EEPROM vendor and model along with the vendor EEPROM family as long as
17 the least-specific compatible entry is "atmel,at25".
29 address-width = <16>;
30 spi-max-frequency = <DT_FREQ_M(20)>;
37 include: ["atmel,at2x-base.yaml", spi-device.yaml]
Datmel,at24.yaml3 # SPDX-License-Identifier: Apache-2.0
12 - Microchip AT24xxx
13 - ST M24xxx
16 width, and timeout) available from the datasheet of the specific EEPROM. The compatible string for
17 these can list the specific EEPROM vendor and model along with the vendor EEPROM family as long as
18 the least-specific compatible entry is "atmel,at24".
24 clock-frequency = <I2C_BITRATE_FAST>;
31 address-width = <16>;
38 include: ["atmel,at2x-base.yaml", i2c-device.yaml]
/Zephyr-latest/drivers/ethernet/
DKconfig.sam_gmac4 # SPDX-License-Identifier: Apache-2.0
25 DT_ETH_SAM_GMAC_NQ := $(dt_node_int_prop_int,$(DT_ETH_SAM_GMAC_PATH),num-queues)
39 bool "Force all traffic to be routed through a specific queue"
44 traffic to be routed through a specific hardware queue. With this enabled
70 at least one complete Ethernet frame. SAM ETH driver will always allocate
74 fit at least two Ethernet frames: one being received by the GMAC module
/Zephyr-latest/doc/security/
Dsecure-coding.rst6 Traditionally, microcontroller-based systems have not placed much
12 the internet, or at least to other devices (that may themselves have
40 vulnerability knowledge that at least one of the primary developers
46 documentation about how security-sensitive issues are handled by the
60 - **Open design** as a design guideline incorporates the maxim that
62 widespread use. Instead of relying on secret, custom-tailored
66 - **Economy of mechanism** specifies that the underlying design of a
71 - **Complete mediation** requires that each access to every object and
75 - **Fail-safe defaults** defines that access is restricted by default
76 and permitted only in specific conditions defined by the system
[all …]
Dsecurity-overview.rst1 .. _security-overview:
14 documents are created, this document is a top-level overview and entry
32 relevant sub-modules is created, threats are identified, and
43 .. figure:: media/security-process-steps.png
64 noted in RFC-2119, "These terms are frequently used to specify behavior
98 - **Security** **Functionality** with a focus on cryptographic
104 - **Quality Assurance** is driven by using a development process that
111 - **Execution Protection** including thread separation, stack and
132 APIs for vendor specific cryptographic IPs in both hardware and software
164 - Verifying correct functionality of the implementation
[all …]
/Zephyr-latest/doc/project/
Dworking_groups.rst8 serve as focused teams dedicated to specific technical areas, initiatives, or
17 - Each Working group (WG) shall determine its own membership eligibility, in
19 - Each working group shall have a team of members who are actively involved
20 in its activities and decision-making processes.
21 - It is expected that WG membership shall be **open to all** Zephyr project
24 - All TSC members are eligible to join a working group as members, part of
26 - The minimal number of members may vary depending on the complexity of the
28 - A working group should aim to have at least five to seven members to
30 - The structure of each working group within the Zephyr Project should be
32 optimal size of a working group can vary depending on the specific context and
[all …]
Dproject_roles.rst51 (https://github.com/zephyrproject-rtos/zephyr/blob/main/CODE_OF_CONDUCT.md)
54 ….github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permiss…
102 not follow the :ref:`expectations <reviewer-expectations>` and the guidelines
171 :ref:`expectations <reviewer-expectations>` from reviewers and seek reviews
175 * Responsibility to re-assign a pull request if they are the original submitter
200 .. _release-engineering-team:
237 time-zones).
243 A *Maintainer* responsible for driving a specific release to
245 project for this specific release.
254 …stone (M3, see `program management overview <https://wiki.zephyrproject.org/Program-Management>`_.)
[all …]
/Zephyr-latest/doc/
Dglossary.rst16 The set of user-supplied files that the Zephyr build system uses
18 It can contain application-specific code, kernel configuration settings,
19 and at least one CMakeLists.txt file.
25 if it does not require any board-specific capabilities.
32 fully-linked binary.
53 specified by the build system can be over-ridden by the application,
57 The human-readable name of a :term:`board`. Uniquely and descriptively
114 high-priority conditions that require interrupting the current code
118 The set of Zephyr-supplied files that implement the Zephyr kernel,
132 least one :term:`CPU cluster` (in turn with at least one :term:`CPU core`),
[all …]
/Zephyr-latest/subsys/mgmt/mcumgr/transport/
DKconfig2 # Copyright Nordic Semiconductor ASA 2020-2022. All rights reserved.
3 # SPDX-License-Identifier: Apache-2.0
11 # MCUMGR_TRANSPORT_ -- general transport options;
12 # MCUMGR_TRANSPORT_WORKQUEUE -- for workqueue configuration;
13 # MCUMGR_TRANSPORT_NETBUF -- for Net Buf related configuration.
47 MCUMGR_TRANSPORT_NETBUF_SIZE >= transport-specific-MTU + transport-overhead
49 at least MCUMGR_GRP_SHELL_BACKEND_DUMMY_BUF_SIZE + 32.
74 module-str = mcumgr_transport
/Zephyr-latest/doc/connectivity/networking/conn_mgr/
Dmain.rst6 … aim to allow applications to monitor and control connectivity (access to IP-capable networks) wit…
8 …ssociation and monitor Internet access, and avoid excessive use of technology-specific boilerplate.
10 …ly support several very different connectivity technologies (for example, Wi-Fi and LTE) with a si…
27 :figclass: align-center
42 * The iface is admin-up
44 …* This means the iface has been instructed to become operational-up (ready for use). This is done …
46 * The iface is oper-up
51 * The iface has at least one assigned IP address
70 When at least one iface is ready, the :c:macro:`NET_EVENT_L4_CONNECTED` :ref:`network management <n…
72 …unready without firing additional events, so long as there always remains at least one ready iface.
[all …]
/Zephyr-latest/dts/bindings/gpio/
Datmel-xplained-pro-header.yaml2 # SPDX-License-Identifier: Apache-2.0
22 All MCU boards have to implement at least PWR, EXT1, EXT2 (on medium and
25 or application specific headers.
28 https://www.microchip.com/development-tools/xplained-boards
29 …http://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-42091-Atmel-Xplained-Pro-Hardware-Developmen…
37 0 ADC(+) 3 4 ADC(-) 1
39 4 PWM(+) 7 8 PWM(-) 5
47 compatible: "atmel-xplained-pro-header"
49 include: [gpio-nexus.yaml, base.yaml]
/Zephyr-latest/doc/develop/languages/c/
Dindex.rst6 C is a general-purpose low-level programming language that is widely used for
17 standard. Applications must return zero (0) from main. All non-zero return
25 Zephyr does not target a specific version of the C standards; however, the
33 * fixed-width integer types (``[u]intN_t`` in ``<stdint.h>``)
40 C11) such as the type-generic expressions using the ``_Generic`` keyword. For
42 processor for Zephyr, makes use of the C11 type-generic expressions, and this
47 least the C11 standard for developing with Zephyr. It is, however, important to
50 the standards, in which case it will be necessary to use a more up-to-date
100 functions (for example, :c:func:`sbrk`) implemented in :file:`libc-hooks.c`.
102 * maintain the architecture- and memory region-specific alignment requirements
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dcsip.rst12 The client will typically be a resource-rich device, such as a smartphone
19 :code:`BT_MAX_CONN` shall be at least 3.
43 .. code-block:: console
45 csip_set_coordinator --help
46 csip_set_coordinator - Bluetooth CSIP_SET_COORDINATOR shell commands
53 lock :Lock specific member [member_index]
54 release :Release specific member [member_index]
55 lock_get :Get the lock value of the specific member and instance
63 -----
65 .. code-block:: console
[all …]
/Zephyr-latest/include/zephyr/
Dtoolchain.h2 * Copyright (c) 2010-2014, Wind River Systems, Inc.
4 * SPDX-License-Identifier: Apache-2.0
9 * @brief Macros to abstract toolchain specific capabilities
12 * utilize toolchain specific attributes and/or pragmas.
20 * @brief Check if the compiler supports the built-in function \a x.
30 * on the toolchain-specific headers to define HAS_BUILTIN_x for the builtins
37 /* This include line exists for off-tree definitions of compilers,
38 * and therefore this header is not meant to exist in-tree
128 * @brief Begin of block to ignore -Wshadow.
139 * @brief End of block to ignore -Wshadow.
[all …]
/Zephyr-latest/doc/build/dts/
Dbindings-upstream.rst1 .. _dt-writing-bindings:
21 Zephyr aims for devicetree :ref:`dt-source-compatibility`. Therefore, if there
24 justify any Zephyr-specific divergences.
28 - There is an existing binding in the mainline Linux kernel. See
32 - Your hardware vendor provides an official binding outside of the Linux
48 https://docs.kernel.org/devicetree/bindings/writing-bindings.html
55 - For example, a binding for compatible ``vnd,foo`` must be named ``vnd,foo.yaml``.
56 - If the binding is bus-specific, you can append the bus to the file name;
57 for example, if the binding YAML has ``on-bus: bar``, you may name the file
58 ``vnd,foo-bar.yaml``.
[all …]
/Zephyr-latest/arch/x86/zefi/
DREADME.txt5 (NOT a "zephyr.strip" intended for grub/multiboot loading -- we need
16 relocatable, and cannot be placed at specific locations in memory.
18 appropriate locations at startup, clear any zero-filled (BSS, etc...)
32 The code and link environment here is non-obvious. The simple rules
45 Linux toolchain. EFI binaries are relocatable PE-COFF files --
50 independent code. Non-static global variables and function addresses
52 time by a system binary (ld-linux.so). But there is no ld-linux.so in
57 via the x86_64 RIP-relative addressing mode and doesn't rely on any
59 the compiler (not the linker) knows a-priori will never be in
63 You might ask: why build a position-independent executable in the
[all …]
/Zephyr-latest/modules/hal_nordic/nrfx/
Dnrfx_glue.h4 * SPDX-License-Identifier: Apache-2.0
34 //------------------------------------------------------------------------------
58 //------------------------------------------------------------------------------
61 * @brief Macro for setting the priority of a specific IRQ.
71 * @brief Macro for enabling a specific IRQ.
78 * @brief Macro for checking if a specific IRQ is enabled.
88 * @brief Macro for disabling a specific IRQ.
95 * @brief Macro for setting a specific IRQ as pending.
106 * @brief Macro for clearing the pending status of a specific IRQ.
117 * @brief Macro for checking the pending status of a specific IRQ.
[all …]
/Zephyr-latest/include/zephyr/drivers/usb_c/
Dtcpci_priv.h3 * SPDX-License-Identifier: Apache-2.0
8 * @brief Helper functions to use by the TCPCI-compliant drivers
10 * This file contains generic TCPCI functions that may be used by the drivers to TCPCI-compliant
11 * devices that want to implement vendor-specific functionality without the need to reimplement the
38 * If the TCPC driver contain any vendor-specific registers, it may override the TCPCI dump_std_reg
45 * @brief Function to read the 8-bit register of TCPCI device
55 * @brief Function to write a value to the 8-bit register of TCPCI device
65 * @brief Function to read and update part of the 8-bit register of TCPCI device
77 * @brief Function to read the 16-bit register of TCPCI device
87 * @brief Function to write a value to the 16-bit register of TCPCI device
[all …]
/Zephyr-latest/doc/_extensions/zephyr/
Dhtml_redirects.py1 # Copyright 2018-2019 Espressif Systems (Shanghai) PTE LTD
3 # SPDX-License-Identifier: Apache-2.0
9 # http://www.apache.org/licenses/LICENSE-2.0
14 # See the License for the specific language governing permissions and
24 # Adapted from ideas in https://tech.signavio.com/2017/managing-sphinx-redirects
35 <meta http-equiv="refresh" content="0; url=$NEWURL" />
39 if (id && (/^[a-zA-Z\:\/0-9\_\-\.]+$/.test(id))) {
56 app.connect('build-finished', create_redirect_pages)
58 # Since we're just setting up a build-finished hook, which runs
74 # check that new_url is a valid docname, or if not that it is at least
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dhealth_srv.h8 * SPDX-License-Identifier: Apache-2.0
32 * vendor. Vendor specific faults should be interpreted in the context
37 * All faults shall be associated with at least one Company ID,
39 * specific fault values are used.
67 * vendor. Vendor specific faults should be interpreted in the context
96 /** @brief Run a self-test.
98 * The Health server may support up to 256 self-tests for each Company
99 * ID. The behavior for all test IDs are vendor specific, and should be
121 * also help identify the specific element the server is in.
/Zephyr-latest/tests/benchmarks/thread_metric/
Dthread_metric_readme.txt1 Thread-Metric RTOS Test Suite
4 1. Thread-Metric Test Suite
6 The Thread-Metric test suite consists of 8 distinct RTOS
9 that can be processed during a specific timer interval. A 30
22 voluntarily release control to each other in a round-robin fashion.
41 highest priority thread - starting the whole process over once again.
75 This test consists of a thread allocating a 128-byte block and
81 A few minor modifications have been made to the Thread-Metric source
84 2.1. tm_main() -> main()
92 than that used by the original Thread-Metric code. These functions
[all …]
/Zephyr-latest/arch/xtensa/
DKconfig4 # SPDX-License-Identifier: Apache-2.0
32 the core-isa.h file. This replaces the previous scheme
62 A design trick on multi-core hardware is to map memory twice
71 This specifies which 512M region (0-7, as defined by the Xtensa
79 region (0-7) contains the "uncached" mapping.
91 bool "Use Xtensa specific arch_spin_relax() with more NOPs"
103 Specify the number of NOPs in Xtensa specific
126 # Selected when at least one XTENSA_HIFIn version has been configured
161 bool "Xtensa exceptions and interrupts cannot be pre-empted"
164 pre-empting low priority interrupts and exceptions.
[all …]
/Zephyr-latest/doc/services/ipc/ipc_service/
Dipc_service.rst29 Endpoint prioritization and multi-instance ability highly depend on the backend
42 DT-compatible configuration that is used to configure the interface at boot
48 * Data exchange using the no-copy API.
64 .. code-block:: c
102 Data exchange using the no-copy API
105 If the backend supports the no-copy API you can use it to directly write and
110 .. code-block:: c
166 subsets of features for specific use cases.
168 The backend must support at least the following:
170 * The init-time creation of instances.
[all …]
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/lll/
Dlll_df_types.h4 * SPDX-License-Identifier: Apache-2.0
68 #define RSSI_DBM_TO_DECI_DBM(x) (-(x) * 10)
70 * It is not defined by Bluetooth Core specification. This is the vendor specific value.
146 /* Stores information if the RX configuration was set at least once.
177 /* Stores information if the TX configuration was set at least once.
/Zephyr-latest/subsys/mgmt/mcumgr/smp/
DKconfig2 # Copyright Nordic Semiconductor ASA 2020-2022. All rights reserved.
3 # SPDX-License-Identifier: Apache-2.0
11 # MCUMGR_SMP_ -- for general SMP options;
12 # MCUMGR_SMP_CBOR -- for CBOR encoding specific options;
23 data directly to main map, creating sub-maps instead so
77 Commands that provide CBOR payload require at least 1 level,

123456789