Searched full:most (Results 1 – 25 of 334) sorted by relevance
12345678910>>...14
| /Zephyr-Core-2.7.6/subsys/net/l2/ethernet/gptp/ |
| D | gptp_md.h | 32 /** Most recent preciseOriginTimestamp from the PortSyncSync. */
35 /** Most recent followupCorrectionField from the PortSyncSync. */
38 /** Most recent upstreamTxTime from the PortSyncSync. */
44 /** Most recent rateRatio from the PortSyncSync. */
|
| /Zephyr-Core-2.7.6/include/arch/common/ |
| D | ffs.h | 21 * @brief find most significant bit set in a 32-bit word
23 * This routine finds the first bit set starting from the most significant bit
28 * @return most significant bit set, 0 if @a op is 0
|
| /Zephyr-Core-2.7.6/subsys/net/l2/ieee802154/ |
| D | Kconfig.radio | 30 Use CSMA-CA mechanism to transmit packets. This is the most common
31 way of transmitting packets and fits most of all the usage.
|
| /Zephyr-Core-2.7.6/doc/reference/peripherals/ |
| D | sensor.rst | 67 Setting the communication bus and address is considered the most basic
75 In compliance with Zephyr's design goals, most of these values are
96 Because most sensors are connected via SPI or I2C busses, it is not possible
103 approach to follow for each driver. Most drivers can entirely disable
|
| /Zephyr-Core-2.7.6/cmake/usage/ |
| D | usage.cmake | 14 message(" clean - Remove most generated files but keep configuration and backup files")
41 message(" 3: more obscure warnings, can most likely be ignored")
|
| /Zephyr-Core-2.7.6/include/drivers/sensor/ |
| D | ccs811.h | 61 /** Sensor status at completion of most recent fetch. */
65 * Sensor error flags at completion of most recent fetch.
73 * @brief Access storage for the most recent data read from the sensor.
|
| /Zephyr-Core-2.7.6/drivers/pinmux/ |
| D | pinmux_intel_s1000.c | 28 * retrieve the least and most significant bit positions for in pinmux_set()
56 * retrieve the least and most significant bit positions for in pinmux_get()
|
| /Zephyr-Core-2.7.6/subsys/bluetooth/controller/util/ |
| D | util.c | 56 * - It shall have a minimum of two transitions in the most significant six
126 /* It shall have a minimum of two transitions in the most in util_aa_le32()
275 uint8_t dwh[2]; /* Holds the two most significant bytes of DW */ in util_bis_aa_le32()
283 /* Most significant 6 bits of DW are bit extension of least significant in util_bis_aa_le32()
296 /* Most significant 16-bits of SAA XOR DW, least significant 16-bit are in util_bis_aa_le32()
|
| /Zephyr-Core-2.7.6/samples/subsys/mgmt/mcumgr/smp_svr/ |
| D | prj.conf | 20 # Enable most core commands.
|
| /Zephyr-Core-2.7.6/drivers/interrupt_controller/ |
| D | Kconfig.shared_irq | 10 support is NOT required in most systems. If in doubt answer no.
|
| D | Kconfig.multilevel | 52 aggregator can manage at most MAX_IRQ_PER_AGGREGATOR level 2
89 aggregator can manage at most MAX_IRQ_PER_AGGREGATOR level 3
|
| /Zephyr-Core-2.7.6/cmake/compiler/armclang/ |
| D | compiler_flags.cmake | 1 # First step is to inherit all properties from gcc, as clang is compatible with most flags.
|
| /Zephyr-Core-2.7.6/.github/ |
| D | SECURITY.md | 8 - The most recent release, and the release prior to that.
|
| /Zephyr-Core-2.7.6/dts/bindings/mdio/ |
| D | mdio-controller.yaml | 17 MDIO bus framing protocol to use for communication. Most devices
|
| /Zephyr-Core-2.7.6/boards/arm/sparkfun_thing_plus_nrf9160/doc/ |
| D | index.rst | 82 sparkfun_thing_plus_nrf9160 can be used with most programmers like:
92 In most cases you'll want to use the ``ns`` target with any of the Zephyr
115 can be found. In most cases (On Linux/Mac) it will be: :code:`/dev/tty.SLAB_USBtoUART`.
|
| /Zephyr-Core-2.7.6/boards/arm/circuitdojo_feather_nrf9160/doc/ |
| D | index.rst | 88 by most programmers like:
98 In most cases you'll want to use the ``ns`` target with any of the Zephyr
121 can be found. In most cases (On Linux/Mac) it will be: :code:`/dev/tty.SLAB_USBtoUART`.
|
| /Zephyr-Core-2.7.6/include/pm/ |
| D | policy.h | 20 * idle and returns the most appropriate state based on the number of
|
| /Zephyr-Core-2.7.6/arch/arm/core/aarch32/cortex_m/ |
| D | vector_table_pad.ld | 15 * multiple times, the padding will only be added at most once, to the
|
| /Zephyr-Core-2.7.6/drivers/display/ |
| D | display_framebuf.c | 4 * This is most of the display driver for a "standard" 32-bpp framebuffer.
6 * it accordingly, but this driver implements most/all of the API functions.
|
| /Zephyr-Core-2.7.6/doc/reference/bluetooth/mesh/ |
| D | cfg_srv.rst | 7 specification. The Configuration Server model controls most parameters of the
|
| D | cfg_cli.rst | 7 specification. It provides functionality for configuring most parameters of a
|
| /Zephyr-Core-2.7.6/doc/guides/tfm/ |
| D | overview.rst | 41 A TF-M application will, generally, have the following three parts, from most
72 hierarchies of trust from most, to less, to least trusted, providing a sound
80 The following RoT hierarchy is defined for TF-M, from most to least trusted:
85 * PSA Updateable Root of Trust: most trusted secure services
88 The **PSA Immutable Root of Trust** is the most trusted piece of code in the
96 The **PSA Updateable Root of Trust** implements the most trusted secure
|
| /Zephyr-Core-2.7.6/include/dt-bindings/interrupt-controller/ |
| D | intel-ioapic.h | 17 * for most device interrupts, lowest priority delivery is preferred
|
| /Zephyr-Core-2.7.6/drivers/modem/ |
| D | Kconfig | 36 Maximum number of modem receiver contexts to handle. For most
55 Maximum number of modem contexts to handle. For most
|
| /Zephyr-Core-2.7.6/doc/development_process/ |
| D | documentation.rst | 20 APIs for the most part document the implementation of requirements or advertised
43 The Zephyr project uses several test methodologies, the most common being the
|
12345678910>>...14
