Lines Matching full:some
30 will be declared in some header under ``include/`` or in another
62 The :ref:`parse_syscalls.py` script does some parsing of the function prototype,
63 to determine the data types of its return value and arguments, and has some
141 Declaring an API with :c:macro:`__syscall` causes some code to be generated in
216 Some system calls may have more than six arguments, but number of arguments
245 declared in some C file. There is no prototype needed for implementation
274 made simpler by some macros in :zephyr_file:`include/zephyr/internal/syscall_handler.h`.
312 * :c:macro:`K_SYSCALL_VERIFY_MSG()` does a runtime check of some boolean
335 calling thread. This is done instead of returning some error condition to
391 for some integral value:
421 memory as part of its logic. For example, it could be used to store some
426 Some parameters may be input/output. For instance, it's not uncommon to see APIs
427 which pass in a pointer to some ``size_t`` which is a maximum allowable size,
477 In some cases the amount of data isn't known at compile time or may be too
537 as data captured from some MMIO region, the implementation function must
541 as a block of memory to write to some hardware destination, this data
573 appropriate permissions on the memory buffer or some size calculation
597 be exposed as system calls. Some driver subsystem APIs may take optional
602 #. Some parameter checks are enforced only from user mode. These should be
606 There are some known exceptions to these policies currently in Zephyr: