Searched refs:amount (Results 76 – 100 of 153) sorted by relevance
1234567
/Zephyr-latest/subsys/lorawan/services/ |
D | Kconfig | 152 This parameter specifies the maximum amount of packet loss (in
|
/Zephyr-latest/boards/phytec/phyboard_nash/doc/ |
D | index.rst | 13 amount of resources in more specific designs.
|
/Zephyr-latest/doc/services/pm/ |
D | power_domain.rst | 54 significant amount of static current leakage that can't be controlled
|
D | system.rst | 12 The kernel requests an amount of time it would like to suspend, then the PM subsystem decides
|
/Zephyr-latest/drivers/clock_control/ |
D | Kconfig.nrf | 110 this amount since the last calibration.
|
/Zephyr-latest/tests/subsys/logging/log_blocking/ |
D | REAME.md | 88 advised to avoid this for any non-negligible amount of time.
|
/Zephyr-latest/samples/bluetooth/channel_sounding/ |
D | README.rst | 27 This limits the amount of data that can be processed at once to about 512 bytes from each device,
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | l2cap.c | 888 size_t amount, in bt_test_l2cap_data_pull_spy() argument 894 size_t amount, in l2cap_data_pull() argument 901 bt_test_l2cap_data_pull_spy(conn, lechan, amount, length); in l2cap_data_pull() 962 bool last_frag = amount >= lechan->_pdu_remaining; in l2cap_data_pull() 1011 if (lechan->_pdu_remaining > amount) { in l2cap_data_pull() 1012 lechan->_pdu_remaining -= amount; in l2cap_data_pull()
|
/Zephyr-latest/doc/kernel/services/data_passing/ |
D | pipes.rst | 84 the producer thread waits for a specified amount of time.
|
/Zephyr-latest/samples/drivers/counter/maxim_ds3231/ |
D | README.rst | 110 faster than civil time on this device. This amount of error is expected
|
/Zephyr-latest/subsys/net/ip/ |
D | Kconfig.ipv6 | 97 support, please increase amount of RX data buffers so that larger 278 int "Max amount of failed DAD attempts"
|
D | Kconfig.ipv4 | 129 fragmentation support, please increase amount of RX data buffers so
|
D | Kconfig | 338 net-shell require also some smaller amount of memory. 818 Each RX buffer will occupy smallish amount of memory. 826 Each TX buffer will occupy smallish amount of memory. 835 header (sizeof(struct net_buf)) amount of data. 843 header (sizeof(struct net_buf)) amount of data.
|
/Zephyr-latest/subsys/logging/ |
D | Kconfig.formatting | 132 this option is causing interrupts locking for significant amount of
|
/Zephyr-latest/lib/os/ |
D | Kconfig.cbprintf | 123 size by a small amount.
|
/Zephyr-latest/samples/kernel/metairq_dispatch/ |
D | README.rst | 17 Each message has a random (and non-trivial) amount of processing that
|
/Zephyr-latest/lib/posix/options/ |
D | Kconfig.pthread | 133 This is the default amount of space to reserve at the overflow end of a
|
/Zephyr-latest/doc/build/dts/ |
D | phandles.rst | 252 single devicetree property, even though the amount of metadata you need to 277 kinds of resources at the same time. The node describes the amount of metadata
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_pkt.rst | 139 One can increase the amount of buffer space allocated by calling 187 exact amount of data that must be read or written.
|
/Zephyr-latest/arch/xtensa/core/ |
D | README_WINDOWS.rst | 29 themselves. Instead they place the rotation amount in two places
|
/Zephyr-latest/dts/arm/nxp/ |
D | nxp_rt1010.dtsi | 299 * The pre-div and post-div are one less than the actual divide-by amount.
|
/Zephyr-latest/drivers/wifi/nrf_wifi/ |
D | Kconfig.nrfwifi | 474 beyond SP, the power consumption increases depending on the amount 791 whether to stay in PS (for a lower amount of buffered data) or exit PS (for a higher 792 amount of buffered data).
|
/Zephyr-latest/subsys/bluetooth/common/ |
D | Kconfig | 42 Controller. This determines the maximum amount of data packets the 114 can assume that the Host has infinite amount of buffers.
|
/Zephyr-latest/boards/arm/mps2/doc/ |
D | mps2_an521.rst | 92 if required, at the cost of reducing the amount of code memory available on 96 ``mps2/an521/cpu1``), care needs to be taken with the amount of code or
|
/Zephyr-latest/doc/kernel/services/scheduling/ |
D | index.rst | 192 of equal-priority threads receive an equitable amount of CPU time, 193 since it does not measure the amount of time a thread actually gets to
|
1234567