/Zephyr-Core-3.7.0/subsys/bluetooth/services/ |
D | Kconfig.hrs | 12 prompt "Default permissions used for HRS characteristics" 15 Default permissions for HRS characteristic attributes
|
/Zephyr-Core-3.7.0/subsys/bluetooth/services/ias/ |
D | Kconfig.ias | 13 prompt "Default permissions used for IAS characteristics" 16 Default write permissions for IAS characteristic attributes
|
/Zephyr-Core-3.7.0/doc/kernel/usermode/ |
D | kernelobjects.rst | 27 has sufficient permissions to work with it. 87 permissions on it) the object will be automatically freed. User threads 89 :c:func:`k_object_release`, and their permissions are automatically 94 Because permissions are also used for reference counting, it is important for 95 supervisor threads to acquire permissions on objects they are using even though 122 * A bitfield indicating permissions on that object. All threads have a 140 Supervisor threads can access any kernel object. However, permissions for 144 thread will then run in user mode with any permissions it had been granted 149 same permissions as the parent thread, except the parent thread object. 154 By default, when a user thread is created, it will only have access permissions [all …]
|
D | overview.rst | 114 assign them permissions to kernel objects. In general, all C and header 156 permissions of all kernel objects granted to the parent, except the parent 162 which are expected to rigorously validate access permissions and type of
|
D | syscalls.rst | 269 calling thread has read or write permissions on the provided buffer. 284 has permissions on it, and that the object is initialized. 296 size. The calling thread must have read permissions on the entire buffer. 300 have write permissions. 305 when computing the total size. The calling thread must have read permissions 310 additionally have write permissions. 327 the calling thread has permissions on it, and that the driver has been 573 appropriate permissions on the memory buffer or some size calculation
|
/Zephyr-Core-3.7.0/cmake/compiler/gcc/ |
D | generic.cmake | 24 message(FATAL_ERROR "Executing the below command failed. Are permissions set correctly?
|
/Zephyr-Core-3.7.0/cmake/compiler/xcc/ |
D | generic.cmake | 25 message(FATAL_ERROR "Executing the below command failed. Are permissions set correctly?
|
/Zephyr-Core-3.7.0/drivers/gpio/ |
D | Kconfig.intel | 14 bool "Check permissions before manipulating GPIO"
|
/Zephyr-Core-3.7.0/tests/bluetooth/tester/src/ |
D | btp_gatt.c | 428 uint8_t permissions; member 451 if (ch->permissions & GATT_PERM_READ_AUTHORIZATION) { in alloc_characteristic() 455 if (!(ch->permissions & GATT_PERM_ENC_READ_MASK)) { in alloc_characteristic() 456 ch->permissions |= BT_GATT_PERM_READ; in alloc_characteristic() 460 if (ch->permissions & GATT_PERM_WRITE_AUTHORIZATION) { in alloc_characteristic() 464 if (!(ch->permissions & GATT_PERM_ENC_WRITE_MASK)) { in alloc_characteristic() 465 ch->permissions |= BT_GATT_PERM_WRITE; in alloc_characteristic() 470 ch->permissions |= BT_GATT_PERM_PREPARE_WRITE; in alloc_characteristic() 475 ch->permissions & GATT_PERM_MASK, in alloc_characteristic() 508 cmd_data.permissions = cp->permissions; in add_characteristic() [all …]
|
/Zephyr-Core-3.7.0/samples/modules/tflite-micro/magic_wand/boards/ |
D | litex_vexriscv.overlay | 12 See the License for the specific language governing permissions and
|
/Zephyr-Core-3.7.0/cmake/compiler/armclang/ |
D | generic.cmake | 36 "Are permissions set correctly? '${CMAKE_C_COMPILER} --version' "
|
/Zephyr-Core-3.7.0/boards/infineon/cyw920829m2evk_02/support/ |
D | qspi_config.cfg | 23 # See the License for the specific language governing permissions and
|
/Zephyr-Core-3.7.0/cmake/compiler/arcmwdt/ |
D | generic.cmake | 23 message(FATAL_ERROR "Executing the below command failed. Are permissions set correctly?
|
/Zephyr-Core-3.7.0/tests/bluetooth/tester/src/btp/ |
D | btp_gatt.h | 37 uint8_t permissions; member 48 uint8_t permissions; member
|
/Zephyr-Core-3.7.0/doc/project/ |
D | index.rst | 39 :ref:`project_roles` describes in detail the Zephyr project roles and associated permissions
|
/Zephyr-Core-3.7.0/include/zephyr/arch/x86/intel64/ |
D | linker.ld | 15 * so that the page permissions can be set in the MMU. Without this, 16 * the kernel is just one blob with the same RWX permissions on all RAM
|
/Zephyr-Core-3.7.0/soc/mediatek/mtk_adsp/mt8195_adsp/ |
D | linker.ld | 67 . = ALIGN(4096); /* Switching MPU permissions, align by 4k */
|
/Zephyr-Core-3.7.0/include/zephyr/linker/common-rom/ |
D | common-rom-kernel-devices.ld | 78 /* Build-time assignment of permissions to kernel objects to
|
/Zephyr-Core-3.7.0/subsys/net/lib/lwm2m/ |
D | lwm2m_object.h | 107 #define LWM2M_HAS_PERM(of, p) (((of)->permissions & p) == p) 169 .permissions = LWM2M_PERM_ ## _perm, \ 184 uint8_t permissions; member
|
/Zephyr-Core-3.7.0/ |
D | LICENSE | 24 exercising permissions granted by this License. 151 risks associated with Your exercise of permissions under this License. 200 See the License for the specific language governing permissions and
|
/Zephyr-Core-3.7.0/samples/userspace/prod_consumer/ |
D | README.rst | 22 - Management of permissions for kernel objects and drivers
|
/Zephyr-Core-3.7.0/include/zephyr/arch/x86/ia32/ |
D | linker.ld | 62 * so that the page permissions can be set in the MMU. Without this, 63 * the kernel is just one blob with the same RWX permissions on all RAM
|
/Zephyr-Core-3.7.0/doc/hardware/arch/ |
D | arm_cortex_m.rst | 436 which programs the flash with RWX permissions. If :kconfig:option:`CONFIG_USERSPACE` is 439 RW permissions. That is, an MPU region is utilized to disallow execute permissions on 442 Arm memory map policies, allowing for privileged-only RWX permissions on SRAM). 444 ``zephyr,memory-attr`` defining the MPU permissions for the memory region.
|
/Zephyr-Core-3.7.0/samples/modules/tflite-micro/magic_wand/train/ |
D | train_magic_wand_model.ipynb | 16 "See the License for the specific language governing permissions and\n",
|
/Zephyr-Core-3.7.0/arch/ |
D | Kconfig | 299 which has significantly restricted permissions and must interact 379 int "Bytes to use when tracking object thread permissions" 384 thread permissions for that object. This controls the size of the 880 bool "Assign appropriate permissions to kernel areas in SRAM" 906 access permissions set, typically read/write/execute. It may be desirable
|