Lines Matching full:which

9 MCUmgr functions by having group handlers which identify a group of functions relating to a
10 specific management area, which is addressed with a 16-bit identification value,
12 corresponding group ID values. The group ID is included in SMP headers to identify which
13 group a command belongs to, there is also an 8-bit command ID which identifies the function of
42 The purpose of the header file is to provide defines which can be used by the MCUmgr handler
51 responses (which have unique error codes per group as opposed to the legacy SMP version 1 error
55 :c:enumerator:`MGMT_GROUP_ID_PERUSER`, which is the start group ID for user-defined groups, note
62 The purpose of the header file is to provide defines which can be used by the MCUmgr handler
70 This sets up a single event which application (or module) code can register for to receive a
71 callback when the function handler is executed, which allows the flow of the handler to be
73 :c:enumerator:`MGMT_EVT_GRP_USER_CUSTOM_START`, which is the start event ID for user-defined groups,
89 The above code creates 2 function handlers, ``test`` which supports read requests and takes 2
90 required parameters, and ``other`` which supports write requests and takes 1 optional parameter,
103 The purpose of the Kconfig file is to provide options which users can enable or change relating
169 This is an example file which can be used to load the Kconfig and CMake files from the root of the
181 This is an example CMakeLists.txt file which loads the CMake file for the example MCUmgr handler,
191 This is an example Kconfig file which loads the Kconfig file for the example MCUmgr handler, and
201 There is a demonstration project which includes configuration for both application and zephyr
202 module-MCUmgr handlers which can be used as a basis for created your own in