Lines Matching +full:raw +full:- +full:y +full:- +full:max
22 out-of-tree SoCs and boards to be ported to the new model. See the
25 * The following build-time generated headers:
27 .. list-table::
28 :header-rows: 1
30 * - Affected header files
31 * - ``app_version.h``
32 * - ``autoconf.h``
33 * - ``cmake_intdef.h``
34 * - ``core-isa-dM.h``
35 * - ``devicetree_generated.h``
36 * - ``driver-validation.h``
37 * - ``kobj-types-enum.h``
38 * - ``linker-kobject-prebuilt-data.h``
39 * - ``linker-kobject-prebuilt-priv-stacks.h``
40 * - ``linker-kobject-prebuilt-rodata.h``
41 * - ``mcuboot_version.h``
42 * - ``offsets.h``
43 * - ``otype-to-size.h``
44 * - ``otype-to-str.h``
45 * - ``strerror_table.h``
46 * - ``strsignal_table.h``
47 * - ``syscall_list.h``
48 * - ``version.h``
49 * - ``zsr.h``
68 ``include/zephyr/sys/`` into ``include/zephyr/arch/``. Out-of-tree source files will need to
74 * Reordered D1 and D0 in the ``pro_micro`` connector gpio-map for SparkFun Pro Micro RP2040 to match
75 …original Pro Micro definition. Out-of-tree shields must be updated to reflect this change. (:githu…
86 ``vexriscv-intc0`` to :dtcompatible:`litex,vexriscv-intc0`. (:github:`73211`)
88 … boards. Laird Connectivity has rebranded to `Ezurio <https://www.ezurio.com/laird-connectivity>`_.
96 * TLS 1.2, RSA, AES, DES, and all the hash algorithms except SHA-256
97 (SHA-224, SHA-384, SHA-512, MD5 and SHA-1) are not enabled by default anymore.
103 enable all the available hash algorithms. Previously, it used to only enable the SHA-2 ones.
120 Trusted Firmware-M
123 * The default MCUboot signature type has been changed from RSA-3072 to EC-P256.
124 This affects builds that have MCUboot enabled in TF-M (:kconfig:option:`CONFIG_TFM_BL2`).
125 …If you wish to keep using RSA-3072, you need to set :kconfig:option:`CONFIG_TFM_MCUBOOT_SIGNATURE_…
126 …to ``"RSA-3072"``. Otherwise, make sure to have your own signing keys of the signature type in use.
132 driver to the input subsystem and use a :dtcompatible:`zephyr,lvgl-pointer-input` in your
139 * The :dtcompatible:`nxp,kinetis-pit` pit driver has changed its compatible
142 compatible :dtcompatible:`nxp,pit-channel` and configure as below.
148 .. code-block:: devicetree
155 num-channels = <1>;
156 #address-cells = <1>;
157 #size-cells = <0>;
160 compatible = "nxp,pit-channel";
166 * The :dtcompatible:`nxp,kinetis-ethernet` has been deprecated in favor of
175 .. code-block:: devicetree
179 pinctrl-0 = <&pinmux_enet>;
180 pinctrl-names = "default";
181 phy-handle = <&phy>;
182 zephyr,random-mac-address;
183 phy-connection-type = "rmii";
188 pinctrl-0 = <&pinmux_enet_mdio>;
189 pinctrl-names = "default";
191 compatible = "ethernet-phy";
197 * The :dtcompatible:`nxp,kinetis-lptmr` compatible string has been changed to
212 .. code-block:: devicetree
218 pwm-controller;
219 #pwm-cells = <2>;
224 .. code-block:: devicetree
232 compatible = "maxim,max31790-pwm";
234 pwm-controller;
235 #pwm-cells = <2>;
247 .. code-block:: devicetree
249 #include <zephyr/dt-bindings/sensor/icm42688.h>
252 accel-pwr-mode = <ICM42688_ACCEL_LN>;
253 accel-fs = <ICM42688_ACCEL_FS_16G>;
254 accel-odr = <ICM42688_ACCEL_ODR_2000>;
255 gyro-pwr-mode= <ICM42688_GYRO_LN>;
256 gyro-fs = <ICM42688_GYRO_FS_2000>;
257 gyro-odr = <ICM42688_GYRO_ODR_2000>;
260 * :dtcompatible:`st,lis2mdl` property ``spi-full-duplex`` changed to ``duplex =
263 * The DT property ``nxp,reference-supply`` of :dtcompatible:`nxp,lpc-lpadc` driver has
265 Added new phandle-array type DT property ``nxp,references``, the user can use this
269 * The DT properties ``mc,interface-type``, ``mc,reset-gpio``, and ``mc,interrupt-gpio`` of
271 ``microchip,interface-type``, ``reset-gpios``, and ``int-gpios``, respectively (:github:`73725`)
276 * Dropped ``constant-charge-current-max-microamp`` property in ``charger_max20335`` driver because
279 * Added enum key to ``constant-charge-voltage-max-microvolt`` property in ``maxim,max20335-charger``
285 * Removed the following deprecated CAN controller devicetree properties. Out-of-tree boards using
286 these properties can switch to using the ``bitrate``, ``sample-point``, ``bitrate-data``, and
287 ``sample-point-data`` devicetree properties (or rely on
292 * ``prop-seg``
293 * ``phase-seg1``
294 * ``phase-seg2``
295 * ``sjw-data``
296 * ``prop-seg-data``
297 * ``phase-seg1-data``
298 * ``phase-seg2-data``
300 The ``bus-speed`` and ``bus-speed-data`` CAN controller devicetree properties have been
305 * Support for manual bus-off recovery was reworked (:github:`69460`):
308 options. Since CAN controllers are initialized in "stopped" state, no unwanted bus-off recovery
318 either fail initialization or rely on automatic bus-off recovery. Having this as a mode
336 .. code-block:: devicetree
344 spi-max-frequency = <100000000>;
345 cmd-data-gpios = <&gpio0 8 GPIO_ACTIVE_HIGH>;
346 reset-gpios = <&gpio0 14 GPIO_ACTIVE_LOW>;
353 #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h>
358 compatible = "zephyr,mipi-dbi-spi";
359 dc-gpios = <&gpio0 8 GPIO_ACTIVE_HIGH>;
360 reset-gpios = <&gpio0 14 GPIO_ACTIVE_LOW>;
361 spi-dev = <&spi0>;
362 #address-cells = <1>;
363 #size-cells = <0>;
369 mipi-max-frequency = <100000000>;
377 manage interfacing with the display. Note that the ``cmd-data-gpios`` pin has
379 ``dc-gpios`` name. For an example, see below:
381 .. code-block:: devicetree
388 spi-max-frequency = <32000000>;
389 reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
390 cmd-data-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>;
397 #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h>
402 compatible = "zephyr,mipi-dbi-spi";
403 reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
404 dc-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
405 spi-dev = <&spi0>;
406 #address-cells = <1>;
407 #size-cells = <0>;
412 mipi-max-frequency = <32000000>;
413 mipi-mode = <MIPI_DBI_MODE_SPI_4WIRE>;
420 interfacing with the display. (:github:`73812`) Note that the ``dc-gpios``
423 .. code-block:: devicetree
430 spi-max-frequency = <4000000>;
431 reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
432 dc-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>;
439 #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h>
444 compatible = "zephyr,mipi-dbi-spi";
445 reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
446 dc-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
447 spi-dev = <&spi0>;
448 #address-cells = <1>;
449 #size-cells = <0>;
453 mipi-max-frequency = <4000000>;
461 ``cmd-data-gpios`` pin has changed polarity with this update, to align better
462 with the new ``dc-gpios`` name. For an example, see below:
464 .. code-block:: devicetree
471 spi-max-frequency = <32000000>;
472 reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
473 cmd-data-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>;
480 #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h>
485 compatible = "zephyr,mipi-dbi-spi";
486 reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
487 dc-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
488 spi-dev = <&spi0>;
489 #address-cells = <1>;
490 #size-cells = <0>;
495 mipi-max-frequency = <32000000>;
496 mipi-mode = <MIPI_DBI_MODE_SPI_4WIRE>;
503 which will manage interfacing with the display. Note that the ``dc-gpios``
506 .. code-block:: devicetree
513 spi-max-frequency = <4000000>;
514 reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
515 dc-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>;
522 #include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h>
527 compatible = "zephyr,mipi-dbi-spi";
528 reset-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
529 dc-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
530 spi-dev = <&spi0>;
531 #address-cells = <1>;
532 #size-cells = <0>;
537 mipi-max-frequency = <4000000>;
542 * The ``orientation-flipped`` property has been removed from the SSD16XX
564 * Basic power management support has been added to the ``gnss-nmea-generic`` driver.
565 If ``CONFIG_PM_DEVICE=y`` the driver is now initialized in suspended mode and the
572 * The ``analog-axis`` deadzone calibration value has been changed to be
573 relative to the raw ADC values, similarly to min and max. The data structures
574 and properties have been renamed to reflect that (from ``out-deadzone`` to
575 ``in-deadzone``) and when migrating to the new definition the value should be
578 * The ``holtek,ht16k33-keyscan`` driver has been converted to use the
580 :dtcompatible:`zephyr,kscan-input` can be used for backward compatibility. (:github:`69875`)
585 * The static auto-generation of the multilevel interrupt controller lookup table has been
590 Multi-level interrupt controller drivers should be updated to use the newly created
591 ``IRQ_PARENT_ENTRY_DEFINE`` macro to register itself with the new multi-level interrupt
602 * The property ``in-gpios`` defined in :dtcompatible:`worldsemi,ws2812-gpio` has been
605 * The ``chain-length`` and ``color-mapping`` properties have been added to all LED strip bindings
632 .. code-block:: devicetree
640 measure-mode = "normal";
641 clock-stretching;
655 as this setting should not be modified by the user. The DT property ``nxp,ground-select``
662 * The :dtcompatible:`zephyr,w1-gpio` 1-Wire master driver no longer defaults to enabling the
663 internal pull-up resistor of the GPIO pin. The configuration is now taken from the pin's
669 * The ``nuvoton,npcx-watchdog`` driver has been changed to extend the max timeout period.
670 The time of one watchdog count varies with the different pre-scalar settings.
684 selects which driver instance to use as the controller by looking for a ``zephyr,bt-hci``
686 ``bt-hci.yaml`` base binding.
688 * As part of the new HCI driver API, the ``zephyr,bt-uart`` chosen property is no longer used,
691 * As part of the new HCI driver API, the ``zephyr,bt-hci-ipc`` chosen property is only used for
693 ``zephyr,bt-hci-ipc``.
694 * The ``BT_NO_DRIVER`` Kconfig option was removed. HCI drivers are no-longer behind a Kconfig
711 got ``const`` qualifier too. The model's metadata structure and metadata raw value
712 can be declared as permanent constants in the non-volatile memory. (:github:`69679`)
794 .. code-block:: c
796 BT_DATA(BT_DATA_NAME_COMPLETE, CONFIG_BT_DEVICE_NAME, sizeof(CONFIG_BT_DEVICE_NAME) - 1)
822 interface. It is now being enforced through a build-time assertion.
851 the long-duration zperf test show with correct throughput result. (:github:`69500`)
870 * Modified the ``wifi connect`` command to use key-value format for the arguments. In the
873 for other options. Having this key-value format makes it easier to extend the options that
875 ``wifi -h`` will give more information about the usage of connect command.
887 during a Coap Block-wise transfer. Any post write, validate or some firmware callbacks
900 https://www.man7.org/linux/man-pages/man7/packet.7.html documentation. (:github:`73338`)
902 * TCP now uses SHA-256 instead of MD5 for ISN generation. The crypto support for
917 and the PSA implementation offers an even greater footprint reduction for devices built with TF-M.
919 …one-time cost of enabling the PSA API (:kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_C` for devices w…
932 * The support for SHA-256 (when using checksum/hash functions), previously provided
953 .. code-block:: bash
955 $ python ${ZEPHYR_BASE}/scripts/utils/migrate_posix_kconfigs.py -r root_path
964 * SMF now follows a more UML-like transition flow when the transition source is a parent of the
976 * The SHA-256 implementation used to perform integrity checks is not chosen with
980 …board is built with TF-M or :kconfig:option:`CONFIG_MBEDTLS_PSA_CRYPTO_C` is enabled. (:github:`73…