Lines Matching +full:driver +full:- +full:bar

19 for supervisor-mode access only.
54 .. code-block:: c
60 simply expands to 'static inline'. However to the post-build
88 .. code-block:: c
203 Exception to above is passing 64-bit parameters on 32-bit systems, in which case
204 64-bit parameters are split into lower and higher part and passed as two consecutive
224 a return type of API prototype declaration. This means that 64-bit value may
225 not be directly returned, from a system call to its wrapper, on 32-bit systems.
226 To solve the problem the automatically generated wrapper function defines 64-bit
231 The problem does not exist on 64-bit systems which are able to return 64-bit
318 * :c:macro:`K_SYSCALL_DRIVER_OP()` checks at runtime if a driver
321   that are automatically generated for every driver subsystem.  For
322   instance, to validate the GPIO driver, one could use the
326   a provided pointer is a valid instance of a specific device driver, that
327   the calling thread has permissions on it, and that the driver has been
329   is stored within the driver instance and ensuring that it matches the
330   provided value, which should be the address of the specific driver's
358 .. code-block:: c
394 .. code-block:: c
412 .. code-block:: c
431 .. code-block:: c
447 .. code-block:: c
449     struct bar {
455         struct bar *bar_left;
456         struct bar *bar_right;
463         struct bar bar_right_copy;
464         struct bar bar_left_copy;
468                                 sizeof(struct bar)));
471                                 sizeof(struct bar)));
483 reported, to a caller, with returning the ``-ENOMEM`` . The ``K_OOPS()``
486 .. code-block:: c
488     struct bar {
494         struct bar *bar_list; /* array of struct bar of size count */
501         struct bar *bar_list_copy;
509             return -EINVAL;
517             return -ENOMEM;
550 .. code-block:: c
579    of reasons: missing driver API, bad kernel object pointer, wrong kernel
584    invoking :c:func:`z_thread_malloc()`, should propagate ``-ENOMEM`` to the
597    be exposed as system calls. Some driver subsystem APIs may take optional
608 * :c:func:`k_thread_join()` and :c:func:`k_thread_abort()` are no-ops if
610   initialization bit pulls double-duty to indicate whether a thread is