Home
last modified time | relevance | path

Searched full:responsibility (Results 1 – 25 of 62) sorted by relevance

123

/Zephyr-Core-3.6.0/doc/project/
Dproject_roles.rst44 * Responsibility to abide by decisions, once made. They are welcome to
46 * Responsibility for issues and bugs introduced by one’s own contributions.
47 * Responsibility to respect the rules of the community.
48 * Responsibility to provide constructive advice whenever participating in
50 * Responsibility to follow the project’s code of conduct
86 * Responsibility to participate in the feature development process.
87 * Responsibility to review relevant code changes within reasonable time.
88 * Responsibility to ensure the quality of the code to expected levels.
89 * Responsibility to participate in community discussions.
90 * Responsibility to mentor new contributors when appropriate
[all …]
/Zephyr-Core-3.6.0/subsys/mgmt/mcumgr/transport/include/mgmt/mcumgr/transport/
Dsmp_reassembly.h21 * Note: for efficiency there is no NULL check on @p smpt pointer and it is caller's responsibility
40 * responsibility to make sure these are not NULL. Also @p len should not be 0 as there is no
61 * Note: for efficiency there is no NULL check on @p smpt pointer and it is caller's responsibility
76 * in which case it is users responsibility to use the user data, passed with the packet, to notify
82 * Note: for efficiency there is no NULL check on @p smpt pointer and it is caller's responsibility
98 * Note: for efficiency there is no NULL check on @p smpt pointer and it is caller's responsibility
111 * Note: for efficiency there is no NULL check on @p smpt pointer and it is caller's responsibility
/Zephyr-Core-3.6.0/subsys/lorawan/nvm/
DKconfig14 If this configuration is used, it is the responsibility of the
/Zephyr-Core-3.6.0/subsys/bluetooth/common/
Dbt_str.h9 * It is the responsibility of the user of this function to copy the information
/Zephyr-Core-3.6.0/dts/bindings/base/
Dpower.yaml14 entirely the responsibility of the device driver.
/Zephyr-Core-3.6.0/subsys/bluetooth/audio/
DKconfig.ascs57 responsibility, but this is a failsafe to ensure that ISO channel is
/Zephyr-Core-3.6.0/soc/xtensa/intel_adsp/common/include/
Dsoc.h38 * responsibility. This function will hang if the other CPU fails to
/Zephyr-Core-3.6.0/
DCODE_OF_CONDUCT.md23 * Accepting responsibility and apologizing to those affected by our mistakes,
46 Community leaders have the right and responsibility to remove, edit, or reject
/Zephyr-Core-3.6.0/doc/services/pm/
Dpower_domain.rst18 When a power domain turns itself on or off, it is the responsibility of the
179 It is responsibility of driver or the application to set the domain as
Dsystem.rst12 It is an application responsibility to set up a wake up event. A wake up event
Ddevice.rst87 state is tracked by the subsystem, it is the responsibility of each device driver
238 It is responsibility of driver or the application to do any additional
/Zephyr-Core-3.6.0/include/zephyr/mgmt/mcumgr/transport/
Dserial.h54 * net_buf containing the decoded request. It is the caller's responsibility
/Zephyr-Core-3.6.0/arch/arm/
DKconfig35 assumes responsibility for handling the NVIC.
/Zephyr-Core-3.6.0/include/zephyr/arch/arc/v2/mpu/
Darc_core_mpu.h22 * of operations and attributes for each MPU and it is responsibility of the
/Zephyr-Core-3.6.0/include/zephyr/drivers/clock_control/
Dnrf_clock_control.h142 * Function does not perform any validation. It is the caller responsibility to
/Zephyr-Core-3.6.0/dts/bindings/clock/
Dst,stm32wba-rcc.yaml52 It is device driver's responsibility to query and use clock source information in
Dst,stm32-rcc.yaml57 It is peripheral driver's responsibility to query and use clock source information in
/Zephyr-Core-3.6.0/subsys/usb/usb_c/
Dusbc_tc_src_states.c276 * responsibility to the Sink through USBPD VCONN_Swap messaging in tc_attached_src_run()
287 * VCONN responsibility to the Sink through USBPD VCONN_Swap in tc_attached_src_run()
/Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/mesh/
Dcore.rst55 This moves the responsibility of storing RPL to the user application and
/Zephyr-Core-3.6.0/doc/contribute/
Dcontributor_expectations.rst107 responsibility to verify.
226 The assignee has the responsibility to document the reasoning for dismissing
/Zephyr-Core-3.6.0/drivers/interrupt_controller/
Dintc_dw_ace.c43 * interrupt sources. Responsibility for these mask bits is left with
/Zephyr-Core-3.6.0/kernel/
DKconfig.vm31 1. It is the architecture's responsibility to transition the
/Zephyr-Core-3.6.0/include/zephyr/sys/
Dmulti_heap.h32 * This is a user-provided functions whose responsibility is selecting
/Zephyr-Core-3.6.0/include/zephyr/logging/
Dlog_output.h83 * its responsibility to mark them as dropped or discarded by returning
/Zephyr-Core-3.6.0/subsys/bluetooth/host/
DKconfig.gatt86 When disabled, it is the application's responsibility to call

123