Searched full:way (Results 1 – 25 of 1096) sorted by relevance
12345678910>>...44
/Zephyr-latest/scripts/pylib/pytest-twister-harness/tests/resources/ |
D | zen_of_python.py | 22 There should be one-- and preferably only one --obvious way to do it. 23 Although that way may not be obvious at first unless you're Dutch.
|
/Zephyr-latest/include/zephyr/bluetooth/mesh/ |
D | cfg_cli.h | 511 * as NULL. This way the method will not wait for response and will return 529 * as NULL. This way the method will not wait for response and will 545 * as NULL. This way the method will not wait for response and will 562 * as NULL. This way the method will not wait for response and will 581 * as NULL. This way the method will not wait for response and will 599 * as NULL. This way the method will not wait for response and will 613 * as NULL. This way the method will not wait for response and will 628 * as NULL. This way the method will not wait for response and will 644 * as NULL. This way the method will not wait for response and will 663 * as NULL. This way the method will not wait for response and will [all …]
|
D | brg_cfg_cli.h | 117 * way the method will not wait for response and will return immediately after 140 * way the method will not wait for response and will return immediately after 166 * This method can be used asynchronously by setting @p size as NULL. This way 187 * This method can be used asynchronously by setting @p rsp as NULL. This way 211 * This method can be used asynchronously by setting @p rsp as NULL. This way 238 * This method can be used asynchronously by setting @p rsp as NULL. This way 269 * This method can be used asynchronously by setting @p rsp as NULL. This way
|
/Zephyr-latest/doc/kernel/data_structures/ |
D | index.rst | 10 way. 18 address from the embedded node pointer in a clean way. The purpose
|
/Zephyr-latest/subsys/net/l2/ieee802154/ |
D | Kconfig.radio | 32 to transmit packets. This is the most common way of mediating radio 40 transmit packets. This is a simplistic way of transmitting packets
|
/Zephyr-latest/samples/sensor/bme280/ |
D | Kconfig | 14 # the device connected either way. These defaults can be overridden if
|
/Zephyr-latest/samples/net/sockets/http_client/ |
D | Kconfig | 13 zero means that the sample application in default way.
|
/Zephyr-latest/arch/xtensa/core/ |
D | README_MMU.txt | 14 4-way-set-associative bank of entries mapping 4k pages, and 3-6 84 an entry for the page table page we want. And the simplest way to do 129 same way we do for data, but somewhat inexplicably, Xtensa does not 135 vector page to succeed always. The way to do this is to similarly pin 148 The way Xtensa resolves this (on the hardware Zephyr supports, see the 149 note below) is to have an 8-entry set ("way 6") of 512M pages able to 199 where the way 5/6 pages are immutable, and specify a set of 261 invisible to the data cache of another. There is no simple way of
|
/Zephyr-latest/soc/atmel/sam/common/ |
D | pwm_fixup.h | 11 * define it this way to match how the other SoC variants name it
|
/Zephyr-latest/boards/qorvo/decawave_dwm1001_dev/doc/ |
D | index.rst | 19 flashed, and debugged in the usual way. See :ref:`build_an_application` and 42 Then build and flash the application in the usual way.
|
/Zephyr-latest/boards/qorvo/decawave_dwm3001cdk/doc/ |
D | index.rst | 22 and debugged in the usual way. See :ref:`build_an_application` and 46 Then build and flash the application in the usual way.
|
/Zephyr-latest/dts/bindings/clock/ |
D | renesas,ra-cgc-external-clock.yaml | 18 Choose the way for external Clock Oscillator supply
|
/Zephyr-latest/samples/subsys/sensing/simple/ |
D | app.overlay | 8 * Names in this file should be chosen in a way that won't conflict
|
/Zephyr-latest/samples/subsys/debug/fuzz/src/ |
D | main.c | 24 * tree in such a way that it would be very unlikely to be found by 26 * linear(-ish) time by discovering each new function along the way 31 * generate the recursive handler functions this way and disable
|
/Zephyr-latest/soc/cdns/dc233c/ |
D | Kconfig.defconfig | 18 # via TLB way 4 (which covers 1MB).
|
/Zephyr-latest/samples/subsys/debug/fuzz/ |
D | sample.yaml | 11 # The sample will run all the way to key 6 (to show off its
|
/Zephyr-latest/arch/xtensa/include/ |
D | xtensa_mmu_priv.h | 126 /** Fixed data TLB way to map the page table */ 129 /** Fixed data TLB way to map the vecbase */ 187 * Generalizing it, any PTE virtual address can be calculated this way: 350 uint8_t way, i, entries; in xtensa_tlb_autorefill_invalidate() local 355 for (way = 0; way < XTENSA_MMU_NUM_TLB_AUTOREFILL_WAYS; way++) { in xtensa_tlb_autorefill_invalidate() 357 uint32_t entry = way + (i << XTENSA_MMU_PTE_PPN_SHIFT); in xtensa_tlb_autorefill_invalidate()
|
/Zephyr-latest/subsys/bluetooth/host/classic/ |
D | hfp_internal.h | 15 #define BT_HFP_AG_FEATURE_3WAY_CALL 0x00000001 /* Three-way calling */ 32 #define BT_HFP_HF_FEATURE_3WAY_CALL 0x00000002 /* Three-way calling */
|
/Zephyr-latest/samples/basic/hash_map/ |
D | Kconfig | 11 in a convenient way. This option translates to MANY in the test sources.
|
/Zephyr-latest/include/zephyr/dt-bindings/usb/ |
D | usb.h | 10 * however, we dont have a good way to know how to name such an enum from
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | sntp.rst | 16 SNTP provides a way to synchronize clocks in computer networks.
|
/Zephyr-latest/tests/lib/hash_map/ |
D | Kconfig | 11 in a convenient way. This option translates to MANY in the test sources.
|
/Zephyr-latest/dts/bindings/sd/ |
D | zephyr,mmc-disk.yaml | 16 Indicates the way the MMC device is connected to the bus.
|
/Zephyr-latest/lib/os/ |
D | Kconfig | 36 storing variable length packets in a circular way and operate directly 43 storing variable length packets in a circular way and operate directly
|
/Zephyr-latest/doc/build/dts/ |
D | phandles.rst | 7 C. You can use phandles to refer to nodes in devicetree similarly to the way 16 The usual way to get a phandle for a devicetree node is from one of its node 48 is related to ``node-a`` in some way. 154 that controls a group of pins. This reflects the way GPIO IP blocks are usually 201 *Specifier spaces* are a way to allow nodes to describe how you should 228 complex, but it's really just a way to assign a meaning to the cells that 229 follow each phandle in a hardware specific way. Every specifier space has a
|
12345678910>>...44