| /Zephyr-Core-2.7.6/subsys/logging/ |
| D | log_core.c | 381 struct log_msg_ids structure; in z_log_vprintk() member
396 log_generic(src_level_union.structure, fmt, ap, in z_log_vprintk()
411 msg_finalize(msg, src_level_union.structure); in z_log_vprintk()
976 struct log_msg_ids structure; in z_vrfy_z_log_string_from_user() member
983 level = src_level_union.structure.level; in z_vrfy_z_log_string_from_user()
984 domain_id = src_level_union.structure.domain_id; in z_vrfy_z_log_string_from_user()
985 source_id = src_level_union.structure.source_id; in z_vrfy_z_log_string_from_user()
1017 log_string_sync(src_level_union.structure, "%s", str); in z_vrfy_z_log_string_from_user()
1024 msg_finalize(msg, src_level_union.structure); in z_vrfy_z_log_string_from_user()
1028 log_1("%s", (log_arg_t)str, src_level_union.structure); in z_vrfy_z_log_string_from_user()
[all …]
|
| /Zephyr-Core-2.7.6/lib/util/getopt/ |
| D | README | 26 its state. In my implementation I put those variables in a structure
27 and a pointer to that structure is passed as an additional parameter
29 own getopt function state structure which it uses.
|
| /Zephyr-Core-2.7.6/subsys/emul/spi/ |
| D | CMakeLists.txt | 4 # subdirectories to match the drivers/ structure.
|
| /Zephyr-Core-2.7.6/doc/reference/api/ |
| D | design_guidelines.rst | 14 configuration structure. The following policies should be followed when
32 allowed when the callback itself was provided through a structure that
33 will be embedded in another structure. An example of such a case is
34 :c:type:`gpio_callback`, normally defined within a data structure
49 timer is embedded in a structure reachable from
84 structure or union declaration. This reduces memory use for
|
| /Zephyr-Core-2.7.6/subsys/emul/i2c/ |
| D | CMakeLists.txt | 4 # subdirectories to match the drivers/ structure.
|
| /Zephyr-Core-2.7.6/doc/reference/storage/flash_map/ |
| D | flash_map.rst | 14 The ``flash_area`` structure contains the name of the flash device the
16 to get the corresponding :c:struct:`device` structure which can be read and
30 structure. The ID number for a flash area can be obtained from a human-readable
80 To get a pointer to the flash area structure and do something with it starting
|
| /Zephyr-Core-2.7.6/doc/reference/iterable_sections/ |
| D | index.rst | 13 Iterable section elements are typically used by defining the data structure and
35 Then the linker has to be setup to place the place the structure in a
|
| /Zephyr-Core-2.7.6/doc/reference/kernel/data_passing/ |
| D | stacks.rst | 104 /* save address of each data structure in a stack */
115 can dynamically allocate an unused data structure.
116 When the data structure is no longer required, the thread must push
117 its address back on the stack to allow the data structure to be reused.
|
| /Zephyr-Core-2.7.6/samples/subsys/mgmt/mcumgr/smp_svr/ |
| D | CMakeLists.txt | 8 # This provides a basic application structure suitable for communication using
|
| /Zephyr-Core-2.7.6/doc/reference/usb/ |
| D | uds.rst | 49 * USB Device configuration structure
57 :start-after: usb.rst config structure start
58 :end-before: usb.rst config structure end
69 USB Device configuration structure:
|
| /Zephyr-Core-2.7.6/doc/reference/networking/ |
| D | mqtt.rst | 33 To create an MQTT client, a client context structure and buffers need to be
46 independently. Additionally, a structure for MQTT Broker address information
47 is needed. This structure must be accessible throughout the lifespan
70 The client context structure needs to be initialized and set up before it can be
|
| /Zephyr-Core-2.7.6/doc/reference/bluetooth/mesh/ |
| D | cfg_srv.rst | 12 The :c:struct:`bt_mesh_cfg_srv` structure has been deprecated. The initial
|
| D | access.rst | 23 The node's element and model structure is specified in the node composition
44 The full opcode list must be passed to the model structure in the composition
84 * By setting up a :c:struct:`bt_mesh_model_pub` structure and calling
|
| /Zephyr-Core-2.7.6/include/arch/x86/ |
| D | pagetables.ld | 22 /* Top-level paging structure is the last thing in this section */
|
| /Zephyr-Core-2.7.6/drivers/adc/ |
| D | Kconfig.nrfx | 26 needs a dedicated structure in RAM that stores the ADC settings
|
| /Zephyr-Core-2.7.6/include/linker/ |
| D | intlist.ld | 10 * What we create here is a data structure:
|
| /Zephyr-Core-2.7.6/doc/development_process/ |
| D | documentation.rst | 51 needs to follow a new structure to avoid confusion. Using a consistent naming
52 scheme and following a well-defined structure we will be able to group this
|
| /Zephyr-Core-2.7.6/arch/riscv/ |
| D | Kconfig | 64 - SOC_ESF_MEMBERS: structure component declarations to
71 - SOC_ESF_INIT: structure contents initializer for struct soc_esf
|
| /Zephyr-Core-2.7.6/samples/drivers/clock_control_litex/ |
| D | README.rst | 41 …rol API <clock_control_api>` function ``clock_control_on()`` and a LiteX driver specific structure:
46 | To change clock parameter it is needed to cast a pointer to structure ``litex_clk_setup`` onto ``…
|
| /Zephyr-Core-2.7.6/samples/sensor/max17262/ |
| D | README.rst | 23 For more info about the node structure see
|
| /Zephyr-Core-2.7.6/samples/net/wpanusb/ |
| D | wpan-radio-spec.txt | 10 Packet structure
|
| /Zephyr-Core-2.7.6/doc/reference/data_structures/ |
| D | mpsc_pbuf.rst | 89 User header structure must start with internal header:
103 Configuration structure contains buffer details, configuration flags and
|
| D | rbtree.rst | 29 represented as a :c:struct:`rbnode` structure which exists in
30 user-managed memory, typically embedded within the the data structure
113 These properties, of a balanced tree data structure that works with
|
| /Zephyr-Core-2.7.6/doc/reference/peripherals/ |
| D | sensor.rst | 62 of the structure accordingly.
93 :c:struct:`sensor_trigger` and a handler function. The structure contains the
|
| /Zephyr-Core-2.7.6/ |
| D | .uncrustify.cfg | 74 align_struct_init_span = 0 # align stuff in a structure init '= { }'
|
