Lines Matching refs:be
12 that provides control over if the action should be allowed or not. An example
13 of this is with the fs_mgmt group, whereby file access can be gated, the
24 The base callback/notification system can be enabled using
28 be selected by enabling the Kconfig's for the required callbacks (see
30 :c:type:`mgmt_cb` type definition can then be declared and registered by
35 With the system enabled, a basic handler can be set up and defined in
66 event, which will be called after a MCUmgr command has been processed and
68 :kconfig:option:`CONFIG_MCUMGR_SMP_COMMAND_STATUS_HOOKS` be enabled to receive
71 Multiple callbacks can be setup to use a single function as a common callback,
72 and many different functions can be used for each event by registering each
73 group once, or all notifications for a whole group can be enabled by using one
76 handlers, events can be combined that are in the same group only, for example
77 5 img_mgmt callbacks can be setup with a single registration call, but to also
78 setup a callback for an os_mgmt callback, this must be done as a separate
109 Events can be selected by enabling their corresponding Kconfig option:
133 an example is the fs_mgmt access hook which allows for access to files to be
135 by a handler will be returned to the MCUmgr client.
189 :c:enumerator:`MGMT_EVT_OP_FS_MGMT_FILE_ACCESS` event, which will be called
191 the file should be allowed or not, note that this requires that
192 :kconfig:option:`CONFIG_MCUMGR_GRP_FS_FILE_ACCESS_HOOK` be enabled to receive
194 Two types of errors can be returned, the ``rc`` parameter can be set to an
196 can be returned, or a group error code (introduced with version 2 of the MCUmgr
197 protocol) can be set by setting the ``group`` value to the group and ``rc``
203 To add a callback to a MCUmgr command, :c:func:`mgmt_callback_notify` can be
205 (which can be modified by handlers). If no data needs to be passed back,
206 ``NULL`` can be used instead, and size of the data set to 0.
272 If no response is required for the callback, the function call be called and
281 or earlier, then it will need to be migrated to the new system. To migrate
282 code, the following callback registration functions will need to be migrated
284 :kconfig:option:`CONFIG_MCUMGR_MGMT_NOTIFICATION_HOOKS` will need to be set to
292 :kconfig:option:`CONFIG_MCUMGR_SMP_COMMAND_STATUS_HOOKS` needs to be set.
296 the action or false to deny, a MCUmgr result code needs to be returned,
299 (:c:enumerator:`MGMT_ERR_EACCESSDENIED` can be used for an access denied
300 error). :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_STATUS_HOOKS` needs to be
310 :kconfig:option:`CONFIG_MCUMGR_GRP_IMG_STATUS_HOOKS` needs to be set.
314 allow the action or false to deny, a MCUmgr result code needs to be
317 (:c:enumerator:`MGMT_ERR_EACCESSDENIED` can be used for an access denied
319 be set.
322 true to allow the action or false to deny, a MCUmgr result code needs to be
325 (:c:enumerator:`MGMT_ERR_EACCESSDENIED` can be used for an access denied
327 be set.