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 <pieter.degendt@basalte.be>
This commit is contained in:
parent
122eb71dda
commit
5a78f8f5ba
2 changed files with 9 additions and 0 deletions
|
@ -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
|
||||
***********
|
||||
|
||||
|
|
|
@ -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_driver_api` for more details.
|
||||
The :c:macro:`DEVICE_API()` macro should be used by out-of-tree driver implementations for
|
||||
the following driver classes:
|
||||
|
||||
* :c:struct:`adc_driver_api`
|
||||
|
||||
Controller Area Network (CAN)
|
||||
=============================
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue