doc: migration-guide-4.1: Add device driver details

Add a migration entry for the device driver API change, and start listing driver classes that have been updated in-tree. Signed-off-by: Pieter De Gendt <[email protected]>
zephyrproject-rtos · Nov 27, 2024 · 4af2ced · 4af2ced
1 parent 09e7419
commit 4af2ced
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/doc/kernel/drivers/index.rst b/doc/kernel/drivers/index.rst
@@ -61,6 +61,8 @@ High-level calls accessed through device-specific APIs, such as
 :file:`i2c.h` or :file:`spi.h`, are usually intended as synchronous. Thus,
 these calls should be blocking.
 
+.. _device_driver_api:
+
 Driver APIs
 ***********
 

diff --git a/doc/releases/migration-guide-4.1.rst b/doc/releases/migration-guide-4.1.rst
@@ -57,6 +57,13 @@ LVGL
 Device Drivers and Devicetree
 *****************************
 
+* Device driver APIs are placed into iterable sections (:github:`71773`) to allow for runtime
+  checking. See :ref:`device_drver_api` for more details.
+  The :c:macro:`DEVICE_API()` macro should by used out-of-tree driver implementations for
+  the following driver classes:
+
+    * :c:struct:`adc_driver_api`
+
 Controller Area Network (CAN)
 =============================