Searched full:stable (Results 1 – 25 of 111) sorted by relevance
12345
| /Zephyr-latest/doc/develop/api/ |
| D | overview.rst | 14 change at any time. The public API SHOULD NOT be considered stable.
26 considered :ref:`stable <api_lifecycle_stable>`.
27 * All existing stable APIs in Zephyr will be start with version 1.0.0.
49 - and finally 1.0.0 indicates a :ref:`stable <api_lifecycle_stable>` APIs.
|
| D | api_lifecycle.rst | 62 testing to be considered stable. The API is considered generic in nature and can
87 Stable section in API Lifecycle
93 An API can be declared ``stable`` after fulfilling the following requirements:
99 - Stable APIs can get backward compatible updates, bug fixes and security fixes
102 In order to declare an API ``stable``, the following steps need to be followed:
113 When the API changes status to stable API, mark the API version in the headers
114 where the API is defined. Stable APIs shall have a version where the major
122 A stable API, as described above, strives to remain backwards-compatible through
220 - Deprecation Time (stable APIs): 2 Releases
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.nrf_xrtc | 33 System clock source initialization waits until clock is stable. When this
34 option is picked, system clock is available and stable after system clock
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.ipv6 | 196 User can also choose to use stable IID specified in RFC 7217 in which
198 The stable IID enhances privacy by having a different IID for each
208 bool "Generate stable IID [EXPERIMENTAL]"
214 Generate a stable IID described in RFC 7217. This option specifies a
217 address configured using this method is stable within each subnet,
222 such that the benefits of stable addresses can be achieved without
224 Currently the stable IID generation is disabled for 6lo networks
|
| /Zephyr-latest/dts/bindings/input/ |
| D | kbd-matrix-common.yaml | 26 stable-poll-period-ms:
30 stable, defaults to poll-period-ms value if unspecified.
|
| /Zephyr-latest/tests/net/iface/ |
| D | testcase.yaml | 12 net.iface.iid.stable:
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/conn_stress/peripheral/ |
| D | prj.conf | 33 # TODO: remove when test is stable
|
| /Zephyr-latest/include/zephyr/bluetooth/ |
| D | testing.h | 9 * The interfaces in this file are internal and not stable.
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 6 The stable and long existing APIs for reading sensor data and handling triggers
40 Triggers in the stable API require enabling triggers with a device
|
| /Zephyr-latest/drivers/sensor/nxp/nxp_kinetis_temp/ |
| D | Kconfig | 31 more stable readings.
|
| /Zephyr-latest/samples/drivers/espi/dts/bindings/ |
| D | mec15xx-board-power.yaml | 16 Board GPIO input used to detect that power rails are stable.
|
| D | mec172x-board-power.yaml | 16 Board GPIO input used to detect that power rails are stable.
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/conn_stress/central/ |
| D | prj.conf | 35 # TODO: remove when test is stable
|
| /Zephyr-latest/dts/bindings/sensor/ |
| D | ti,ina219.yaml | 78 Averaging over multiple samples gives more stable readings but adds
114 Averaging over multiple samples gives more stable readings but adds
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 60 sufficiently stable (and which is accepted by the maintainers and the wide community) is
90 considered to be sufficiently stable and the release criteria have been achieved
236 - **Stable APIs**
250 documented and tracked. The footprint and scope of mature and stable APIs expands
252 and new hardware while keeping a stable foundation that evolves over time.
263 Stable APIs
266 Zephyr LTS provides a stable and long-lived foundation for developing
271 mature and well-established implementations with stable APIs that are
276 - All stable APIs need to be frozen 2 releases before an LTS. APIs can be extended
|
| D | release_cycle.svg | 4 …stable</div></div></div></foreignObject><text x="78" y="119" fill="rgb(0, 0, 0)" font-family="Helv…
|
| /Zephyr-latest/tests/posix/eventfd/ |
| D | Kconfig | 14 eventfd_write() are stable enough to run for an arbitrarily long
|
| /Zephyr-latest/samples/subsys/edac/src/ |
| D | main.c | 27 * delayed_work, mutex and semaphores are not working stable in notification_callback()
|
| /Zephyr-latest/soc/espressif/common/ |
| D | Kconfig.esptool | 92 - Flash 120 MHz SDR mode is stable.
94 the temperature is stable.
|
| /Zephyr-latest/doc/services/input/ |
| D | index.rst | 17 includes a synchronization bit to indicate that the device reached a stable
29 bit once the output is stable.
|
| /Zephyr-latest/doc/develop/manifest/external/ |
| D | cannectivity.rst | 57 https://python-can.readthedocs.io/en/stable/interfaces/gs_usb.html
|
| /Zephyr-latest/doc/contribute/ |
| D | proposals_and_rfcs.rst | 21 - The modification of an existing stable API.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | i2c.rst | 35 considered stable.
|
| /Zephyr-latest/drivers/clock_control/ |
| D | Kconfig.stm32 | 77 Since the LSI RC frequency is affected by temperature, which is not stable
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt118x/ |
| D | soc.c | 82 * Note : Users need override this function to change FLEXSPI clock source to stable
84 * should runs in RAM and move the FLEXSPI clock source to a stable clock
133 /* Wait for 24M OSC to be stable. */ in clock_init()
138 /* Call function board_flexspi_clock_safe_config() to move FlexSPI clock to a stable in clock_init()
|
12345
