792b7e3570
Add a helper function that constructs a rtio SQE chain with the purpose
to perform a bus read operation on a list of registers.
Usage:
struct rtio_regs regs;
struct rtio_reg_list regs_list[] = {{regs_addr1, mem_addr_1, mem_len_1},
{regs_addr2, mem_addr_2, mem_len_2},
...
};
regs.rtio_regs_list = regs_list;
regs.rtio_regs_num = ARRAY_SIZE(regs_list);
rtio_read_regs_async(rtio,
iodev,
RTIO_BUS_SPI,
®s,
sqe,
dev,
op_cb);
Signed-off-by: Armando Visconti <armando.visconti@st.com>
129 lines
4.0 KiB
ReStructuredText
129 lines
4.0 KiB
ReStructuredText
:orphan:
|
|
|
|
..
|
|
What goes here: removed/deprecated apis, new boards, new drivers, notable
|
|
features. If you feel like something new can be useful to a user, put it
|
|
under "Other Enhancements" in the first paragraph, if you feel like something
|
|
is worth mentioning in the project media (release blog post, release
|
|
livestream) put it under "Major enhancement".
|
|
..
|
|
If you are describing a feature or functionality, consider adding it to the
|
|
actual project documentation rather than the release notes, so that the
|
|
information does not get lost in time.
|
|
..
|
|
No list of bugfixes, minor changes, those are already in the git log, this is
|
|
not a changelog.
|
|
..
|
|
Does the entry have a link that contains the details? Just add the link, if
|
|
you think it needs more details, put them in the content that shows up on the
|
|
link.
|
|
..
|
|
Are you thinking about generating this? Don't put anything at all.
|
|
..
|
|
Does the thing require the user to change their application? Put it on the
|
|
migration guide instead. (TODO: move the removed APIs section in the
|
|
migration guide)
|
|
|
|
.. _zephyr_4.3:
|
|
|
|
Zephyr 4.3.0 (Working Draft)
|
|
############################
|
|
|
|
We are pleased to announce the release of Zephyr version 4.3.0.
|
|
|
|
Major enhancements with this release include:
|
|
|
|
An overview of the changes required or recommended when migrating your application from Zephyr
|
|
v4.2.0 to Zephyr v4.3.0 can be found in the separate :ref:`migration guide<migration_4.3>`.
|
|
|
|
The following sections provide detailed lists of changes by component.
|
|
|
|
Security Vulnerability Related
|
|
******************************
|
|
The following CVEs are addressed by this release:
|
|
|
|
More detailed information can be found in:
|
|
https://docs.zephyrproject.org/latest/security/vulnerabilities.html
|
|
|
|
API Changes
|
|
***********
|
|
|
|
* RTIO
|
|
|
|
* :c:func:`rtio_is_spi`
|
|
* :c:func:`rtio_is_cspi`
|
|
* :c:func:`rtio_is_i3c`
|
|
* :c:func:`rtio_read_regs_async`
|
|
|
|
Removed APIs and options
|
|
========================
|
|
|
|
* The TinyCrypt library was removed as the upstream version is no longer maintained.
|
|
PSA Crypto API is now the recommended cryptographic library for Zephyr.
|
|
|
|
Deprecated APIs and options
|
|
===========================
|
|
|
|
New APIs and options
|
|
====================
|
|
|
|
..
|
|
Link to new APIs here, in a group if you think it's necessary, no need to get
|
|
fancy just list the link, that should contain the documentation. If you feel
|
|
like you need to add more details, add them in the API documentation code
|
|
instead.
|
|
|
|
.. zephyr-keep-sorted-start re(^\* \w)
|
|
|
|
* Settings
|
|
|
|
* :kconfig:option:`CONFIG_SETTINGS_TFM_ITS`
|
|
|
|
.. zephyr-keep-sorted-stop
|
|
|
|
New Boards
|
|
**********
|
|
|
|
..
|
|
You may update this list as you contribute a new board during the release cycle, in order to make
|
|
it visible to people who might be looking at the working draft of the release notes. However, note
|
|
that this list will be recomputed at the time of the release, so you don't *have* to update it.
|
|
In any case, just link the board, further details go in the board description.
|
|
|
|
New Drivers
|
|
***********
|
|
|
|
..
|
|
Same as above for boards, this will also be recomputed at the time of the release.
|
|
Just link the driver, further details go in the binding description
|
|
|
|
* Input
|
|
|
|
* :dtcompatible:`chipsemi,chsc5x`
|
|
|
|
* Interrupt controller
|
|
|
|
* STM32 EXTI interrupt/event controller (:dtcompatible:`st,stm32-exti`) has a dedicated driver and API now, separate from STM32 GPIO Interrupt Control driver.
|
|
|
|
* RTC
|
|
|
|
* STM32 RTC driver has been updated to use the new STM32 EXTI interrupt controller API
|
|
|
|
|
|
New Samples
|
|
***********
|
|
|
|
..
|
|
Same as above for boards and drivers, this will also be recomputed at the time of the release.
|
|
Just link the sample, further details go in the sample documentation itself.
|
|
|
|
Other notable changes
|
|
*********************
|
|
|
|
..
|
|
Any more descriptive subsystem or driver changes. Do you really want to write
|
|
a paragraph or is it enough to link to the api/driver/Kconfig/board page above?
|
|
|
|
* Removed support for Nordic Semiconductor nRF54L20 PDK (``nrf54l20pdk``) since it is
|
|
replaced with :zephyr:board:`nrf54lm20dk` (``nrf54lm20dk``).
|