| /nrf52832-nimble/nordic/nrfx/drivers/include/ |
| H A D | nrfx_usbd.h | 58 * This number would be shared between IN and OUT endpoint.
162 … * This error would also be returned when next_transfer function has been defined
398 * After calling this function USBD peripheral would be enabled.
399 * The USB LDO would be enabled.
400 * Enabled USBD peripheral would request HFCLK.
402 * program after enabling USBD driver HFINT would be used for the USBD peripheral.
408 * Interrupts and USB pins pull-up would stay disabled until @ref nrfx_usbd_start
416 * After calling this function USBD peripheral would be disabled.
417 * No events would be detected or processed by the driver.
418 * Clock for the peripheral would be disconnected.
[all …]
|
| H A D | nrfx_power.h | 143 * The regulator would be enabled or disabled automatically
154 * The regulator would be enabled or disabled automatically
220 * Enabled power module driver would process all the interrupts from power system.
247 * If event handler is set to NULL, interrupt would be disabled.
255 * would be disabled.
|
| H A D | nrfx_systick.h | 54 * would be the highest supported time in the library.
55 * But it would be really hard to detect if overflow was generated without
56 * using interrupts. For safety we would limit the maximum delay range by half.
|
| H A D | nrfx_twis.h | 178 * It would be used by interrupts so make it sure that object
179 * would not be destroyed when function is leaving.
206 * selected pins would not be reset to default configuration.
291 * @param[in] p_buf Buffer that would be filled with received data.
|
| /nrf52832-nimble/packages/NimBLE-latest/apps/blemesh_models_example_1/ |
| H A D | README.md | 30 using one button for "on" and another for "off" would reduce the number
36 This sample has been tested on the Nordic nRF52840-PDK board, but would
43 would expect with an actual switch.
|
| /nrf52832-nimble/rt-thread/tools/kconfig-frontends/libs/lxdialog/ |
| H A D | menubox.c | 29 * *) Formerly when I used Page Down and Page Up, the cursor would be set
34 * *) Formerly if I selected something my scrolling would be broken because
40 * one, but it would be nice if Menuconfig could make another "rm -f"
55 * would leave mis-synchronized lxdialog.scrltmp files lying around,
56 * fscanf would read in 'scroll', and eventually that value would get used.
|
| /nrf52832-nimble/rt-thread/components/drivers/audio/ |
| H A D | audio_pipe.h | 36 /* read would block */
38 /* write would block */
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/src/ |
| H A D | README | 107 in a product, an acknowledgment in the product documentation would be
116 If you use the zlib library in a product, we would appreciate *not*
122 If you redistribute modified sources, we would appreciate that you include
|
| H A D | algorithm.txt | 18 it would be useful to start another block with fresh trees. (This is
76 table took no time (and if you had infinite memory), then there would only
87 length, i.e. the code length of an approximately flat code which would be a
122 would take too long if you're only decoding several thousand symbols. At the
|
| H A D | FAQ | 55 Because we would like to keep zlib as a very small and simple
191 in zlib.h as you would for a full source distribution.
268 If you don't have snprintf() or vsnprintf() and would like one, you can
322 "deflate" transfer encoding using the zlib format would be the more
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/core/ipv6/ |
| H A D | icmp6.c | 213 * received right now. Otherwise, address zones would be lost.
229 * received right now. Otherwise, address zones would be lost.
245 * received right now. Otherwise, address zones would be lost.
283 * received right now. Otherwise, address zones would be lost and the calculated
284 * offset would be wrong (calculated against ip6_current_header()).
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/controller/test/src/ |
| H A D | ble_ll_csa2_test.c | 33 * prn_e and unmapped channel values but those would require extra access in TEST_CASE()
75 * prn_e and unmapped channel values but those would require extra access in TEST_CASE()
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/netif/ppp/ |
| H A D | ppp.h | 110 * named user would be authenticated by multiple methods. This would
113 * secret was used, PAP would reveal the secret to be used later with
|
| /nrf52832-nimble/rt-thread/tools/kconfig-frontends/docs/ |
| H A D | kconfig-language.txt | 429 We would in lib/Kconfig see:
437 And in lib/Makefile we would see:
440 For each architecture using the generic IOMAP functionality we would see:
562 the current known recursive dependency issues. It is not known if this would
591 industrial variability modeling languages [1] [2]. Its study would help
614 desirable on Kconfig one approach would be to evaluate repurposing such efforts
|
| /nrf52832-nimble/rt-thread/libcpu/arm/realview-a8-vmm/ |
| H A D | context_gcc.S | 76 @ need to make sure we are in vmm domain as we would use rt_current_thread
105 the guest thread would call rt_hw_context_switch and "yield".
|
| /nrf52832-nimble/packages/NimBLE-latest/ext/tinycrypt/documentation/ |
| H A D | tinycrypt.rst | 92 peculiarities would increase the code size and thus are not considered here.
165 blocks. If you need to encrypt larger data sets, your application would
179 very efficient decryption algorithm that would not otherwise be possible.
186 collision property of AES128-CMAC, an external attacker would need the
|
| /nrf52832-nimble/rt-thread/components/net/freemodbus/modbus/include/ |
| H A D | mb.h | 307 * timeout would be violated. In this case a <b>SLAVE DEVICE BUSY</b>
329 * this would be the case when the Modbus master has issued an
342 * timeout would be violated. In this case a <b>SLAVE DEVICE BUSY</b>
377 * timeout would be violated. In this case a <b>SLAVE DEVICE BUSY</b>
406 * timeout would be violated. In this case a <b>SLAVE DEVICE BUSY</b>
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/api/ |
| H A D | err.c | 56 EWOULDBLOCK, /* ERR_WOULDBLOCK -7 Operation would block. */
88 "Operation would block.", /* ERR_WOULDBLOCK -7 */
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/api/ |
| H A D | err.c | 56 EWOULDBLOCK, /* ERR_WOULDBLOCK -7 Operation would block. */
88 "Operation would block.", /* ERR_WOULDBLOCK -7 */
|
| /nrf52832-nimble/nordic/nrfx/drivers/src/ |
| H A D | nrfx_usbd.c | 209 * Event handler that would be called on events.
263 * It would be cleared only from USBD interrupt.
287 * @brief The structure that would hold transfer configuration to every endpoint
341 * This is internal buffer that would be used to emulate the possibility
746 * If it is OUT endpoint transmission would be directed from endpoint to RAM.
747 * If it is in endpoint transmission would be directed from RAM to endpoint.
777 * This function would check it again, but it makes it inside critical section.
790 /* If the bit in m_ep_dma_waiting in cleared - nothing would be in usbd_ep_abort()
881 * Interrupt runtimes that would be vectorized using @ref m_isr.
908 * This handler would be called when EasyDMA transfer for endpoints that does not require clearing.
[all …]
|
| /nrf52832-nimble/nordic/nrfx/hal/ |
| H A D | nrf_systick.h | 51 * Also keep in mind that this timer would be stopped when CPU is sleeping
123 * Any write to VAL register would clear the timer.
|
| /nrf52832-nimble/rt-thread/documentation/ |
| H A D | coding_style_en.txt | 143 When matching braces have their own lines, the reader would identify the code
175 would have influence to the timing sequence of the log output.
|
| /nrf52832-nimble/rt-thread/documentation/doxygen/ |
| H A D | kernel.h | 83 * when the resource is available, thread pended on this resource at first would get
87 * priority would get the resource.
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/ |
| H A D | mqtt_client.txt | 81 normal behaviour would be to take some action if subscribe fails like
90 Example here uses a global variable, better would be to use a member in arg
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/doc/ |
| H A D | mqtt_client.txt | 81 normal behaviour would be to take some action if subscribe fails like
90 Example here uses a global variable, better would be to use a member in arg
|