Home
last modified time | relevance | path

Searched refs:struct (Results 26 – 50 of 232) sorted by relevance

12345678910

/Zephyr-latest/scripts/coredump/gdbstubs/arch/
Drisc_v.py9 import struct
72 tu = struct.unpack(self.ARCH_DATA_BLK_STRUCT, arch_data_blk)
74 tu = struct.unpack(self.ARCH_DATA_BLK_STRUCT_2, arch_data_blk)
105 bval = struct.pack(reg_fmt, self.registers[idx])
Darm_cortex_m.py9 import struct
58 tu = struct.unpack(self.ARCH_DATA_BLK_STRUCT, arch_data_blk)
60 tu = struct.unpack(self.ARCH_DATA_BLK_STRUCT_V2, arch_data_blk)
92 bval = struct.pack(reg_fmt, registers[idx])
145 tu = struct.unpack("<IIIIIIII", barray)
Dx86_64.py9 import struct
123 if len(arch_data_blk) != struct.calcsize(arch_data_blk_struct):
129 tu = struct.unpack(arch_data_blk_struct, arch_data_blk)
185 bval = struct.pack(reg_fmt, self.registers[idx])
Darm64.py9 import struct
74 tu = struct.unpack(self.ARCH_DATA_BLK_STRUCT, arch_data_blk)
115 bval = struct.pack(reg_fmt, self.registers[idx])
Dx86.py9 import struct
101 tu = struct.unpack(self.ARCH_DATA_BLK_STRUCT, arch_data_blk)
141 bval = struct.pack(reg_fmt, self.registers[idx])
/Zephyr-latest/doc/hardware/peripherals/
Dmspi.rst43 * Check :c:struct:`mspi_cfg` against hardware's own capabilities to prevent
52 * Configure the hardware using :c:struct:`mspi_cfg` and possibly more
55 * Usually, the :c:struct:`mspi_cfg` is filled from device tree and contains
68 * The :c:struct:`mspi_dev_cfg` should be filled by device tree and helper macro
71 * The controller driver should then validate the members of :c:struct:`mspi_dev_cfg`
77 :c:struct:`mspi_dev_id`.
93 The transceive request is of type :c:struct:`mspi_xfer` which allows dynamic change to
98 :c:struct:`mspi_xfer_packet`. However, it is up to the controller implementation
170 With :c:struct:`mspi_dev_id` defined as collection of the device index and CE GPIO from
177 software controlled device switching by saving and updating :c:struct:`mspi_dev_cfg` and
[all …]
/Zephyr-latest/include/zephyr/linker/
Dintlist.ld12 * struct {
14 * struct _isr_list isrs[]; <- Usually of smaller size than num_vectors
19 * an appropriate number of instances of struct _isr_list. See
/Zephyr-latest/doc/kernel/memory_management/
Dshared_multi_heap.rst21 2. Each memory region encoded in a :c:struct:`shared_multi_heap_region`
31 // Fill the struct with the data for cacheable memory
32 struct shared_multi_heap_region cacheable_r0 = {
42 struct shared_multi_heap_region cacheable_r1 = {
51 struct shared_multi_heap_region non_cacheable_r2 = {
/Zephyr-latest/scripts/coredump/coredump_parser/
Delf_parser.py8 import struct
165 …self.kernel_thread_info_size_t_size = struct.unpack('B', self.elf.stream.read(size_t_size_symbol['…
175 …self.kernel_thread_info_num_offsets = struct.unpack(struct_format, self.elf.stream.read(num_offset…
185 …self.kernel_thread_info_offsets = struct.unpack(array_format, self.elf.stream.read(info_offsets_sy…
/Zephyr-latest/arch/x86/
Dgen_gdt.py40 import struct
81 return struct.pack(GDT_PD_FMT, size, addr, 0)
124 return struct.pack(GDT_ENT_FMT, limit_lo, base_lo, base_mid,
142 return struct.pack(GDT_ENT_FMT, limit_lo, base_lo, base_mid,
/Zephyr-latest/doc/build/dts/
Dzephyr-user-node.rst79 const struct device *my_device =
93 const struct device *my_devices[] = {
115 You can convert the pin defined in ``signal-gpios`` to a ``struct
124 const struct gpio_dt_spec signal =
133 (See :c:struct:`gpio_dt_spec`, :c:macro:`GPIO_DT_SPEC_GET`, and
Dhowtos.rst56 Get a struct device from a devicetree node
60 :ref:`struct device <device_model_api>` corresponding to a devicetree node.
62 For example, with this devicetree fragment, you might want the struct device
108 const struct device *const uart_dev = DEVICE_DT_GET(MY_SERIAL);
126 ``struct device`` by combining :c:func:`device_get_binding` with the device
132 const struct device *uart_dev = device_get_binding(dev_name);
146 const struct device *const uart_dev = DEVICE_DT_GET(MY_SERIAL);
390 enable the driver via Kconfig and :ref:`get the struct device <dt-get-device>`
399 ``struct device`` for each ``status = "okay"`` devicetree node with a
418 a ``struct device`` for each one. There are two options for instantiating each
[all …]
/Zephyr-latest/soc/espressif/common/
DKconfig.flash19 given by ``chip_drv`` member of the chip struct. This adds support for variant
27 given by ``chip_drv`` member of the chip struct. This adds support for variant
35 directly given by ``chip_drv`` member of the chip struct. If you are using Wrover
48 given by ``chip_drv`` member of the chip struct. This adds support for variant
56 given by ``chip_drv`` member of the chip struct. This adds support for variant
64 given by ``chip_drv`` member of the chip struct. This adds support for variant
73 given by ``chip_drv`` member of the chip struct. This adds support for variant
/Zephyr-latest/doc/connectivity/networking/api/
Dcoap_client.rst27 static struct coap_client;
28 struct coap_client_request req = { 0 };
40 /* Sock is a file descriptor referencing a socket, address is the sockaddr struct for the
89 static struct coap_client;
90 struct coap_client_request req = { 0 };
93 static struct coap_client_option block2_option;
Dnet_l2.rst15 through a :c:struct:`net_if` declared in
20 :zephyr_file:`include/zephyr/net/net_l2.h` as :c:struct:`net_l2`.
41 into a :c:struct:`net_pkt`, will push this buffer to the network
71 - The driver_api pointer must point to a valid :c:struct:`net_if_api`
77 instantiate a unique :c:struct:`net_if` related to the created
92 :c:struct:`net_pkt` and should be allocated through
118 - It requires a dedicated device driver API: :c:struct:`ieee802154_radio_api`,
119 which overloads :c:struct:`net_if_api`. This is because 802.15.4 L2 needs more from the device
135 :c:struct:`ieee802154_radio_api` requires a tx function pointer which differs
136 from the :c:struct:`net_if_api` send function pointer. Zephyr's native
[all …]
Dmqtt_sn.rst46 static struct mqtt_sn_client client;
55 static struct mqtt_sn_transport tp;
61 static void evt_cb(struct mqtt_sn_client *client,
62 const struct mqtt_sn_evt *evt)
77 struct mqtt_sn_data client_id = MQTT_SN_DATA_STRING_LITERAL("ZEPHYR");
78 struct sockaddr_in gateway = {0};
83 mqtt_sn_transport_udp_init(&tp, (struct sockaddr*)&gateway, sizeof((gateway)));
111 Note that :c:func:`mqtt_sn_input` is a non-blocking function, if the transport struct contains a
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dchannels.rst16 A channel is specified in Zephyr using a :c:struct:`sensor_chan_spec` which is a
19 historical since the introduction of :c:struct:`sensor_chan_spec` for Zephyr 3.7.
Dattributes.rst23 const struct device *accel_dev = DEVICE_DT_GET(DT_ALIAS(accel0));
24 struct sensor_value accel_sample_rate;
/Zephyr-latest/soc/mediatek/mt8xxx/
Dmtk_adsp_load.py8 import struct
62 regs = struct.unpack(f">{2 * len(rnames)}Q", readfile(path + "reg"))
64 for i, ph in enumerate(struct.unpack(">II", readfile(path + "memory-region"))):
67 if os.path.exists(phf) and struct.unpack(">I", readfile(phf))[0] == ph:
68 (addr, sz) = struct.unpack(">QQ", readfile(rmem + "reg"))
218 return struct.unpack("<I", bstr)[0]
Dgen_img.py4 import struct
93 of.write(struct.pack("<III", FILE_MAGIC, len(sram), boot_vector))
/Zephyr-latest/doc/kernel/data_structures/
Dindex.rst13 data structures. The "node" data is the only struct used by the
17 user-defined struct. Macros are provided to retrieve a user struct
/Zephyr-latest/scripts/build/
Duf2conv.py7 import struct
28 w = struct.unpack("<II", buf[0:8])
53 hd = struct.unpack(b"<IIIIIIII", block[0:32])
137 hd = struct.pack(b"<IIIIIIII",
142 block = hd + chunk + datapadding + struct.pack(b"<I", UF2_MAGIC_END)
157 hd = struct.pack("<IIIIIIII",
163 hd += struct.pack("<I", UF2_MAGIC_END)
/Zephyr-latest/doc/develop/optimizations/
Dtools.rst239 struct _dnode * head; /* 0 4 */
240 struct _dnode * next; /* 0 4 */
244 struct _dnode {
246 struct _dnode * head; /* 0 4 */
247 struct _dnode * next; /* 0 4 */
250 struct _dnode * tail; /* 4 4 */
251 struct _dnode * prev; /* 4 4 */
260 struct _dnode * tail; /* 0 4 */
261 struct _dnode * prev; /* 0 4 */
/Zephyr-latest/doc/hardware/peripherals/can/
Dcontroller.rst132 struct can_frame frame = {
138 const struct device *const can_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_canbus));
155 void tx_callback(const struct device *dev, int error, void *user_data)
164 int send_function(const struct device *can_dev)
166 struct can_frame frame = {
190 void rx_callback_function(const struct device *dev, struct can_frame *frame, void *user_data)
205 const struct can_filter my_filter = {
211 const struct device *const can_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_canbus));
228 const struct can_filter my_filter = {
234 struct can_frame rx_frame;
[all …]
/Zephyr-latest/doc/kernel/services/data_passing/
Dmessage_queues.rst73 A message queue is defined using a variable of type :c:struct:`k_msgq`.
81 struct data_item_type {
87 char my_msgq_buffer[10 * sizeof(struct data_item_type)];
88 struct k_msgq my_msgq;
90 k_msgq_init(&my_msgq, my_msgq_buffer, sizeof(struct data_item_type), 10);
100 K_MSGQ_DEFINE(my_msgq, sizeof(struct data_item_type), 10, 1);
117 struct data_item_type data;
147 struct data_item_type data;
171 struct data_item_type data;

12345678910