| /Zephyr-latest/tests/posix/headers/ |
| D | testcase.yaml | 11 portability.posix.headers.with_posix_api:
14 portability.posix.headers.without_posix_api:
17 portability.posix.headers.minimal.with_posix_api:
20 portability.posix.headers.minimal.without_posix_api:
23 portability.posix.headers.picolibc.with_posix_api:
29 portability.posix.headers.picolibc.without_posix_api:
35 portability.posix.headers.newlib.with_posix_api:
41 portability.posix.headers.newlib.without_posix_api:
46 portability.posix.headers.arcmwdtlib.with_posix_api:
51 portability.posix.headers.arcmwdtlib.without_posix_api:
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | Kconfig | 83 processing HPACK compressed headers. This effectively limits the
108 application wishes to access headers of a greater length.
116 (applies to response headers only, not request headers). The default
117 value is sufficient for the standard headers included with a response,
119 additional response headers.
122 bool "Allow capturing HTTP headers for application use"
124 This setting enables the HTTP server to capture selected headers that have
128 int "Size of buffer for capturing HTTP headers for application use"
134 HTTP headers for later use by the application.
137 int "Maximum number of HTTP headers to be captured for application use"
[all …]
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | atmel-xplained-pro-header.yaml | 5 GPIO pins exposed on Atmel Xplained Pro headers.
8 one or more headers and can share pins. The extension headers are given
12 standard extension headers that have a predefined position according to the
24 on the board design. EXT4 to EXT7 can either be standard extension headers
25 or application specific headers.
|
| D | sparkfun-pro-micro-header.yaml | 5 GPIO pins exposed on Sparkfun Pro Micro (and compatible devices) headers.
7 The Sparkfun Pro Micro layout provides two headers, along opposite
32 A graphical datasheet of the headers can be seen here:
|
| D | ti,boosterpack-header.yaml | 7 GPIO pins exposed as BoosterPack headers on TI LaunchPads.
10 20 pin variant has two 10 x 1 pin headers and the 40 pin variant has two
11 10 x 2 pin headers. Both variants are compatible and stackable.
|
| D | renesas,mipi-header.yaml | 5 GPIO pins exposed on Renesas MIPI lcd display headers.
7 The Renesas MIPI lcd display layout provides 2 columns of 13 pins headers
|
| D | raspberrypi,pico-header.yaml | 5 GPIO pins exposed on Raspberry Pi Pico headers.
7 The Raspberry Pi Pico layout provides 2 columns of 20 pins headers
|
| D | adafruit-feather-header.yaml | 5 GPIO pins exposed on Adafruit Feather headers.
7 The Feather layout provides two headers, one each along
|
| D | seeed-xiao-header.yaml | 7 GPIO pins exposed on Seeeduino Xiao (and compatible devices) headers.
9 The Seeeeduino Xiao layout provides two headers, along opposite
|
| D | arduino-nano-header-r3.yaml | 5 GPIO pins exposed on Arduino Nano (R3) headers.
7 The Arduino Nano layout provides two headers on opposite edges of the board.
|
| D | mikro-bus.yaml | 5 GPIO pins exposed on Mikro BUS headers.
7 The Mikro BUS layout provides two headers, aligned on the opposite
|
| D | ambiq-header.yaml | 5 GPIO pins exposed on Ambiq Apollo4p EVB headers
7 The Ambiq Apollo4p EVB layout provides 5x16 and 1x20 pin headers.
|
| D | arduino-header-r3.yaml | 6 GPIO pins exposed on Arduino Uno (R3) headers.
8 The Arduino Uno layout provides four headers, two each along
|
| /Zephyr-latest/doc/services/llext/ |
| D | build.rst | 6 often useful to have access to the headers and compiler flags used by the main
18 needs to export the headers and compiler flags used by the main Zephyr
138 headers and compiler flags used by the main Zephyr application, since they have
139 a direct impact on how Zephyr headers are interpreted and the extension is
151 directory. It's a tarball that contains the headers and compile flags needed
152 to build extensions. The extension developer can then include the headers
167 Compiler flags to add directories containing non-autogenerated headers
172 Compiler flags to add directories containing autogenerated headers to
177 Compiler flags to add all directories containing headers used in the
183 Compiler flags for autogenerated headers that must be included in the
[all …]
|
| /Zephyr-latest/samples/arch/smp/pktqueue/ |
| D | README.rst | 4 Use SMP to process multiple packet headers in parallel.
17 of packet headers is initialized. Each header contains some random data of size
38 The headers then are stored in multiple "sender" queues (the number is defined
47 As soon as all headers in each pair of queues are moved from "sender" to
57 the number of headers in queue (``SIZE_OF_QUEUE``), and
63 This project outputs total time required for processing all packet headers.
79 Each of 2 parallel queues is processed by 3 threads on 2 cores and contain 5000 packet headers.
84 All 20000 packet headers were processed in 89 msec
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | CMakeLists.txt | 5 zephyr_library_include_directories(include/internal) # secure_storage headers
8 # Make the subsystem's PSA Secure Storage API headers available only when it's enabled.
13 # Make the secure_storage headers available to the application only when it's implementing the rele…
|
| /Zephyr-latest/include/zephyr/net/http/ |
| D | server.h | 173 /** @brief Status of captured request headers */
175 HTTP_HEADER_STATUS_OK, /**< All available headers were successfully captured. */
176 HTTP_HEADER_STATUS_DROPPED, /**< One or more headers were dropped due to lack of space. */
190 struct http_header *headers; /**< Array of HTTP request headers */ member
191 size_t header_count; /**< Array length of HTTP request headers */
192 enum http_header_status headers_status; /**< Status of HTTP request headers */
198 const struct http_header *headers; /**< Array of HTTP headers */ member
199 size_t header_count; /**< Length of headers array */
348 /** Flag indicating that headers were sent in the reply. */
365 /** @brief Context for capturing HTTP headers */
[all …]
|
| /Zephyr-latest/subsys/usb/device/class/netusb/ |
| D | CMakeLists.txt | 6 # USB headers
12 # IP headers
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | http_server.rst | 303 * The ``headers``, ``header_count`` and ``headers_status`` fields pass request
304 headers to the application, if
313 * The ``headers`` and ``header_count`` fields can be used for the application to
314 send any arbitrary HTTP headers. If not populated, only Transfer-Encoding and
323 Headers and/or response codes may only be sent in the first populated
371 Accessing request headers
374 The application can register an interest in any specific HTTP request headers.
375 These headers are then stored for each incoming request, and can be accessed
376 from within a dynamic resource callback. Request headers are only included in
383 Then the application can register headers to be captured, and read the values
[all …]
|
| /Zephyr-latest/boards/shields/arduino_uno_click/doc/ |
| D | index.rst | 9 The Arduino UNO click is an extension to the Arduino UNO R3 headers.
10 It's a simple shield that converts Arduino UNO R3 headers to two mikroBUS
16 Two mikroBUS headers are exposed by the overlay: ``mikrobus_header_1`` and
|
| /Zephyr-latest/samples/arch/smp/pktqueue/src/ |
| D | pktqueue.h | 18 struct phdr_desc *head; /* packet headers are removed from here */
19 struct phdr_desc *tail; /* packet headers are added here*/
|
| D | main.c | 9 /* Amount of parallel processed sender/receiver queues of packet headers */
15 /* Amount of packet headers in a queue */
48 /* Array of packet headers */
49 uint8_t headers[QUEUE_NUM][SIZE_OF_QUEUE][SIZE_OF_HEADER]; variable
63 descriptors[queue_num][i].ptr = (uint8_t *)&headers[queue_num][i]; in init_datagram_queue()
163 " on %d cores and contain %d packet headers.\n", in main()
214 "All %d headers were processed in %d msec\n", in main()
|
| /Zephyr-latest/subsys/net/ip/ |
| D | 6lo.h | 25 * @details After this IPv6 packet and next header(if UDP), headers
49 * @details After this IPv6 packet and next header(if UDP), headers
84 * @details This will do a dry-run on uncompressing the headers.
|
| /Zephyr-latest/soc/nordic/ |
| D | CMakeLists.txt | 15 # Include dt-bindings headers into the build. This lets us validate all required
17 # headers for different SoCs.
|
| D | validate_binding_headers.c | 7 * This file validates definitions found in dt-bindings headers against their
10 * Note: all dt-bindings headers which have been included by DTS in this build
|
