Searched full:specific (Results 1 – 25 of 955) sorted by relevance
12345678910>>...39
| /Zephyr-Core-2.7.6/include/drivers/interrupt_controller/ |
| D | sam0_eic.h | 33 * @brief Acquire an EIC interrupt for specific port and pin combination
35 * This acquires the EIC interrupt for a specific port and pin combination,
51 * @brief Release the EIC interrupt for a specific port and pin combination
53 * Release the EIC configuration for a specific port and pin combination.
63 * @brief Enable the EIC interrupt for a specific port and pin combination
71 * @brief Disable the EIC interrupt for a specific port and pin combination
|
| /Zephyr-Core-2.7.6/drivers/interrupt_controller/ |
| D | intc_plic.c | 39 * @brief Enable a riscv PLIC-specific interrupt line
41 * This routine enables a RISCV PLIC-specific interrupt line.
62 * @brief Disable a riscv PLIC-specific interrupt line
64 * This routine disables a RISCV PLIC-specific interrupt line.
85 * @brief Check if a riscv PLIC-specific interrupt line is enabled
87 * This routine checks if a RISCV PLIC-specific interrupt line is enabled.
102 * @brief Set priority of a riscv PLIC-specific interrupt line
104 * This routine set the priority of a RISCV PLIC-specific interrupt line.
124 * @brief Get riscv PLIC-specific interrupt line causing an interrupt
126 * This routine returns the RISCV PLIC-specific interrupt line causing an
|
| /Zephyr-Core-2.7.6/lib/posix/ |
| D | pthread_key.c | 15 * @brief Create a key for thread-specific data
41 * @brief Delete a key for thread-specific data
53 /* Delete thread-specific elements associated with the key */ in pthread_key_delete()
73 * @brief Associate a thread-specific value with a key
99 * associate thread specific data in pthread_setspecific()
114 /* Associate thread specific data, initialize new key */ in pthread_setspecific()
135 * @brief Get the thread-specific value associated with the key
|
| /Zephyr-Core-2.7.6/include/pm/ |
| D | device_runtime.h | 37 * @param dev Pointer to device structure of the specific device driver
50 * @param dev Pointer to device structure of the specific device driver
64 * @param dev Pointer to device structure of the specific device driver
81 * @param dev Pointer to device structure of the specific device driver
97 * @param dev Pointer to device structure of the specific device driver
114 * @param dev Pointer to device structure of the specific device driver
128 * @param dev Pointer to device structure of the specific device driver
|
| /Zephyr-Core-2.7.6/drivers/ethernet/ |
| D | phy_xlnx_gem.h | 21 /* PHY register addresses & constants that are not vendor-specific */
25 /* PHY registers & constants -> Marvell Alaska specific */
126 * @brief Vendor-specific PHY management function pointer table struct
128 * Contains the PHY management function pointers for a specific PHY
142 * Contains the PHY management function pointers for a specific PHY
152 /* PHY identification function -> generic, not vendor-specific */
|
| /Zephyr-Core-2.7.6/doc/guides/debug_tools/ |
| D | coredump.rst | 203 architecture-specific block, and multiple memory blocks. All numbers in
245 Architecture-specific Block
248 The architecture-specific block contains the byte stream of data specific
251 .. list-table:: Architecture-specific Block
260 - ``A`` to indiciate this is a architecture-specific block.
264 architecture specific block parser.
268 for target data. The format of the byte stream is specific to
272 - Contains target architecture specific data.
309 The architecture-specific block is target specific and requires new
326 #. Parse the architecture-specific block from
|
| /Zephyr-Core-2.7.6/samples/boards/ |
| D | boards.rst | 1 .. _board-specific-samples:
3 Board-specific samples
|
| /Zephyr-Core-2.7.6/drivers/modem/ |
| D | Kconfig.quectel-bg9x | 38 context. This value is specific to the network provider and may
46 context. This value is specific to the network provider and may
54 context. This value is specific to the network provider and may
|
| /Zephyr-Core-2.7.6/doc/reference/peripherals/ |
| D | rtc.rst | 9 This is a placeholder for API specific to real-time clocks. Currently
11 device-specific API for counters with real-time support.
|
| /Zephyr-Core-2.7.6/doc/guides/dts/ |
| D | design.rst | 8 specific examples about how they impact Zephyr's source code, and areas where
53 Zephyr's binding language *semantics* can support Zephyr-specific attributes,
54 but shall not express Zephyr-specific relationships.
65 Zephyr-specific features. Its purpose is to provide a higher-level view of the
69 :file:`edtlib.py`, contains Zephyr-specific knowledge and features.
|
| /Zephyr-Core-2.7.6/include/drivers/ |
| D | hwinfo.h | 55 * based on vendor-specific assumptions of byte order. It should express the
64 * @retval any negative value on driver specific errors.
88 * @retval any negative value on driver specific errors.
101 * @retval any negative value on driver specific errors.
116 * @retval any negative value on driver specific errors.
|
| /Zephyr-Core-2.7.6/subsys/mgmt/osdp/ |
| D | CMakeLists.txt | 9 # PD mode specific sources
12 # CP mode specific sources
|
| /Zephyr-Core-2.7.6/include/sys/ |
| D | arch_interface.h | 12 * call architecture-specific API so will have the prototypes for the
13 * architecture-specific APIs here. Architecture APIs that aren't used in this
16 * The set of architecture-specific APIs used internally by public macros and
55 * Obtain the current cycle count, in units that are hardware-specific
193 * @param data context parameter, implementation specific
200 * This starts and initializes a specific CPU. The main thread on startup is
209 * others for design-specific processing.
289 * Arch-specific hook to install a dynamic interrupt.
295 * @param flags Arch-specific IRQ configuration flag
378 * @defgroup arch-smp Architecture-specific SMP APIs
[all …]
|
| /Zephyr-Core-2.7.6/tests/drivers/i2c/i2c_slave_api/ |
| D | README.txt | 9 controllers on a common bus. The test is supported by a test-specific
23 * Use API specific to the simulated EEPROM to pre-populate the simulated
24 devices with device-specific content.
|
| /Zephyr-Core-2.7.6/include/drivers/misc/ |
| D | README | 4 Zephyr Device Drivers API. Such drivers have only device-specific API providing
16 rendering. These operations are controlled by a vendor-specific API designed
|
| /Zephyr-Core-2.7.6/include/portability/ |
| D | cmsis_os.h | 40 * See the License for the specific language governing permissions and
133 // >>> the following data type definitions may shall adapted towards a specific RTOS
136 /// \note CAN BE CHANGED: \b os_thread_cb is implementation specific in every CMSIS-RTOS.
140 /// \note CAN BE CHANGED: \b os_timer_cb is implementation specific in every CMSIS-RTOS.
144 /// \note CAN BE CHANGED: \b os_mutex_cb is implementation specific in every CMSIS-RTOS.
148 /// \note CAN BE CHANGED: \b os_semaphore_cb is implementation specific in every CMSIS-RTOS.
152 /// \note CAN BE CHANGED: \b os_pool_cb is implementation specific in every CMSIS-RTOS.
156 /// \note CAN BE CHANGED: \b os_messageQ_cb is implementation specific in every CMSIS-RTOS.
160 /// \note CAN BE CHANGED: \b os_mailQ_cb is implementation specific in every CMSIS-RTOS.
165 /// \note CAN BE CHANGED: \b os_thread_def is implementation specific in every CMSIS-RTOS.
[all …]
|
| /Zephyr-Core-2.7.6/arch/arm64/core/ |
| D | irq_init.c | 23 * is invoked for SoC-specific interrupt system initialisation.
28 /* Invoke SoC-specific interrupt controller initialisation */ in z_arm64_interrupt_init()
|
| /Zephyr-Core-2.7.6/include/ |
| D | toolchain.h | 9 * @brief Macros to abstract toolchain specific capabilities
12 * utilize toolchain specific attributes and/or pragmas.
30 * on the toolchain-specific headers to define HAS_BUILTIN_x for the builtins
|
| /Zephyr-Core-2.7.6/subsys/net/lib/mqtt/ |
| D | mqtt_os.h | 9 * @brief MQTT Client depends on certain OS specific functionality. The needed
14 * in the OS. OS specific port of the interface shall be provided.
60 /**@brief Acquire lock on the module specific mutex, if any.
73 /**@brief Release the lock on the module specific mutex, if any.
|
| /Zephyr-Core-2.7.6/tests/bluetooth/bsim_bt/edtt_ble_test_app/gatt_test_app/src/gatt/ |
| D | service_c_2_1.c | 164 * with a specific ATT error code.
186 * with a specific ATT error code.
209 * with a specific ATT error code.
237 * with a specific ATT error code.
260 * with a specific ATT error code.
290 * with a specific ATT error code.
319 * with a specific ATT error code.
342 * with a specific ATT error code.
372 * with a specific ATT error code.
401 * with a specific ATT error code.
[all …]
|
| D | service_f_1.c | 99 * with a specific ATT error code.
121 * with a specific ATT error code.
144 * with a specific ATT error code.
172 * with a specific ATT error code.
196 * with a specific ATT error code.
227 * with a specific ATT error code.
251 * with a specific ATT error code.
282 * with a specific ATT error code.
309 * with a specific ATT error code.
336 * with a specific ATT error code.
|
| /Zephyr-Core-2.7.6/tests/drivers/gpio/gpio_basic_api/ |
| D | README.txt | 6 identified through a test-specific devicetree binding in the `dts/`
7 subdirectory, implemented for specific boards by overlay files in the
|
| /Zephyr-Core-2.7.6/kernel/include/ |
| D | kernel_arch_interface.h | 11 * Not all architecture-specific defines are here, APIs that are used
35 * Architecture-specific implementation of busy-waiting
50 /** Handle arch-specific logic for setting up new threads
52 * The stack and arch-specific thread state variables must be set up
214 * @defgroup arch-pm Architecture-specific power management APIs
225 * @defgroup arch-irq Architecture-specific IRQ APIs
243 * @defgroup arch-mmu Architecture-specific memory-mapping APIs
558 * Architecture-specific kernel initialization hook
561 * architecture-specific setup before the rest of the kernel is brought up.
574 * @defgroup arch-coredump Architecture-specific core dump APIs
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/api/ |
| D | design_guidelines.rst | 23 * The next parameter(s) should be additional information specific to the
35 specific to the code that also defines the callback function. In those
93 * Where code specific to the feature is isolated in a source file that
98 * Where code specific to the feature is part of a source file that has
99 other content the feature-specific code should be conditionally
|
| /Zephyr-Core-2.7.6/include/posix/ |
| D | pthread_key.h | 25 * specific data for the key
36 /* Key and thread specific data passed to pthread_setspecific() */
|
12345678910>>...39
