Searched refs:pulled (Results 1 – 13 of 13) sorted by relevance
35 pulled up.
5 # is pulled in as though the source files are in main repo. This results in
15 pulled out through a file system registration API. Each file system
36 amount of code pulled in if used. Build time filtering is supported,
1741 uint16_t pulled; in sdp_client_get_total() local1753 pulled = 1U; in sdp_client_get_total()1757 pulled += 1U; in sdp_client_get_total()1761 pulled += 2U; in sdp_client_get_total()1765 pulled += 4U; in sdp_client_get_total()1775 pulled = 0U; in sdp_client_get_total()1779 return pulled; in sdp_client_get_total()
37 However, when ``EXT1`` is also enabled, GPIO2 and GPIO4 should be pulled-down
107 supply. If this pin is pulled low this main 3.3V power supply for the MCU will be
353 The I2C port can independently pulled up to 3V3 through JP3 (I2C_SCL) and JP4 (I2C_SDA).367 respectively. If the pushbutton is pressed, the attached port pin is pulled low.
40 GCC's __udivdi3 helper could end up being pulled into the
309 The I2C ports can independently pulled up to V_AUX (3.3V default) through JP4 (I2C0_CL_PU) and JP5
3 ; This does *not* cover macros pulled out of DT via Kconfig,
60 * Picolibc can either be built as part of the OS build or pulled from the
1772 * :github:`26975` - Control never returns from stm32_i2c_msg_write(), when SCL is pulled low perman…1911 * :github:`16766` - net: net_pkt_copy don't work as expected when data was pulled from destination
