Searched refs:Manager (Results 1 – 25 of 47) sorted by relevance
12
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.vim | 9 bool "TI Vectored Interrupt Manager"
13 The TI Vectored Interrupt Manager provides hardware assistance for prioritizing
|
| /Zephyr-latest/boards/intel/socfpga/agilex5_socdk/ |
| D | intel_socfpga_agilex5_socdk_defconfig | 25 # Enable Clock Manager
31 # Reset Manager
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | index.rst | 3 Connection Manager
|
| D | main.rst | 6 Connection Manager is a collection of optional Zephyr features that aim to allow applications to mo…
8 Using Connection Manager, applications can use a single abstract API to control network association…
12 Applications can also use Connection Manager to generically manage and use multiple connectivity te…
17 Connection Manager is split into the following two subsystems:
26 :alt: A simplified view of how Connection Manager integrates with Zephyr and the application.
29 A simplified view of how Connection Manager integrates with Zephyr and the application.
78 … Connection Manager also fires the following more specific ``CONNECTED`` / ``DISCONNECTED`` events:
114 /* Call this before Connection Manager monitoring initializes */
136 …nectivity events, you should register your listener(s) before Connection Manager monitoring initia…
181 Applications can request that ifaces be ignored by Connection Manager by calling :c:func:`conn_mgr_…
[all …]
|
| D | implementation.rst | 47 :alt: A detailed view of how Connection Manager integrates with Zephyr and the application.
50 A detailed view of how Connection Manager integrates with Zephyr and the application.
181 Rather than implement all features centrally, Connection Manager relies on each connectivity implem…
183 This approach allows Connection Manager to remain lean, and allows each connectivity implementation…
315 Connection Manager provides a context pointer to each binding.
343 In other words, it should be possible to configure builds that include Connectivity Manager, as wel…
391 …work management <net_mgmt_interface>` events are not triggered automatically by Connection Manager.
436 …y trigger a new connection attempts if that timeout is shorter than the Connection Manager timeout.
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr.rst | 63 …| nRF Connect Device Manager: |br| | | …
65 …| <https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/>`_ | | …
67 …| <https://github.com/NordicSemiconductor/IOS-nRF-Connect-Device-Manager>`_ | | …
102 …| nRF Connect Device Manager: |br| | iOS, |br| |…
104 …| <https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/>`_ | |…
106 …| <https://github.com/NordicSemiconductor/IOS-nRF-Connect-Device-Manager>`_ | |…
|
| D | smp_protocol.rst | 14 it is unrelated to SMP in Bluetooth (Security Manager Protocol), but there
|
| /Zephyr-latest/boards/intel/socfpga/agilex_socdk/ |
| D | intel_socfpga_agilex_socdk_defconfig | 19 # Enable Clock Manager
|
| /Zephyr-latest/boards/quicklogic/quick_feather/ |
| D | quick_feather_defconfig | 14 # EOS S3 Configuration Manager copies software from external flash to MCU
|
| /Zephyr-latest/samples/subsys/sip_svc/ |
| D | README.rst | 4 Use the SiP SVC subsystem to interact with the Secure Device Manager on Intel Agilex SoC FPGA.
10 performs a voltage value query from Secure Device Manager in Intel Agilex
19 intel Agilex SoC FPGA query the voltage levels in Secure Device Manager.
|
| /Zephyr-latest/boards/quicklogic/qomu/ |
| D | qomu_defconfig | 15 # EOS S3 Configuration Manager copies software from external flash to MCU
|
| /Zephyr-latest/tests/kernel/timer/timer_behavior/pytest/ |
| D | saleae_logic2.py | 21 with automation.Manager.connect(address=address, port=port) as manager:
|
| /Zephyr-latest/boards/efinix/titanium_ti60_f225/doc/ |
| D | index.rst | 9 Using the Efinity IP Manager, you can configure the SoC to include only the peripherals that you re…
|
| /Zephyr-latest/lib/utils/ |
| D | Kconfig | 30 bool "On-Off Manager"
|
| /Zephyr-latest/modules/hal_silabs/simplicity_sdk/ |
| D | CMakeLists.txt | 164 # Power Manager
178 # HFXO Manager
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | brg_cfg.rst | 28 A node implementing the Bridge Configuration Client model can act as a *Configuration Manager* for
70 The Bridge Configuration Client (or Configuration Manager) can enable or disable the Subnet Bridge
|
| D | blob_cli.rst | 65 address, instead of being sent individually to each Target node. Mesh Manager must ensure that all
|
| /Zephyr-latest/drivers/flash/ |
| D | CMakeLists.txt | 100 # BLE is enabled. Use implementation over Flash Manager for coexistence with RF activities
|
| /Zephyr-latest/doc/project/ |
| D | project_roles.rst | 147 Release Engineering Team member, Release Manager, but are no longer engaged
208 the Release Manager role based on a defined cadence and selection process.
240 Release Manager
249 A Release Manager is a member of the Release Engineering team and has
|
| D | release_process.rst | 173 - Release Manager
182 - Release Manager
188 - Release Manager
192 - Release Manager
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 23 On-Off Manager
|
| /Zephyr-latest/samples/drivers/clock_control_litex/ |
| D | README.rst | 11 The driver uses Mixed Mode Clock Manager (MMCM) module to generate up to 7 clocks with defined phas…
|
| /Zephyr-latest/boards/nxp/imx95_evk/doc/ |
| D | index.rst | 224 The i.MX System Manager (SM) is used on i.MX95, which is an application that runs on
233 multiple elements required, like ELE+V2X firmware, System Manager, TCM OEI, Cortex-M7
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 407 bool "Security Manager Protocol support"
412 This option enables support for the Security Manager Protocol
626 The Paring Failed command of the Security Manager Protocol cannot be
664 bool "Security Manager Debug Mode"
666 This option places Security Manager in a Debug Mode. In this mode
714 With this option enabled, the Security Manager will set MITM option in
|
| /Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
| D | autopts-win10.rst | 103 In Device Manager find COM port of your nrf board. In my case it is COM3.
|
12
